> why you're not getting the results that a lot of us are talking about?
IMO the problem occurs when "the results" are hyped up linkedIn posts not based in reality, AI is a boon but it's not lived up to the "IDEs are a thing of the past, youre all prompt engineers now" expectations that we hear from executives
I spent the last 18 months unemployed and on WA "Apple Care", wasn't terrible, got me into the doctor for an ultrasound and into the dentist for an extraction at no cost to me.
Location: Bonney Lake, WA
Remote: yes, please
Willing to relocate: no, thank you
Technologies: Typescript, React, Node (and lots of the associated tooling and libraries)
Résumé/CV: https://bit.ly/3JI3Pq0
Email: (see resume)
~8 years experience frontend development (with some fullstack mixed in)
~8 years experience systems & network administration
I'm Don, an experienced frontend developer seeking a role working with Typescript and React/Node. Capable full stack and familiar with servers and networks. Passionate about my craft and personal growth.
barely related but I used to commute 60/90 minutes for an entry level tech job in orange county (I lived inland where it was more industrial and was chasing opportunity). Sometimes we'd have client network outages that left us in office until late night/early morning, twice I tried to sleep at the office instead of driving home.
first time was in my car and was kicked out of the parking lot by security, I probably should have protested more
second time was curled up against a wall in our equipment room, and the poor cleaning lady let out a shout when she discovered me haha
on one hand a company hotel seems kind of perverse to me, on the other its cheaper than the super 8 was in 2010, and I probably would have taken a $99 room over the commute every now and then
Large employers in Germany will enforce the max 10 hour rule for non-managers not from the goodness of their hearts or because they don’t want to be stuck paying overtime, but because here, they have a good chance of having at least some of the liability if you are involved in an accident.
When my skip-level’s boss spotted me in the office at 7pm during a very serious outage, and told him that I’d been there since 6, he commended my efforts and insisted I take a cab home and have them bill the company directly, no matter how far away home was, and stated that I was under no circumstance to set foot on company property before 8am the next day, and that I needed to have at least 10 hours between arriving home and leaving for work the next morning.
From a front end perspective I think the selling points I see pitched for these new server side frameworks are "SEO" and "speed".
SEO I personally think is a questionable motivation except in very specific use cases.
Speed is almost compelling but the complexity cost and all the considerations around how a page is structured (which components are server, which are client, etc) does not seem worth the complexity cost IMO. Just pop a loading animation up in most cases IMO.
I think I'm stuck somewhere in the middle between old-hacker-news-person yelling "lol were just back at index.html" and freshly-minted-youtube-devs going "this is definitely the new standard".
I think it makes sense in the "beer is tangible" and "speech is not" sense (to my brain anyway). If I saw a "free beer" sign in a window I'd probably be inclined to think (albeit suspiciously) that there might be a frosty mug inside at no cost to me. Whereas if I saw a "free speech" sign, I'd assume they support my right to say whatever I want (or I suppose maybe that there's a lecture going on inside with no admittance fee).
We all got different brains though, shoutout learning from others perspectives, ty for sharing yours.
IMO the problem occurs when "the results" are hyped up linkedIn posts not based in reality, AI is a boon but it's not lived up to the "IDEs are a thing of the past, youre all prompt engineers now" expectations that we hear from executives