221–230 of 292 posts
* "Optimized for Programmer Happiness"
* The Principle of Least Surprise
The knowledge you gained 10 years ago is still applicable, language/framework is not going anywhere soon. I kinda love what I do.
Shameless plug - my Ruby book https://leanpub.com/rubyisforfun/
I call this the "path to enlightenment." You have discovered that the most popular toolchain is overkill for 95% of the things its used for. The problem is that's true literally across the board. You move to the backend and you have to deal with people who fell in love with microservices and weird databases that they didn't need. You move to ops and you have to deal with k8s when a single container would do. If you t…
> Why does this happen I wrote up my hypothesis here: https://hasen.substack.com/i/52275953/why-the-situation-pers... Basically, programmers love complexity. If they can't solve real problems, they will create fake problems so they can solve them. They might not realize that's what they're doing. Programmers love solving puzzles. It's why they program. The problem arises when they can't solve the real puzzle due to l…
People who don't see the existing solutions as overly complex are content to stay at their current level and have no vision of solving bigger more difficult problems. They think they are already working at or near the peak of human possibility.
don't use tools just because it's popular but make your productivity plummet..
Earlier quoted context omitted.
I still work on a Django monolith and agree on being able to focus 100% on business logic. I've found Angular is excellent for "sprinkling" a little JS into the frontend where necessary rather than going the full SPA/React route.
I worked on multiple Django monolith projects in the past years where parts of it with heavy client-side logic were offloaded to tiny Vue.js applications injected into the html template. If data requires reloads or manipulations a side restful api needs to be created along the main endpoint which renders html. But it's fairly straightforward with DRF and the enforced by default apps/models structure of Django. Until…
I feel your pain. My career happiness peaked around 2014 or 2015, when I was writing Rails monoliths. I felt like I could focus 100% of my energy on business logic since the framework was so opinionated and the stack was simple. Things went rapidly downhill after that, once microservices, SPAs, node.js, NoSQL, and serverless computing started becoming popular. Everything just felt like a step backward. Microservices…
Spot on. Rails just let you get shit done. All we needed was a Rails for Node.js.
Using React with an API back-end is only 1 of many choices. There's tools like Hotwire[0] and htmx[1] (both are back-end agnostic) that will let you create good old boring web apps with any back-end language where you don't need to write a ton of JS. You can sprinkle in front-end quality of life enhancements as needed to make nice feeling web apps with reasonably minimal complexity. [0]: https://hotwired.dev/ [1]: ht…
Don't forget Unpoly: https://demo.unpoly.com/
no such thing as frontend development. only full stack. and react for all the trillions of words written about it, what can you actually do with it? not much. also it's over-saturated as hell. you think there's high demand, you're right, now try applying for a position and see how it goes. there are two types of roles in modern web dev: 1 .90% of jobs are code monkey work: extremely saturated, you are competing with…
It’s crazy and impressive how we devs created this fucking huge industry where hundreds of millions was spent to solve a problem that didn’t really exist and actually made things harder and more expensive.
no such thing as frontend development. only full stack. and react for all the trillions of words written about it, what can you actually do with it? not much. also it's over-saturated as hell. you think there's high demand, you're right, now try applying for a position and see how it goes. there are two types of roles in modern web dev: 1 .90% of jobs are code monkey work: extremely saturated, you are competing with…
Come on now. With modern flow, you have to "install git", but in ye olde times you don't install svn or ftp? And back then we didn't have gatekeeping seniors? And we request sudo now, and not back then? I think you got that confused. Old software sucked a lot, and automation sucked a lot. Weird issues where you HAD to know what went wrong, because handholding was looked down upon. The lack of automation meant that se…
I was talking specifically about React. But it's not a surprise that "modern front end" devs conflate React with JavaScript.
I was thinking the same thing recently. I’ve finally realized that React is painful and overly complex. I just followed the crowd and got too deep. Backbone was elegant and simple. I could step through all the code being executed with my debugger. React is impossible to step through and the error messages are still terrible. It’s like an entirely new programming language and runtime. This “it’s just javascript” bulls…