It’s an art to produce something that lasts long but doesn’t take years to build. Tech evolves rapidly.
415 karma · joined August 30, 2013
It’s an art to produce something that lasts long but doesn’t take years to build. Tech evolves rapidly.
AWS might be in the trenches of the biggest tech debt in terms of impact known to human kind.
How to solve this? I think lifecycle management. Define lifespan of services so that these can be replaced eventually.
Havent give this too much thought yet but it could work.
Since we have premium support (P1?), we had some internal azure postgresql engineer look at the issue and they pushed the problem back to us. Blaming our app not built correctly. That has been ping-ponging for over a year now.
Finally i saw this semi-acknowledgment in their health status yesterday.
Do you happen to know a proper solution? Are you waiting for them to fix this issue or moved to a different db service?
Perhaps the flexible server is better?
Crazy how our lives are becoming so dependent on private company techs.
And the funny thing? Status.azure.com is all green. No events in activity overview. No service health within the affected instance.
Workaround advised by azure? Upgrade to next plan. We already reached the maximum size. Maybe time for Citus . More $$$ for M$
How can this be a premium iaas/paas? Azure feels like the MS teams of tele conference. Companies buy in because they are already in the MS world. Not because azure is better.
I purchased cyberpunk combo pack few years ago. I wonder if the controller can be used on pc/osx for other games.
Anyone?
* macbook: at a desk or whenever/wherever it is accessible
* iphone: quick note pretty much anywhere like train ride
* apple watch: running, in the pool, during sauna session or in the gym weightlifting
* siri: while driving car or riding bike
These all end into a single inbox.
Unfortunately this requires full buy-in into the apple eco-system.
Did a quick look via street view. There are some very nice houses indeed. I might even say it’s the perfect location: golf course, beach and huge park adjacent to the neighborhood. These people will probably not actually visit the beach nor the park as these seem to be public areas.
The reason i’m raising this is knowing software is very complicated nowadays and are more susceptible for bugs. The other day my MS teams froze. I closed the app and tried to open it again. That didn’t work. It felt like i merrily closed the frontend while the backend was stuck. I remember the days a window was a task, closing that window terminates the task. These days are over. Somehow these softwares are made so complicated, not sure for what reason, that the likelihood of introducing bugs is increased.
So taking this frontend-backend example. Imagine the mute button just sends the command to backend for mute but the backend failed to do so. And the frontend assumed all was fine. The user would have been misinformed.
I would use the (hardware) button that stops the audio at the microphone level all the time.
If i would you, look for new opportunities elsewhere.