1,355 karma · joined July 12, 2010
email: postit at mm.st
A low hanging fruit are spot instances if you can manage stateless sessions.
If you have multiple snapshots that could cost money as well
I use it mainly with feedbin. It works most of the time
https://www.youtube.com/watch?v=IH-grgRmClY
https://forum.pjrc.com/threads/54995-Zeus-Commander-SPS-16-M...
Therefore most feature code should be shipped to master with feature flags.
We have a huge DB cluster instead.
The issue is that now we have +10k people wondering about their future because they have bills to pay and a hard path ahead. Meanwhile, Galloway brags about how he was right during all this time and suggest massive layouts to save "investors."
I'm getting tired of this.
( ͡° ͜ʖ ͡°) - But still 99% of tutorials and documentation refer to the UI.
I pushed the teams implement user story mappings for each project and cut the fat to delivery it on time. The argument with the developers was basically around: "I know you want to plan ahead and put shine things on your resume, you can do that if you get the following 3 releases on first."
20-ish years ago was impossible to have an interchangeable application between two OS, without a huge effort on porting and adaptations trade off. Now we have the web applications running in a handful of different systems. We’re also watching the people theorizing supporting webassembly binaries directly in the kernel. If you don’t want to run a webapp you have virtualization to rescue you.
My last straw with Wine was when I bought navicat for Linux and they shipped a wine wrapped windows app. Really, some tech should just retire.