Recently I got this DM,
“Which tech stack should I learn?”
“Should I use Next.js or Svelte?”
“Is Python better for the backend than node?”
I ...
For further actions, you may consider blocking this person and/or reporting abuse
Absolutely
I’ve seen some super technical teams with a lot of frameworks, good practices and time wasted in code reviews and so, deliver nothing, only wasting company money playing to be good engineers!! I totally agree with you ! Thanks for the post!
Do you think the technical temes has a responsibility to delivering the product?
Great post.
Some feedback: You need to differentiate hobby and professional software. This post needs more nuance. In certain contexts, I absolutely agree with it and others not.
If you keep asking the question "what tech stack should I use?" then you're in the phase of your learning that should probably just do something. Don't get stuck, just do something. Same goes for being a junior developer in a team. It's better to produce then to get stuck.
Creating clones and trying out tech stacks is exactly what hobby projects are for. Once you work professionally or you do something with the purpose of actually making money, go with what you know.
You don't need to upgrade every time but staying up-to-date with security patches is a must in a professional context.
Great insights!
Cool
Couldn't agree more, solving real problems instead of chasing the latest stack has always pushed me further - and honestly, it's way more fun that way. What's the most unexpected tech/tool you've ended up loving just because it solved a problem for you?
Still maintain a web app that runs 4000 requests a second (with mysql, solr and memcached) using a single server, on php.
The single server (which is mirrored and backed up, btw, so it has failover) is a 64 core ryzen. Using cloud, serving literally millions of requests in minutes would cost us so much that it would be bankrupt in a month. But this way, we pay a few thousand per month in server charges for probably 10 local content servers (that are synced using rsync) scattered over the world. Global traffic rank btw around place 500-600.
By now the single server is backed up by a second server that does some additional tasks, but the brunt is still covered by that one server.
Use what works.
But that said, you sometimes need to be able to anticipate. Do your best, don't take "it'll be fine" sort of shortcuts. Try to understand your stack, and that's easier when your stack isn't tall.
I had to write a lot of libraries myself, but now I understand them. This is good. They also only do exactly what is needed and nothing more.
Yeah Ive wasted way too much time stressing over tools before actually making anything. This hits hard.
Thanks! 😄
fr
True
Fullack
Solid men
Bold And Clear📝 Amazing
Right!
Facts
Quite insightful!
💯