Hahaha. Vecel, planet scale, 0auth (or something) and a credit card are the requirements to be a real modern web dev 🤪 i must give him one thing, he put axiom on my radar which I use. 👍
@@lindblomdev yeah a broken clock is also correct twice a day… so occasionally he puts out something useful. But 99% of the time it’s basically JavaScript/react madness and if you don’t agree you’re a horrible person and a terrible dev… I remember when DHH talked about leaving the cloud and him having a meltdown over it XD
Both doing the work that is not yet and may never be required and working in a way that prevents future change are a problem, but working in a way that enables future change is not the exactly the same as assuming what that change will look like.
Imagine if you have issue A in 5 years from now Imagine if you have issue B in 10 years from now Those aren't "imagine" problems, those are problems that people can't fix them when they will happened, so they are creating solutions for the future, because it will be easy :) Imagine been paid (top money) for problem solving and you don't know how to solve the problem in front of you
You know I actually resigned from a job due to the imaginary problem solving tasks/project. Basically imaginary problem for a potential imaginary customer that would probably use it for the imagined use case. In the end of course nothing was realized the project was put off because you can not work forever on imaginary income. I think that these people are either malicious or stupid. If they have a customer and are billing them for the imaginary tasks. But the end result is usually bad. Shipping bad product that are difficult to change due to bad assumptions and decisions. Personally coming from a position where we shipped software to real users with real feedback you can see that the only way to do it is iteratively. The users/market feedback will let you know what direction is the project going. My 2c like the videos 👍
Theo will be exploding of anger, he's the guy who is pushing for entire techstacks that solve non-existent problems
Hahaha. Vecel, planet scale, 0auth (or something) and a credit card are the requirements to be a real modern web dev 🤪 i must give him one thing, he put axiom on my radar which I use. 👍
@@lindblomdev yeah a broken clock is also correct twice a day… so occasionally he puts out something useful. But 99% of the time it’s basically JavaScript/react madness and if you don’t agree you’re a horrible person and a terrible dev… I remember when DHH talked about leaving the cloud and him having a meltdown over it XD
Before development start with product research, design, and then development. Repeat that after shipping.
I think this ties into ux and user testing instead of making assumptions about users and their behavior.
Wayland protocol discussions be like:
Both doing the work that is not yet and may never be required and working in a way that prevents future change are a problem, but working in a way that enables future change is not the exactly the same as assuming what that change will look like.
i completely broke apart when the mic dropped slowly hahaha
Haha yeah a real content creator pro over here, didn't even notice until later 😆
Imagine if you have issue A in 5 years from now
Imagine if you have issue B in 10 years from now
Those aren't "imagine" problems, those are problems that people can't fix them when they will happened, so they are creating solutions for the future, because it will be easy :)
Imagine been paid (top money) for problem solving and you don't know how to solve the problem in front of you
You know I actually resigned from a job due to the imaginary problem solving tasks/project.
Basically imaginary problem for a potential imaginary customer that would probably use it for the imagined use case. In the end of course nothing was realized the project was put off because you can not work forever on imaginary income.
I think that these people are either malicious or stupid. If they have a customer and are billing them for the imaginary tasks. But the end result is usually bad. Shipping bad product that are difficult to change due to bad assumptions and decisions.
Personally coming from a position where we shipped software to real users with real feedback you can see that the only way to do it is iteratively.
The users/market feedback will let you know what direction is the project going. My 2c like the videos 👍
I feel your pain, good call 👊