TBH reviewing PRs on VSCode's Pull Request extension works pretty well for me.
I agree it is a bit slow but I get to see the changes with all my keybindings, themes and other tweaks, this just makes the experience better IMO.
I use TickTick to manage my daily tasks, it also comes with a habit tracker and you can even set reminders for your habits, for ex. Workout time, diet check, meditation time, everything is synced to cloud and the free tier has enough features for a normal user. Moreover the pomodoro timer and time tracking features it offers are a plus and it just gets so easy having all these features in a single application.
Why is all of this implemented in SQL? Wouldn't it be better to do it in code with dedicated methods to filter stuff out? IMO logic inside of SQL queries just adds unnecessary complexity, implementing this in code would've been maintainable and testable.
Boss: "Hey Bob! People started spamming one of our boards, we are currently busy doing other things and cannot deploy new client, can you make filter with these 3 words and deploy it ASAP?"
Bob: "Sure no problem if it's only temporary"
--few months later
Chief architect:
"People are spamming more and more, we should design new system for these 234 new bad words, I need team of 7, two backend guys, 5 frontend guys and 4 weeks. It will also require minor rewrite of few external components."
Boss: "geez we're in the middle of sprint right now, Bob can you add these 234 words to existing filter? Make sure it's in production before lunch, thanks" (checks watches) "I have to go now, meeting with customer, bye".
It is FUNCTIONS so it is code like any other. Even SQL is code (declarative).
The reason is: This can be updated very easily and out-of-band of other deploys of the main application code.
To make this work it has to be super agile to update. Probably this version we are looking at is an old version that happened to be put in git. The functions in prod probably have several additions since.
> I work at a job
> I got fired
> If I'm skilled enough I don't think it would be an insanely hard task for me to find another job.
Recession is another thing but general layoffs can be fixed it you decide to pick yourself up.
I've never been much for following courses and really the best way to learn is practice. Working with a cloud stack like AWS is a great start. Try to setup a an app server behind a load balancer, CDN (Cloudfront) and DNS (Route53). Read up on VPCs, what a CIDR block denotes. The core functions of these kinds of appliances is actually really simple. Just routing, caching and occasionally transforming requests. The ins and outs of specific products (ie CloudFront vs Cloudflare) is going to most useful and you get that from reading product docs. That and learning to use command-line tools like curl, dig and maybe tracert if you're feeling fancy.
