4 ms·

I agree with most comments here. Just wanted to highlight this is not just a "frontend" thing. I'm seeing the same thing happening in the backend (when overcomp

by midrus 5y ago

I agree with most comments here. Just wanted to highlight this is not just a "frontend" thing. I'm seeing the same thing happening in the backend (when overcomplicating everything with Elixir or Go, etc) and infrastructure (Kubernetes, etc...) for what would be a single landing page or a very minimal "CMS" kind of site that with Rails or Django you'd be up and running in less than a week. Instead we spend months with "modern" stacks. Worst part is these stacks have a HUGE amount of custom glue code and what happens is that people eventually leave the company, leaving new joiners with a system which is impossible to understand in a reasonable amount of time. So these new joiners call this old system "legacy" and back to the start. Where if you had used a simpler, well documented, well tested, opinionated, popular solution (rails/django/laravel/etc) you'd at least have a good baseline despite any mess developers could create on top of it. At my last job I was horribly looked down at when suggesting doing simpler things. People want to master a single gold hammer and use it for everything, no matter what the business problem is. React is THE WAY, Go is THE WAY, kubernetes is THE WAY and now it doesn't matter (we don't even think about it!! what's the actual f**ng business problem we're trying to solve). We just use THE WAY tools because otherwise we're doing "legacy". It's sad, really sad.

tcbasche 5y ago
> documented, well tested, opinionated, popular solution The problem I found is when less experienced developers build hacks in and then all of the above attributes fly out the window. All the custom glue code kinda renders the use of a framework more of a hindrance. But yes, fully agree. Don't start with the technology, start with the problem that is to be solved.
- midrus 5y ago
  I just don't want to imagine what a developer that makes a mess out of something built with Django, rails, Laravel, etc would do with custom tied together libraries (node, go, flask, etc...).
  - tcbasche 5y ago
    I think it's worth noting that a developer like that comes from a combination of poor management, poor leadership and an inexperienced team. I would say it's almost rarely their fault (emphasis on almost) and we could do better to educate better principles on software design and structure. Although maybe we're already trying our best, who knows.

by midrus 5y ago

tcbasche 5y ago

> documented, well tested, opinionated, popular solution The problem I found is when less experienced developers build hacks in and then all of the above attributes fly out the window. All the custom glue code kinda renders the use of a framework more of a hindrance. But yes, fully agree. Don't start with the technology, start with the problem that is to be solved.

midrus 5y ago
I just don't want to imagine what a developer that makes a mess out of something built with Django, rails, Laravel, etc would do with custom tied together libraries (node, go, flask, etc...).
- tcbasche 5y ago
  I think it's worth noting that a developer like that comes from a combination of poor management, poor leadership and an inexperienced team. I would say it's almost rarely their fault (emphasis on almost) and we could do better to educate better principles on software design and structure. Although maybe we're already trying our best, who knows.