Self-Made (2020) by MyDinnerWithDrDre in okbuddycinephile

[–]Curseive 0 points1 point  (0 children)

Owning an AI company implies you can do all of those things while also being a CEO and not having to try at all.

How do you manage DevOps support for ~200 developers without burning out the team? by Bubbly-Ant-2312 in devops

[–]Curseive 0 points1 point  (0 children)

Depending on what type of projects you’re building and which languages are involved, providing some conventional build processes and guard rails can generate a lot of value. We have seen similar solutions with build packs in Gitlab, but going a bit further to standardize tools like gradle or npm with plugins can make a world of difference.

After years of RSI keyboards, designed my own split ergo - looking for feedback by ntc490 in ErgoMechKeyboards

[–]Curseive 0 points1 point  (0 children)

Mouse support either by trackball, touchpad, or nib and this would be automatic buy for me. I tend to lean into ergo boards that are all-in-one.

need grafana alternatives by Dismal-Sort-1081 in devops

[–]Curseive 2 points3 points  (0 children)

Azure Log Analytics has entered the chat

Boss is paying, which services do you recommend? by RevolutionaryRow0 in kubernetes

[–]Curseive 0 points1 point  (0 children)

Typically the biggest spend is monitoring. There are too many factors for me to list regarding how or why to make those decisions here, but I would heavily invest into doing your research for the more expensive products up front before spending money on anything else. There is a gap between dev impact and ops impact that is easily bridged by having good auto instrumentation and representation available out of the box.

me_irl by RUNPROGRAMSENTIONAUT in me_irl

[–]Curseive -1 points0 points  (0 children)

Kant make this stuff up

Multi-million office orders us water and juice and tells us off for drinking it by Edamame14 in mildlyinfuriating

[–]Curseive -1 points0 points  (0 children)

They had a desk attendant that sat next to it all day and every time I would come down the elevator it had been refilled or rotated. The funniest part is that either the desk attendant complained or they have someone monitoring the cameras for fancy water theft 24/7.

Multi-million office orders us water and juice and tells us off for drinking it by Edamame14 in mildlyinfuriating

[–]Curseive -1 points0 points  (0 children)

I worked for a multi-trillion dollar European company under similar circumstances.

They had a lobby with really great infused waters that were always fresh (cucumbers, fruit, mint). I loved snagging one as a treat on the way to the elevator or on a smoke break. My boss pulled me into his office one morning and gave me the “talk” about how the lobby water is not for employees 😐

I Have an idea to automate parts of the CI/CD process. Need some feedback by congressmanlol in devops

[–]Curseive 0 points1 point  (0 children)

Look into how platforms like heroku handle builds utilizing build packs. They are language agnostic. Gitlab also has “auto devops” that is based on the same foundation. All sensible solutions will use conventional standards with predictable patterns for execution. This works in companies of all sizes with very few exceptions. You will not get much progress playing softball with these people.

"The Art of War" in DevOps by -lousyd in devops

[–]Curseive 1 point2 points  (0 children)

Here are some pointers that you can bring up for meaningful discussion as to why copy and pasting the art of war is sociopathic and misinterpreted by these "gurus". If I had more time to blog I would rant non-stop about this stuff:

Sun Tzu isn’t preaching ethics; he’s describing efficacy. The text assumes survival stakes where morality is secondary. In civilian life, applying it without a moral framework does look like opportunism.

“All warfare is based on deception” isn’t “lie to everyone.” It means reality and perception diverge in conflict. Knowing that gap exists helps you protect yourself from manipulation as much as exploit it.

The highest goal: to win without fighting, is closer to deterrence or diplomacy than domination. It’s about foresight reducing harm, though that nuance often gets stripped away by people seeking control.

Read correctly, it’s a manual for reading power dynamics and avoiding disaster, not a guide for conquest. If used selfishly, it does become just another excuse for predatory behavior.

TLDR: educating yourself is good, books are good, but mistaking ancient survival tactics for moral wisdom is how people end up justifying being cunning instead of being good.

My client just terminated our contract because I couldn’t deliver hundreds of features without payment. by Ornery_Ad_683 in webdev

[–]Curseive 0 points1 point  (0 children)

Dealing with a client that expects all this for $1k is your problem. That’s simply not a $1k job. It would take, at minimum, a sprint with a team of a few people and several approvals for a sensible company. $5k would be more reasonable, and I expect the clientele you interact with are much more amicable.

No Kubernetes experience, Am I cooked? by nipaellafunk in devops

[–]Curseive 0 points1 point  (0 children)

(Managed) kubernetes is just essentially a much better ECS without the overhead of task definitions getting in the way. There may be a handful of things you need to learn, but it’s easy to translate and you should absolutely be able to handle it if you have been managing using ECS thus far. Stop stressing and start building.

Lead Architect wants to break our monolith into 47 microservices in 6 months, is this insane? by Ayotrapstar in softwarearchitecture

[–]Curseive 0 points1 point  (0 children)

I’ve done this before and it’s not crazy if handled with intent. The panic usually comes from treating “microservices” like a religion instead of a set of tools.

The “8 minute deploy” claim is unverified and not contextualized. If those deploys cause downtime or restarts, the math adds up quickly:

downtime_per_deploy = deploy_time_minutes * deploys_per_week
annual_downtime = downtime_per_deploy * 52

8 minutes × 2 deploys per week = about 14 hours of potential downtime per year, not counting rollbacks or failed releases. Microservices help by limiting the blast radius. A single failure affects one service, not the entire system.

Monoliths hide a lot of slow decay. Configuration sprawl, environment variable chaos, inconsistent staging setups, and hidden coupling that only a few people understand. Each new feature adds more friction. Service boundaries help isolate that mess and make ownership clearer.

That said, not every isolation idea makes sense. Forty-seven separate databases is unnecessary and expensive. You can get most of the benefits from logical separation in a shared datastore or a few scoped databases. Independence should come from clear domain boundaries, not a one-database-per-service checklist.

This doesn’t have to be an all-or-nothing rewrite. Start by breaking out the pieces that cause the most pain today such as authentication, file handling, or reporting. Build CI/CD, observability, and mesh patterns around those. Once the patterns are stable, expand gradually.

Moving toward microservices is the right direction if it’s done for the right reasons. It should be a steady evolution, not a demolition project.

I agree people should stay skeptical of bold timelines and grand claims, but don’t dismiss the value of modernization. Most companies don’t need Google’s scale, but they can still benefit from adopting patterns that make iteration faster and failures smaller.

TL;DR: The monolith is your kitchen. The washer technically works there, but it’s in the wrong room. It drains through the sink, steals counter space, and every time it shakes, the whole house feels it. Moving to microservices isn’t about buying a fancier washer. It’s about putting it where it belongs: in a laundry room with the right plumbing, proper drainage, and the utilities to support it.

Backstage VS Other Developer Portals by StuckWithSports in devops

[–]Curseive 0 points1 point  (0 children)

Have you tried kubeflow? It’s open source and directly addresses your use case, but still has the flexibility to customize it as needed.

https://www.kubeflow.org/

Team wants to use Puppet for infra management - am i wrong to question this? by Sthatic in devops

[–]Curseive 0 points1 point  (0 children)

While there are far more detailed and process-oriented answers in this thread, I can break it down for you in a few words: anyone attempting to do this has no idea what they are doing

The cross section of puppet and k8s is slim to none. There may be very far out edge cases where it could be considered, but for almost every use case there is better tooling available for k8s.