Next.js is pretty dope when it comes to frontend work. Image optimisations and SSG/R just to start.
But, the backend portion of Next.js isn't great. You're given the request and that's it. So, I made a library to make the pain go away.
https://t.co/W923yvyKAw
Have you ever wondered how a Staff Engineer approaches the dreaded algorithm interview?
Check the image to preview my post, where I break down my process step by step.
You can read the full post over here: https://t.co/6SmtFFgK31
@petecodes I found the blue light coating to alter colours a bit when I was doing design work/work that depended on colour accuracy.
I chose to get new lenses that didn’t have the coating for that reason.
@TomFrankly@levifig Git is the way to do this, as others have said you could use the keyboard shortcuts in VSCode.
Or, if your using the terminal you could create a custom function that commits, pushes and pulls and pop it in your bashrc/zshrc on both computers.
@tdinh_me As someone trying to break into the scene, absolutely. I’ve got enough time and experience to do it, but getting a leg up and helping others would be perfect.
As someone who doesn't have a computer science degree and is ignorant of a lot of computer science _stuff_ beyond the basics. ChatGPT has been a game-changer.
It just taught me what a Trie is and how it can be used for route matching in web services.
I breezed over this last year, but I managed to make my first freelance sale.
ARR is at a blazing $300.
Having a job you hate is incredible motivation.
@keithpitt Coming back to this, after giving Hyper a go for a few weeks I'm going back to Iterm2.
I missed some smaller bits, such as `cmd` clicking on link and cmd+shift+enter to make a terminal split window take up the whole window.
@keithpitt This is pretty much the same boat I was in a few weeks ago.
I've given Hyper (https://t.co/4erj4da5dW) a go and have really enjoyed it thus far.
The special pattern you’ve established that exists only at your company and works with your special bespoke library will likely create maintenance overhead, slower onboarding and be blown away in a few years.
The past four months have seen me swapping back and forth between typescript-based cloud functions triggered by PubSub events and traditional Rails APIs.
Guess which one of those has been easier to pick up, maintain and introduced less complexity into our codebases?
Don’t get me wrong, Rails, REST and co. have a lot of foot guns built in. You can certainly still make something complex and unmaintainable with them.
But I guarantee that predictable, industry-wide know patterns that have a history of performing well will continue to do so
The amount of time I’ve lost to configuring, debugging and bashing my head against the combo of jest and typescript is too high.
Does anyone know any legitimately useful alternatives to jest?