Live data from Hacker News

I no longer build software

github.com

651–660 of 891 posts

Re: I no longer build software

#651

Earlier quoted context omitted.

It goes without saying that your feelings are personal ones, totally valid, and nobody can really question them. I'm 20 years behind you, and I don't know what effect that will have on my views. But I don't really recognise the picture you're painting. Compared to the first steps I took as a developer about 15 years ago, almost everything about software development seems better to me. I find developing software to be…

I'm 20 years behind you Me too. And all I can do is point at Javascript in webpages. Which, as a Java dev (if I can still call myself that 15 years into doing all sorts of other stuff too), I want nothing to do with but somehow get dragged into all the time. I can really relate with the idea that we're feeding the beast we built rather than the one borne of necessity. Unfortunately, which I'm sure the latter still ex…

I'm at the end of my software development life cycle, but I've got the opposite perspective on java vs javascript. There's just so much boiler plate and unnecessary typing to implement solutions in java relative to javascript. The amount of stuff I can accomplish per line of code is significantly higher than any other language I've worked with, with possible exception being python.

Re: I no longer build software

#652
post #239

Seems to be a heavy "all modern software development sucks" vibe in this thread, when the issue is more "software I get paid to write sucks". What software would you write if you could write whatever you wanted using whatever language/technology you wanted? Unless all the joy gets sucked out beforehand, pretty sure I'm going to move to be developing Mobile Apps after I retire. It was the most fun I've had writing App…

> What software would you write if you could write whatever you wanted using whatever language/technology you wanted?

The sort that solves problems I'm interested in. I love the idea of treating software as a home-cooked meal [1]: something you prepare with love for a small crowd of people.

For instance, I added a recipes section to my personal website. I also added achievements to it some time ago[2]. Both were completely pointless, but I enjoyed doing it the same way I enjoy cooking.

[1] https://www.robinsloan.com/notes/home-cooked-app/

[2] https://nicolasbouliane.com/achievements

Re: I no longer build software

#653
post #317

Earlier quoted context omitted.

> Compared to the first steps I took as a developer about 15 years ago, almost everything about software development seems better to me. If you mean this is better, I hardly agree with you: https://twitter.com/thomasfuchs/status/810885087214637057?la...

Honestly, this IS better. Separating the HTML, JS, and CSS is an approach that works up to a certain size/complexity app. When I’m working on some functionality, I need to be able to understand the relevant parts of the HTML, JS, and CSS. With a smaller app, one person can more or less grok the code base well enough to find everything they need. With simpler apps, you might have fairly uniform or boring styling and n…

I agree. I came to realize a few years ago how arbitrary the HTML, CSS, JS separation is. It makes sense if you think of the web as simply a set of documents (with progressive enhancement and all that), but we've gone way beyond that metaphor. If you're building a web app, separating the three is cargo-culting.

Re: I no longer build software

#654
post #623

Earlier quoted context omitted.

Playing with legos is delivering value. Reinventing the same wheel over and over again is not.

What's often missed here is that the problem the lego is slotted in to is often subtly different each time. So you have a guy building an 8x2 lego brick that slots perfectly into his mansion and then someone else really needs to cut a corner off of it to fit their problem. But the original designer never gave you the option to do that so now you have to write an adapter to plug the 8x2 into an 8x2 without a corner. I…

I agree. You have to know your lego blocks well and understand where they fit and where they don't. But if you choose to remain ignorant of the available lego blocks, and instead write everything from scratch every time, you're wasting a lot of effort.

Re: I no longer build software

#655

Earlier quoted context omitted.

It goes without saying that your feelings are personal ones, totally valid, and nobody can really question them. I'm 20 years behind you, and I don't know what effect that will have on my views. But I don't really recognise the picture you're painting. Compared to the first steps I took as a developer about 15 years ago, almost everything about software development seems better to me. I find developing software to be…

I think you are right to say that the methods are vastly improved, but the ends to which those methods are applied have become ever more uninteresting (for a lot of people), and often morally suspect. We have built exquisite tools, but we use them to extract profit, to manipulate behaviour and often for no discernable purpose at all. Programming has become joyless. There are ever-shrinking spaces where a developer ge…

At least for me, this is exactly why I do personal projects. E.g., here's something random I did a couple weeks ago. It's so simple that it's almost embarrassing to post, but it's:

    100% vanilla Javascript
    no dependencies
    no cookies
    100% client side; no server side state, no ajax
    state is stored entirely in the URL
    state is correctly maintained across page loads (i.e. page edits its own URLs to maintain state)
    Javascript is 100% local, so it's instant and doesn't require any data fetch
    correctly detects a potentially spoiler-full page load by looking at the referrer (so it doesn't annoy you as you navigate around the site)
    ... and the entire thing is less than 100 lines of code
And it was surprising to me how genuinely fun this project was. I work on compilers/runtime systems for a living and I often get stuck in large code bases. I enjoy what I do, but working with a small codebase that's not massively overabstracted is just so fun.

https://exanderproject.com/spoiler-test/

The other thing that stuck me, as I was doing this, was how much the Javascript ecosystem has improved over the last 10-15 years. It was possible to do this in a very small amount of code with no dependencies precisely because of the all the bells and whistles that have been added to Javascript over the years. Maybe this isn't so obvious to someone who has been neck deep in Javascript for 15 years, but as someone who has been mainly in other languages, it was a very noticeable and dramatic improvement. The web platform is way, way nicer to develop for now than it used to be when I first got started.

Now I'm trying to figure out what other small projects I can get involved with.

Re: I no longer build software

#656

Earlier quoted context omitted.

I think you are right to say that the methods are vastly improved, but the ends to which those methods are applied have become ever more uninteresting (for a lot of people), and often morally suspect. We have built exquisite tools, but we use them to extract profit, to manipulate behaviour and often for no discernable purpose at all. Programming has become joyless. There are ever-shrinking spaces where a developer ge…

Not to mention that those CRUD apps have been done, exactly the same, 10000s of times before and 10000s of people are doing the same work you are doing now at this moment. Everyone thinks they are productive but value is being burned all day, every day in most companies all over the world. The level of reuse is depressing and people, especially here, firmly believe we need to use the latest frontend and backend crap…

> Not to mention that those CRUD apps have been done, exactly the same, 10000s of times before and 10000s of people are doing the same work you are doing now at this moment.

And yet now OP is making wood furniture, which has been made before the same thousands of times. Some people need originality some don't. Some just like the work for its-own sake. For those who need originality they should find a job working on something that's not a CRUD app. Not everything is a CRUD app. That's on them.

Re: I no longer build software

#657
All these complaining is funny. I was building software since the later 1990's. I'm not tired of it. Sure, most of the jobs out there are your standard CRUD stuff. But I still like it.

A lot of people complain about not having interesting stuff to work on in the day job. Well, that's why it's called a job.

I was burnt out from my software job as well until I got a shift in perspective. I picked up a photography hobby and got pretty good. In fact, I was seriously contemplating changing careers and was gaining steam. But I realized the more clients I picked up, the more uninspiring crap I had to shoot. This wasn't your everyday wedding or family photos. It was fashion photography where the industry was seen as more "creative" and "edgy." But once you get down to it, it was the same crap as any other job.

Sure I shot a lot of my own personal projects as well (like open source projects for software engineering). In fact, in that industry it's more required to have a huge portfolio of test shots where you're constantly evolving. In software engineering, that's not as required. But even that became a grind since you're pressured to constantly hone your blade while new, younger, more creative people were coming up.

Is it hard dealing with your manager, product managers, changing requirements, etc. in your software job? Well it's the same stuff in commercial fashion photography. Change their minds constantly. Sometimes I doubt they know what they want either. Budgets change, scope changes, a ton of politics, and so on. It's all the same.

This is when I realized I actually liked software engineering better. I found it more fun solving "boring" problems and learning the new technology of the day instead of hustling hard in the photo industry.

I get people complaining about not doing interesting work in their job. But that's what 99% of the industry is. You'll most likely create another CRUD app or work on stuff that is the least interesting to you. Only the lucky/elite 1% (just like in other industries) gets to do cool, interesting stuff.

Grass in greener on the other side. But I've stepped my toes on the other grass, and it's the same shade of green. I learned to enjoy my job as a software engineer. I'm in the 40's, and hopefully I'll have enough energy to keep it up for 20+ more years.

Re: I no longer build software

#658
post #15

Earlier quoted context omitted.

> It's not like any random software developer can go remote and compete with the rest of the world This is actually becoming more and more of an option. At my last (small) company, we hired several individual remote developers from various parts of the world that most would consider "third world". We were introduced to them via referrals from contract work done elsewhere, and we did a paid trial period at first. Not…

> > It's not like any random software developer can go remote and compete with the rest of the world > This is actually becoming more and more of an option. To do this though, you generally have to know how to market yourself, put together proposals, gather requirements, design and project manage, on top of coding. Not every coder is good at this or wants to be.

This is not necessarily true. In a large enough organization you can have a lot of that done for you, and you just basically "pull tickets" (to be reductive about it) and deliver the work.

You have to be able to interview well of course, but do design and project management? I'm not talking about a freelancer who delivers an end-to-end project here, I'm talking about hiring a remote developer to join an existing team and deliver features.

Re: I no longer build software

#659

Totally on board with not building software any more. In fact, at 55 this is my last week of it. For real. Basically, everything sucks more about building software nowadays more than I remember it sucking before, from the mere mechanics of navigating through an obscenely large pseudo-object-oriented codebase to the WRONG constructs/idioms people use to build distributed systems to the way software is packaged and dep…

> I sincerely feel bad for people who have to stay in it.

I'm in my 50s, and I've been getting paid to build software for over 27 years now, and started programming on a near daily basis on a TRS-80 in the 1970s.

Please don't feel sorry for me. I still very much enjoy building software.

I won't necessarily disagree with the particular challenges you cite.

The total complexity is enormous now, but the tools and abstractions, which themselves have variable quality, and bring their own complexities, are tremendously powerful, and, though it often doesn't feel like it, effective.

Beyond the specifics, I acknowledge that 'the industry' has evolved in many ways and directions, not all of which are positive.

I face non-technical challenges today that, had I known about them 30 years ago, would have probably caused me to switch careers.

So, I acknowledge what you're saying, and to it I will only add this: each of us exerts a great deal of control over how we perceive the world around us. It's possible that the difference in the way you and I 'grade' the software industry is that I am, for no knowable or particular reason, more fundamentally optimistic about things than you. It's also possible that, primarily for reasons beyond our control, I've ended up working in more positive organizations.

To other people reading this far: two specific anecdotes about how the software industry has changed over three decades provides very little concrete indication for how your personal experiences are likely to go.

Re: I no longer build software

#660
I still enjoy writing software. I mainly do mobile development on iOS.

However, after 20 years in the industry, I grow tired of the corporate life and how projects are run. I can't complain about the pay or the hours, though. I've managed to hold jobs that generally don't have crunch or any type of regular overtime.

What I grow tired of is the endless cycle of performance reviews, planning for the work ahead (short-term and long-term), discussions about what will be done and what won't be done, seeing how hard it is to come to consensus on some things, and how some of it doesn't even matter.

When you're younger, you have more of a fire in your belly and will passionately argue for certain decisions or directions, but after you've worked a while, you realize a lot of those things that don't make huge differences in how well your product actually does out in the field. There are decisions above your head that have greater effect and worrying about those is just a waste of time, and so you detach a bit.

The technical challenges themselves can also be the same ones you've encountered again and again, so that becomes sort of same-y.

As others have suggested, I highly recommend working on your own side projects if you are looking for a creative outlet. That's what I've ended up doing over the years and it's helped a lot.

Post reply on HN