Live data from Hacker News

Thoughts on the software industry (2022)

linus.coffee

31–40 of 86 posts

Re: Thoughts on the software industry (2022)

#31

> Ultimately those tools have to model reality, and to do that, we need an interpretation of reality. Conversely, reality slowly changes to be easier to model in software. When Computer says no, a user adapts.

Right, you're not wrong but... "No", you can't scan that box in Chicago, the system says it's in New York. The world state is invalid, not the system. Screw that guy just trying to do his job, right?

Gotta be careful with that attitude even though it represents some insight.

Re: Thoughts on the software industry (2022)

#32
post #3

Since the article jumps around a lot, let me add one more; Software is an amazing passion, but a terrible job. Imagine you love music, play the piano for hours every day, then once you grow up someone pays you a huge salary just to play. You're in heaven. Now imagine someone who loves classical music, but can't play. You see the fortunes being made by piano players, so you decide to learn. Which takes years of doing…

Write a job description.

Now consider it from a perspective of someone who hates the job.

They hate the job, right?

This works for any job.

Re: Thoughts on the software industry (2022)

#33

As someone who does play music, although not professionally, I don't really agree with the analogy that writing code is like playing music. You don’t expect to learn how to play the piano by reading a book, but you might expect to pick up a programming language or concept because you read about it. Really, it doesn’t work that way. You have to read it, and then use it and practice it and make a hundred mistakes, and…

The specific analogy with music isn't great, but it makes more sense if you step back and say that a large part of software is aesthetic rather than technical concerns.

[deleted]

Re: Thoughts on the software industry (2022)

#34

As someone who does play music, although not professionally, I don't really agree with the analogy that writing code is like playing music. You don’t expect to learn how to play the piano by reading a book, but you might expect to pick up a programming language or concept because you read about it. Really, it doesn’t work that way. You have to read it, and then use it and practice it and make a hundred mistakes, and…

It’s not about writing for loops, the practice is to get good at problem solving and algorithmic thinking. For loops are a means to an end, like writing letters on a page.

Re: Thoughts on the software industry (2022)

#35

> Ultimately those tools have to model reality, and to do that, we need an interpretation of reality. Conversely, reality slowly changes to be easier to model in software. When Computer says no, a user adapts.

Right, you're not wrong but... "No", you can't scan that box in Chicago, the system says it's in New York. The world state is invalid, not the system. Screw that guy just trying to do his job, right? Gotta be careful with that attitude even though it represents some insight.

I think the comment you're replying to is partially sarcastic or tongue-in-cheek.

Re: Thoughts on the software industry (2022)

#36

> Ultimately those tools have to model reality, and to do that, we need an interpretation of reality. Conversely, reality slowly changes to be easier to model in software. When Computer says no, a user adapts.

Right, you're not wrong but... "No", you can't scan that box in Chicago, the system says it's in New York. The world state is invalid, not the system. Screw that guy just trying to do his job, right? Gotta be careful with that attitude even though it represents some insight.

My understanding is this is how USPS packages with tracking can seem to teleport around the country. They accidentally get scanned for the outbound to somewhere, it gets caught while never leaving the tray, and they scan it back in.

Re: Thoughts on the software industry (2022)

#38
A word of caution for highly intelligent but otherwise regular (not well connected) people. The software industry is the most manipulated industry on the planet and in human history. If you work on any significant, high exposure project, be prepared for unimaginable political f***ery.

It's also one of the least meritocratic industries in existence because most big companies have monopolies and can afford to be extremely inefficient when it comes to software development. The bar is mediocre. You just need to rehearse your leetcode to pass the interview; beyond that, you just need to be very good in a tiny area. You will be so highly specialized in the minutiae of your role that basically you will be useless as a software developer. You better hope there exists an equivalent role in a different large company if you want to have any leverage at all in the market. Startups or any business which relies on efficiency and actual skills will not have any use for you...

Still, the biggest problem is just how easy it is for incompetent people to bullshit their way out of anything and the metrics that are used to measure performance are so objectively horrible that it would be better if no metrics existed.

I've been in this industry for over 15 years. Not sheltered by big tech. Careful what company you join because working for the wrong company can be literal hell on earth.

It is clear to me that this industry is still very new and almost nobody knows what they're doing. Most people who lead this industry are not equipped to do so. They just got lucky and now set the rules which are essentially arbitrary and change all the time because they suck.

It's not like Law or Medicine; these industries have existed in various forms for thousands of years and there is a lot of philosophy behind those. It's relatively easy to figure out who is a good lawyer or a good doctor. With software development, it's extremely difficult for people to do because there are many aspects to consider and almost nobody understands which ones are actually important.

Imagine being a really good surgeon with years of experience and a 100% success rate on your surgeries but the hospital fires you because one of your colleagues was jealous and filed a fraudulent complaint claiming that you don't hold your scalpel in the approved way. Without metrics to accurately measure individual performance, everything becomes political hearsay. It becomes all about stupid immaterial things and all the important stuff is ignored.

I hope this saves some people from suffering. I would not recommend this industry if you enjoy coding. There is a non-trivial chance that you will be a life of pain. Especially if you are skilled.

I have met some top engineers who were so bright, passionate and were pioneers in their area and ended up miserable and brought to the edge of insanity. If you don't have deep social connections to this industry or intelligence agencies or other entities that can give you an insider's edge, stay away.

There are many stories about software devs who ended up retiring from Microsoft or other to be goose farmers or similar. These people are not eccentric; they are rational... And these are the lucky ones.

You don't want to know what happens to those who got trapped in this industry, got their passion for coding completely beaten out of them and can't find any off-ramp.

Re: Thoughts on the software industry (2022)

#39
Programming is so different than software engineering, to the point some people (like me) love the former but little by little are starting to hate the latter.

Learning for the sake of learning, being able to be picky about what to learn, feeling like a god by creating your own worlds, trial and error… these are all traits of programming. On the other hand, software engineering is about sprints, useless deadlines, using the wrong tool for the job, writing code to increase shareholders value, high-performing-team obsession, useless C-level execs, broken tech interviews…

Two different worlds.

Re: Thoughts on the software industry (2022)

#40

As someone who does play music, although not professionally, I don't really agree with the analogy that writing code is like playing music. You don’t expect to learn how to play the piano by reading a book, but you might expect to pick up a programming language or concept because you read about it. Really, it doesn’t work that way. You have to read it, and then use it and practice it and make a hundred mistakes, and…

I've gotten into the habit of actually reading the manuals for my synths and DAW after realizing I was missing out on lots of little quality of life things. I've used enough synths--and not just subtractive!--that I can usually pick a new one up in seconds, but the people who made it and the people who know it best contribute to those manuals and the stuff they share can lead to massive leaps in proficiency.
Post reply on HN