Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That argument is usually made by the kind of people who consider developer experience the most important part of software development. I'm on the opposite end of this spectrum: I couldn't care less about developer experience, user experience is the king.

Your users won't see your "write less code" crap and all your other "elegant" overengineered solutions that use 5 libraries for something that should be a trivial 10-line function. They'll see that your app is an unreliable resource hog that looks and feels like it's not from this world. And it's never finished. It's constantly updating but always broken one way or another. And they'll suck it up because there are no alternatives and most software these days is like this.

I'll do everything in my power to change this. It's my mission in this world. I want people to rediscover non-crappy software and have their minds blown by what modern computers can do when programmed by people who actually know what they're doing.



Be careful about the baby/birtwater situation. I can deliver a website a lot faster if I get to write it in typescript than if I have to write it in C++, even if the latter might execute faster.


There's a big difference between build-time and runtime dependencies. It doesn't matter what you use in your build environment, so yes, I do use TypeScript in my own web projects. It does matter a lot what you leave in your final product, so I'm never using react or any other JS frameworks.

I also use Java for my backend because not having to manage memory manually is worth of the small performance tradeoff.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: