111–120 of 162 posts
Earlier quoted context omitted.
As a back end Dev it looks like build tooling has largely materialized into a few choices and doesn’t change as fast.
As a firmware dev it looks like all yalls crazy
I hate javascript front-end stuff with a burning passion. I wanted to make a small widget, and somehow I needed 100+ libraries for this. The compilation/build/etc process makes no sense whatsoever, and I just type magic commands and hope it works. I am seriously considering just using something like blazor or phoneix live view so I can ignore front end entirely.
This feels like an incredible security problem to me. When companies like 1Password switch to an Electron client, I'm left wondering how many dependencies they have. How do they protect against some minor library change introducing a security flaw?
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…
As a candidate, I've "fired" interviewers that were just wasting my time asking me about googleable trivia. There are other employers willing to pay premium for experience over technology memorization.
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
Earlier quoted context omitted.
> 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
I enjoyed it while I used it but my main issues with it were with the developer experience and how many files the logic was spread across: actions, action constants, reducers, etc. When you have to edit 4 different files just to add a loading flag then I feel like something has gone wrong. If it solves your problems and you’re happy though, no need to let anyone convince you to change!
Also both of these libraries are from the official redux team.
Just a really happy user and has helped me tame the state problem.
Still running with simple Bootstrap themes, jQuery and mostly server side rendering and have thousands of users on my side project and lots of paying ones too.
Confident I could scale this to hundreds of thousands of users with no issue.
I've found the way to reduce churn the most is discard frameworks and DSLs whenever possible. This morning, I rewrote a page of frontend code for a scheduling webapp. I'd initially built it in TS/React years ago. Switched to Rust/WASM with a custom VDOM-based framework a year ago. I'm reasonably confident I won't rewrite it again in a new framework: the new page is an HTML document with an included JS script that per…
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've heard of a theory that says "A's hire A's but B's hire C's". The gist is that cream-of-the-crop interviewers actively look for open-ended-ness and the possibility that the interviewee may be better at things than they are, whereas less effective interviewers only look for people whose skills are a subset of their own (and by implication, design tests that only leverage the skillset they know, hence the "must hav…
I feel like this is a great bit of advice for interviewers and interviewees: for the interviewer, don’t ask about things that are easy to look up, and for the seeker, take it as a red flag if they do.
Earlier quoted context omitted.
It's also a big part of the hype cycle that is an actual industry with Patreon etc now. The first rule you should remember when reading HN is the real world is not HN.
https://veekaybee.github.io/2019/05/10/java8/ This sums it up quite nicely.
I don't see my previous employer (a Federal government) running workloads on K8s anytime soon.
However, I do hope they've finished their migration from Windows Server 2008 by now though (we started this project in 2018, but I left halfway through).
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
It's a bit bad if you try to add a bunch of extra shit to it unless you really need that shit (e.g. Thunk).
The terminology's kinda bad ("action" for "event", especially, which also gives us junk like "action creator") which can make it seem more complex than it is.
(I mostly like it, for the record)