I am currently looking for a new full-time remote position!
With 11 years of experience as a back-end lead engineer (not full-stack), I am specialized in Node.js APIs and CLIs.
Most recently I have been Netlify Build's and Netlify Plugins' technical lead for 2.5 years.
The demise of #Jamstack and #Netlify as an indie-first, "static site" hosting company feels like an end of an era. But why did it have to happen like this? Where did things go wrong? And which companies can #WebDev folks turn to for streamlined, pragmatic web hosting and architecture?
Here's my take on it, serving as a reply of sorts to @remotesynth's excellent coverage of the topic:
I’m sorry to hear the news of layoffs at #netlify. I’ll boost any looking for work posts I see from former Netlify employees. I hope everyone looking for work lands on their feet soon 🙏
Moving my websites from #Netlify to a traditional (and local to me) small legit non-VC business brought a lot of positive vibes, and a realisation.
Once again, Silicon Valley had convinced me that convenience should be the path to do more tasks in less time. As in growth at all costs.
But designing for the web is not like using a machine to wash the laundry. It’s more like cooking: takes knowledge, experience, a bit of artistry. Also, it takes the right amount of time.
We noticed a naive attack on our websites the morning, attempting to exfiltrate #netlify env vars.
Because our websites are simple docs websites this was largely pointless and we have no reason to assume anything valuable got stolen. We still took precautions and rotated all of our keys & credentials.
Many others were similarly attacked, and after we informed #github security, the user account has been suspended.
Woohoo! I got my automated daily build to work for my website (#Github > #Netlify). I have a few other kinks I'm still trying to work out with some markdown plugins, but I'm sure I'll figure it out. #11ty#eleventy#blog
Can anyone working at #Netlify comment on the current discourse regarding small hobbyists with static sites having to unexpectedly deal with huge, sudden bills?
Buuuuut… seems unavailable on free plans (just checked on my "team" and individual site), so the $104k bill catastrophe is still a possible scenario… that's a bit of a disappointment.
And is that an AI-generated voice in the video? Very weird cuts. 😅
@chriskirknielsen I do wish netlify had another tier a little way above free. One that boosted a few things marginally, like build minutes, form submissions, and something like this rate limiting. Like a fiver a month.
#netlify doesn’t send a confirmation email (or even show a success page!) when you delete your account. Fucking yikes.
If someone got access to your account, they could delete it and you wouldn’t find out until later!
There’s no record that you deleted your account, e.g. in the event that they keep billing you and you need to prove you don’t have an account there anymore
I suspect the #netlify people are happy that every free tier site owner is dropping them like a hot potato. No need for slow enshittification and shutting down your free tier when you can just scare all those freeloaders off with bankruptcy and penury.
Because of the Netlify controversy this week, I’m starting to migrate some of my websites to regular ol' shared web hosting at Porkbun for the time being. It probably won't be a permanent change, but it's a step towards reducing my reliance on VC-backed third-party services that have extreme amounts vendor lock-in.
I wrote a blog post about my move from Netlify to Cloudflare Pages and how I use caching with GitHub Actions to speed up my Eleventy build step from over 14 minutes to just 30 seconds.
So I'm going to assume Netlify isn't going to suddenly charge me the cost of a small house if something goes awry and stick with them for the time being.
Also ooo, they're launching a new shiny. Blobs? Can I finally code up a working hit counter?