Love the pronunciation section, it’s settles nothing.

These statements can sum up most of what happening. Companies are always trying to make number go up. Ai is the new fad and they feel that if they don’t use Ai, their number won’t go up as much as their stakeholders expect it to. To not look bad to their stakeholders they jam in Ai anywhere they can fit it, but they don’t know what Ai is or how to use it. I believe this is the case where the how to use it is known however it is a shit tool that codes badly and does not actually understand code, just what is the most probable token to output next.

You are telling me that you can’t proof of concept something without a matching tech stack? Or learn exactly how a new tech works? It also sounds like you should never give your work any of your personal time, you won’t gain anything except for more work.

I think it means they setup new tech on their homelab to learn how everything works and how to break it. Then when a problem arises where one of these solutions is needed at work, you can implement it without any large issues. It makes sense if your hobby is close to or adjacent your day job, and you are on Salary, and your boss treats you right.

Legendary, I love the idea but sometimes I rely on the models stupidity. For example, if it hallucinates a library that does not exist, it might lead me to search a different way. Sometimes I am using an undocumented library or framework and the LLMs guess is a good as mine. Sometimes I think this might be more efficient than looking everything up on Stackoverflow to adapt a solution and have the first 5 solution you tried not work like you want. What is a less drastic version?

Your name is amazing

Ask Steve why he was working on my feature branch. Steve is not a smart person. He also built a feature that another team was working on, over a weekend and implemented it on Monday morning. The feature was already finished on Friday and the PR was waiting for approval. While 10x devs work fast, they create 10x the work for everyone else. He no longer works here and it turns out he burned every single team with shit like this. It is so hard to get rid of someone who can work fast. When upper management is convinced someone who is productive and smart can do no wrong. They ignore the fucking carnage they create.

I wasn’t going to get into the whole lossyness of the formats and just simplified to full image instead of compressed formatted. That is interesting that it is only saving 20%-40%. I was under the impression that the page only rendered the image size necessary to fit the layout and not the full resolution image. Forcing it to less lossy or lossless would mean that the larger image would always be available to be served to be rendered without any web request.

Maybe this should come with a warning. The purpose of WebP is to quickly serve images to the user without grabbing the entire image data. Without WebP all images will be fully loaded, in the right conditions a page could load real slow.

I can’t swear or reference other team members anymore, it was considered hostile. Fuck Steve, trying to get his git numbers up by running a linter on my feature branch while I am developing the branch. Now I can’t fucking quickly read the code, it is a mess for a reason, it is temporary. I hate Python for this, I come from C++ land and need my whitespace.

Some models hide their reasoning all together, but at the end spit out a summary of their reasoning. Its useless.

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.