There are thousands of Java developers in the US who make $80,000 a year and live a fantastic life. No leetcode, no Bay Area, no FAANG. Just people writing the code responsible for our banking, travel, supermarkets and many other systems which underpin our society.
$80,000 is hardly the measure of a true professional these days surely?
The silent majority in software
341–350 of 371 posts
Re: The silent majority in software
#342Earlier quoted context omitted.
No, I think that's very wrong, now more than ever. What you read "on the internet" is almost always fabricated and published with manipulative intent and asymetric capabilities to promote a product, lang/skill, or whatever. It's the negative comments you should care about.
Exactly : troll farms, astroturfing and Sock Puppets are a thing. Not being skeptic in 2022 of comments or news online is being very naive.
I simply forget. Maybe that's how they get you. They wear you down.
Re: The silent majority in software
#343I may belong to that silent majority. I have learnt a lot from the discussions here in HN and other sites, but I rarely participate on them. This post made me think about being a little more active because, sincerely, most of the times it is just laziness what prevents me from commenting anything. In fact, this is my first comment here in HN. Little by little.
Not commenting is a superior personal strategy. I've always been the vocal outspoken critic. XML, EJB, annotations, aspects, ORMs, everything JavaScript, agile, ad nauseum. (My non-technical list is way longer.) It's always cost me. I really wish I could tell young me to just smile and STFU.
Re: The silent majority in software
#344Earlier quoted context omitted.
To me what youre writing sounds like a parody given the context. And I feel like I could write a form webpage with a logo in significantly fewer characters than used in your explanation for why you need all that stuff. But this isnt my field of expertise so I'll have to take your word for it that you're not joking.
Like I said, doing a form is just a few lines of HTML in a tag (assuming you have a cooperative server that isn't expecting anything unusual and just digests POSTed form bodies). Doing a form that will do things people expect these days (client-side validation, formatting, error-handling and highlighting / locating fields with errors in them, auto-fill of addresses... What, you don't expect the user to type in a whol…
Re: The silent majority in software
#345Earlier quoted context omitted.
Feels pretty lined up to the amount of programmers who are skilled in writing compilers.
If I got a job in writing compilers I could becomes skilled at it. However I have a job in a different area. I doubt few as as skilled at writing the type of code I write as me, but the world only needs a few handfuls of people who write the type in the niche I'm writing code in. The world needs lots of websites, and so the world needs lots of people skilled in writing them.
What you do as your first job massively influences you career. I did .NET for years by the fluke that is what my first job did. If they did Java, I would be an expert in Java. If I worked somewhere they needed a compiler written in C++ I would have done it and may have a compiler career.
The paradox is as a graduate you generally, unless very exceptional or well connected, or live in the (not "a") tech city, just need to get that first job.
It is hard to get that breaking opportunity, and so that thing that will have echoes throughout your career, you don't have much control over! The reason it is hard to get the first job is because it needs interview experience, and you have very little proof yet. You are asking a company to take that leap of faith.
Later side stepping is possible but very hard as you are competing with people who can be paid the same as a web dev with deep experience.
Also as a young person back then, I had approximately zero confidence, both in myself and even that programming is a good thing to do. Getting into it was very weird, I was probably the only person at my high school of hundreds who geeked out on electronics and programming, for example.
Nowadays with HN and other sites, there is an online community such that even in a country town you can get a sense of community and what is possible. With that any graduate now could hatch a decent plan for their career. They might take any job to pay the bills, but aim to get into a FAANG for example, knowing what it pays and how to go about it. 2020's are amazing.
Re: The silent majority in software
#346There's nothing quite like an author getting basic history completely wrong at the very beginning. Really builds confidence.
Do you mean the paragraph that was lifted almost verbatim from the first paragraph of this Wikipedia page? https://en.wikipedia.org/wiki/Silent_majority
Re: The silent majority in software
#347There's nothing quite like an author getting basic history completely wrong at the very beginning. Really builds confidence.
What color is the bike-shed?
Re: The silent majority in software
#348Earlier quoted context omitted.
I’ve been programming ~15 years, and from my perspective, those frameworks helped us move on from a world riddled with XSS, “better than fail whale”-level reliability expectations, and software ossification (Gmail, Facebook, etc). Today, the frameworks bite me in the ass about once a week, but I think it’s worth it to get safe React with strict TypeScript, and plenty besides. Caveat: All infrastructure requires a lot…
??? XSS has long been a solved problem. Security is definitely not an argument for using front end JS frameworks as they add attack vectors and complication to the stack.
Re: The silent majority in software
#349Earlier quoted context omitted.
Did a personal web project and chose TypeScript to see what the rage was about. I spent a ridiculous amount of time trying to design types. At some points I couldn't figure it out, or I ran into some limitation of the language to express what I need. So my code has a bunch of exclamation points everywhere to assert that a null ain't coming. It feels dirty. Just too hard to use for me.
What's so hard about designing types? I'm Java developer and when I need to use TS, I just write Java with it. Works fine. The only times I encounter weird types is when for some reason I need to read type definitions for some weird JS library. But that's relatively rare.
Re: The silent majority in software
#350Earlier quoted context omitted.
Such a saying is what the incompetent obsessively repeat to themselves. They can't stand by the thought of people who don't need an Internet connection to program, who don't copy and paste from the fools over at StackOverflow, and the many other things they do which their betters don't. The fools over at Reddit call some things "adulting", because the idea of growing out of childhood is so foreign to them that they'd…
> we’re all amateurs, and sometimes we can be wrong. > Such a saying is what the incompetent obsessively repeat to themselves. I'll take humble over arrogant.