CV Driven Development is exactly what happened. I'm looking for new job now, and nobody is asking me about problem solving but only about frameworks and tools. So what should I do to survive? I have no other choice than to adapt. Maybe I will find something the old way, like "we have this goals and problems, can you help us?", but I'm about to give up.
Honestly, I can understand the sentiment behind these types of talks, but they don't really say much of interest. Everyone hates the problems with whatever they're working with - thirty years ago, stupid server issues, slow hardware allocation and spin-up, and routine system updates sucked. Now we complain about cloud providers APIs, kubernetes, and whatever the newest tech is because we have to use it. What's really important, and something Hariri barely touches on in his presentation, is the tradeoffs of when one technology or language or paradigm's benefits and drawbacks outweigh their alternatives. Sure, dealing with kubernetes deployments can be a pain - but I bet it's better than having to call your in-house hardware guys and ask why DSC-PROD-11 isn't working. Complaining is easy. Solutions are hard.
CV Driven Development is exactly what happened. I'm looking for new job now, and nobody is asking me about problem solving but only about frameworks and tools. So what should I do to survive? I have no other choice than to adapt. Maybe I will find something the old way, like "we have this goals and problems, can you help us?", but I'm about to give up.
* His presentation was well-crafted;
* He made good use of his presentation with the things he said
* The next time I present, I will surely do so.
One of the best talks -- everyone should watch
This made my monday. And gave something to think about as we are just planning "the next thing"
Great talk!
Amen
Honestly, I can understand the sentiment behind these types of talks, but they don't really say much of interest. Everyone hates the problems with whatever they're working with - thirty years ago, stupid server issues, slow hardware allocation and spin-up, and routine system updates sucked. Now we complain about cloud providers APIs, kubernetes, and whatever the newest tech is because we have to use it.
What's really important, and something Hariri barely touches on in his presentation, is the tradeoffs of when one technology or language or paradigm's benefits and drawbacks outweigh their alternatives. Sure, dealing with kubernetes deployments can be a pain - but I bet it's better than having to call your in-house hardware guys and ask why DSC-PROD-11 isn't working.
Complaining is easy. Solutions are hard.