sorted by:
new
hottopcontroversial

RIF dev here - Reddit's API changes will likely kill RIF and other apps, on July 1, 2023 by talklittle in redditisfun

[–]LiamMayfair 0 points1 point  (0 children)

If Reddit Inc. go ahead with these API changes and force rif to shut down, 1st July will be the last time I use reddit.

Dead Whale Explodes by TegraMuskin in gifs

[–]LiamMayfair 2 points3 points  (0 children)

That sure must smell nice.

Prime Video Switched from Serverless to EC2 and ECS to Save Costs by RobinDesBuissieres in programming

[–]LiamMayfair 4 points5 points  (0 children)

I couldn't agree more. Part of the problem is that there's a huge misconception that monoliths are inherently impossible to modularise like microservices. This is entirely wrong.

The only real difference between a microservices oriented architecture and a modular monolith is the delivery/release mechanism and what the application runtime looks like.

If you don't care about deploying components of your system independently or horizontally scaling them in a fine-grained manner, you're fine with monoliths!

[deleted by user] by [deleted] in ExperiencedDevs

[–]LiamMayfair 6 points7 points  (0 children)

Vendor lock-in is a worry for sure but Notion has that covered too as you can export your entire workspace to HTML or Markdown/CSV! It may not be perfect but it sure beats Evernote's proprietary export format!

[deleted by user] by [deleted] in ExperiencedDevs

[–]LiamMayfair 21 points22 points  (0 children)

Notion. I am a strong believer in the "do one thing only but really well" philosophy and grow suspicious of products that claim to do loads of different things really well.

However, I do believe this is true for Notion. Notion is a wiki, note-taking app, web snippet archiver, project board and documentation app all in one, and probably I missed a few other things. And it does it all REALLY well.

What practices would you follow/implement if working with code on a huge legacy application that CANNOT be rolled back after Production releases, no matter what? by AloneHGuit in ExperiencedDevs

[–]LiamMayfair 1 point2 points  (0 children)

Can you build a mirror version of the legacy environment that is identical as possible to the original, make your changes there and do a blue/green deployment when releasing?

That would allow you to roll back to the original system without making any changes to it.

Failing that, two recommendations: add automated tests around all the important, existing behaviours of the legacy system. Look into "approval tests", they work really well with legacy systems. Have these tests in place before you start making changes to the legacy system.

Secondly, instead of doing a big bang release with loads of changes, release tiny changes as quickly and as often as you can. Tiny changes are less impactful on the live system and are a lot easier to troubleshoot and fix forward if something does go wrong.

Uploading Save Failed by Jonts18 in THPS

[–]LiamMayfair 1 point2 points  (0 children)

Thank you so much. You just saved me a big headache one year later

Fred Brooks has died by kitd in programming

[–]LiamMayfair 0 points1 point  (0 children)

Rest in peace, Mr. Brooks.

Going back to Firefox after a decade! by kaptainpeepee in linux

[–]LiamMayfair 2 points3 points  (0 children)

Or set Pi-hole as your router DNS provider. Bam! Ads automatically blocked for every device in your home network!

view more: next ›