

Seriously speaking, what is option B? Start new projects in Svelte? Go back to angular or vue?


Seriously speaking, what is option B? Start new projects in Svelte? Go back to angular or vue?


I am pretty sure the whole thing uses React. You know, the framework created by Facebook.


Azure is everything but the Zeppelin and the hydrogen. It’s the factories, the maintenance facilities, and refueling stations.


I have the perfect module to use this once. Most people will see it and will figure out that it is doing what it should, but no one can change it because the file will be LFS locked like 99% of the time.
I look at it differently, everything used to be hobbled together messes without real consideration for running live. Then when you go to scale, you had to redo the whole thing because it’s base architecture was garbage. This is going to sound dumb, but the philosophy behind DevOps creates an environment that encourages building extensible systems that hopefully will not require taking a fucking sledge hammer to the systems to upgrade when you get users. My role in particular would require time from a dev from each team and a SysAdmin that understands software and OS at a low levell. That is really inefficient and has communication gaps.
Most DevOps spend our days designing and coding. We are deeper into architecture than anyone else, the dev team does not even consider deployment and uptime. We have to go to each separate teams meetings because our input is needed for many decisions. I had no idea that it was like this when I got into it.
When I was a Sysadmin at a MSP, we had client with 2 main sites and multiple satellite sites. At one of the satellite locations there were two servers. The first ran a bunch of VMs and the second was the backup. If you disconnected the backup, the AD stopped working everywhere and half of the NAS storage was not reachable. As a far as anyone knew the second server was set to spin up replacement VMs if the first went down and nothing else. We were a pretty shitty MSP and never spent any time doing proactive work. So when that server dies, that company is going to have the most epic outage that will cost them a fortune.
I have been thinking about this and there are 4 messages I could receive that would illicit a similar response. I would ask if the system is down and if it is up, I have 2 people that would be forced to take the day off. Mainly because they never read any documentation throughly and can’t follow instructions.
Add something like NvChad to Neovim. The amazing thing with Neovim is that everything is custom. You can have your IDE if you want.


Nope, it is simply because they are overwhelmed. Either it’s too much work to do after your day job or just too much work for one person.


It’s all legal including the massive amout of corporate Socialism required to unfuck this.
There is no right answer. The only hard rule i have is that if it only requires key-value pairs keep it real simple. I use a variety of databases and things I can used as a database. One project uses Google sheets. Another uses a bunch of CSVs on a NAS as document oriented type database. And then there are the usuals; SQLite, MySQL, PostgreSQL, Mongo, and some god awful MS Azure crap that uses KQL.


In game dev, a binary file conflict means someone is going to have to do their work a second time.


The Amish/Mennonites are so close to Islam that if they didn’t reject other religions so hard they would be best friends.


One day we are going to lose an unbelievable amount of information, but do you know what is simple to archive and bring back, a simple form from 2005.


I have made worse, I used to do a cascading merge everyday to move stuff from dev branches to staging to production. Then I did a merge in the opposite direction for a small selection of branches so they could get their updates from staging. Feature branches were rebased as needed.


“During the gold rush, sells shovels model” Is a perfect analogy. It worse, OpenAi and similar companies don’t find using any sluice machines profitable. It is basically a gold rush were even the big operations don’t want to be involved with anything, other than selling shovels. This bubble is going to burst and there is an unimaginable about of money invested if this scam.
Undocumented feature flag in a plug-in, that changes the behavior drastically when in any deployment mode.


Don’t. Unless you are confident you are not adding hot garbage to the code base.
Remember that most hacking is not done by breaking encryption and running code. It’s %100 social engineering. The weakest point is always a person.