Live data from Hacker News

I completely ignored the front end development scene for 6 months. It was fine

rachsmith.com

101–110 of 162 posts

Re: I completely ignored the front end development scene for 6 months. It was fine

#101

Earlier quoted context omitted.

I agree with you in theory, but in practice, I find it really hard to get a job saying, "I'm acquainted with CS fundamentals." I once got bounced from a job interview for not knowing about a quirk of the newest XCode (less than a week old).

> I once got bounced from a job interview for not knowing about a quirk of the newest XCode (less than a week old) Sounds like they did you a favor. Who’d want to work for people like that?

> Who’d want to work for people like that

Recruiters, HR and interviewers often are nothing like the culture of the people you will end up working with.

Treat everything as a potential signal, but take care not to mistake noise for signal.

Also recruitment is often about reducing false positives (avoiding bad hires), at the cost of a high number of false negatives (failing to employ suitable candidates). Try not to take it personally when they give you a no for an obviously bad reason?!

Re: I completely ignored the front end development scene for 6 months. It was fine

#103
post #73

Earlier quoted context omitted.

Rust has a huge exposure in the programming community. I may not know how to write it, but I sure know what it is. It's not just limited to HN in awareness.

>Rust has a huge exposure in the programming community. And it's used exactly nowhere. Can you name one project that is rust based and isn't part of the rust toolchain?

IIRC some of the HTTP/2 or 3 server-side stack (I forget which) in Cloudflare is implemented in Rust.

Parts of Firefox are implemented in Rust.

Swc is a JS bundler written in Rust.

I agree it's not a super in-demand skill as far as job postings go, but it's not exactly completely unused either.

Re: I completely ignored the front end development scene for 6 months. It was fine

#104

Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…

> everyone is looking into trendy redux replacements now What's wrong with redux? I've been using it in my last 2 companies, it scales amazingly and I think that's one of the stack in react that I'm comfortable with

The pushback I've gotten is that there's too much boilerplate.

I really like the boiler plate though. Everything is very specific

Re: I completely ignored the front end development scene for 6 months. It was fine

#105

Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…

[deleted]

Re: I completely ignored the front end development scene for 6 months. It was fine

#106

Earlier quoted context omitted.

I agree with you in theory, but in practice, I find it really hard to get a job saying, "I'm acquainted with CS fundamentals." I once got bounced from a job interview for not knowing about a quirk of the newest XCode (less than a week old).

> I once got bounced from a job interview for not knowing about a quirk of the newest XCode (less than a week old) Sounds like they did you a favor. Who’d want to work for people like that?

I did.

The company I worked for was infinitely worse (literal Sociopathic management). The pay was better, it was closer to home, and the work was more stable. If I had to guess-- I'd say the existing iOS guy wanted a friend to be hired so he tanked me.

Re: I completely ignored the front end development scene for 6 months. It was fine

#107

Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…

> everyone is looking into trendy redux replacements now What's wrong with redux? I've been using it in my last 2 companies, it scales amazingly and I think that's one of the stack in react that I'm comfortable with

its global state with a bunch of ceremony. outside of things like the user session and feature flags its essentially useless and more error prone than its worth.

Re: I completely ignored the front end development scene for 6 months. It was fine

#109

Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…

I have encountered little to no adoption of GraphQL in the wild. It really never blew up the way anyone expected.

Re: I completely ignored the front end development scene for 6 months. It was fine

#110

Obsession with the latest frameworks and the proclivity to refer to someone as an "X developer" for some X ∈ {popular frameworks} is a sign of ignorance/immaturity, both for developers and hiring managers. Those with a solid understanding of the underlying principles (both computer science theory and, in the case of front-end development, the core web standards) are the best positioned to make the most impactful cont…

None of this is true. The latest frameworks aren’t just “trends”, like fashion. They’re improved ways of doing things. Better, simpler, more reliable. Advocating to use tech that changes slowly, or avoid latest frameworks is advocating being slower and less productive.

Frameworks are a spinning wheel that reinvent technology every 3-5 years. It only seems like an improvement because the people using and writing it are relearning the same lessons that their predecessors already learned, but are unaware of this.

There’s only so many ways to write a reasonable GUI framework. There’s only so many ways to do general purpose data stores. There’s only so many ways to handle events. There’s only so many ways to schedule load/threads/work. There’s only so many ways to build code. There’s only so many ways to do object/class/etc. inheritance. There’s only so many ways to do interfaces/contracts/whatever. etc. It’s the same patterns and trade offs over and over again, but if you’ve never much of anything outside of web dev you’d never know that.

The past 15 years of web dev is the story of young programmers racing forward, having never bothered to look at the past.

Post reply on HN