Hacker Newsnew | past | comments | ask | show | jobs | submit | donutshop's commentslogin

"We laid off most of the team despite record profits and need free labor to maintain what remains"


Let's hear it!



Same.


... and kubernetes networking, service mesh, secrets management


You arent' forced to use service mesh and complex secrets management schemes. If you add them to the cluster is because you value what they offer you. It's the same thing as kubernetes itself - I'm not sure what people are complaining about, if you don't need what kubernetes offers, just don't use it.

Go back to good ol' corsync/pacemaker clusters with XML and custom scripts to migrate IPs and set up firewall rules (and if you have someone writing them for you, why don't you have people managing your k8s clusters?).

Or buy something from a cloud provider that "just works" and eventually go down in flames with their indian call centers doing their best but with limited access to engineering to understand why service X is misbehaving for you and trashing your customer's data. It's trade-offs all the way.


So the tl:dr is that they took a risk and never tested their high availability setup.


I think what Adam Jacob is doing with system initiative addresses this, right off the get go.


Massive scale*


This smells like "Industry best practices"


The siloing causes tons of issues from what I have observed.

Why do we need a two month lead time now to ship a new static page?

How could we have drifted so far that we need kubernetes for that?

How is it possible that we need a platform team to build yet another later of abstraction from our cloud providers?

Why do we have more yaml than the code we're shipping?


I try to think about developer experience in my day-to-day. K8s might make deployment for the DevOps team easier but more painful for the devs, and that's not good because they are the ones who make the company money. So work together with the developers if they're complaining to make it possible to ship code as fast as possible. If the devs don't like settings in yaml files, find a way to abstract that away (use standardized naming so there's fewer values they have to care about, give sane defaults that won't be overwritten 90% of the time).

The DevOps team's sole existence is there to enable developers to ship better code faster. If DevOps practices are preventing this, that needs to be addressed.


I don't agree with this generalization for good communication "In my experience more extroverted and “chaty” engineers have it better on average."

Often times we conflate loud communication with good communication. In my personal experience there are lots of verbose individuals that are poor communicators.


My personal experience with a room full of very smart introverts is that they do not communicate near enough information, or simplify it to the proper level. I assume it is because their expectation of "common knowledge" is much higher.


I was just discussing this with my girl last night. This is technically irrelevant to the overall context but in this specific comment thread, it's hard to figure out how to make content for the general population. I feel a lack of confidence because I surround myself with people who are smarter and better at things than me a lot of the time. So when I want to make them interested in something it's got to be super complex.

At the same time I see people watching a tutorial telling them how to put their OpenAI API key into a mass-adopted bot platform and getting "It's really cool you can do these kinds of things!" which is what started the conversation. Like it's cool they're trying, no shade to them but my baseline of what most people will think is interesting is so distorted.


> I feel a lack of confidence because I surround myself with people who are smarter and better at things than me a lot of the time.

It's not feasible in a number of organizations, but things like this are why it's important for developers to interact with the users of the software that they create. You learn so much more about what works and doesn't work for the users. You learn their vocabulary and assumptions about using apps which is often quite different from "power users" like we tend to be.


I look at it as signal to noise ratio. If someone communicates a lot but has a very low signal to noise ratio, parsing what might be valid from everything else, becomes a chore and adds cognitive overhead.


You don't have any idea what introversion means. Introversion doesn't mean withholding information nor being afraid to speak out loud nor being unable to synthetise information.

It does not mean to be shy, nor uncomfortable with people. Introversion does not mean exhibiting symptoms of autism either, which might be what you are talking about with "simplify at the proper level" (?).

Introversion and extroversion have absolutely nothing to do with the quality of a software engineer or its documentation. I just wish this label would just die, given how its misunderstood and misconstrued.


You had the opportunity to explain what introversion actually is, but instead this comment is only what it is not. I don't think that's useful if you are actually trying to help the commenter to which you replied.


Indeed. I'm an introvert who is in a leadership position at a large consulting company. My natural inclination is to be quiet unless things are going off the rails. But that doesn't work for the job I have, so I have to put myself out there more and communicate things much more explicitly and clearly than I'd prefer. But I can do it. I can lead calls and projects. I can "charm" CTO's with my ability to understand and breakdown the challenges they are facing. I can be persuasive and an effective mediator. But it's exhausting for me.

I spend most of my working day talking to people, and at the end of the work day I'm done with people and need to spend a significant time alone in my head to recharge. I doubt that any of the folks I work with would describe me as an introvert because the nature of my work doesn't allow me to fall into the comfortable isolation I'd prefer. At the same time, I can't have the impact that I do if I was the stereotypical "introvert" engineer which is what makes all the effort worthwhile. The biggest challenge with this is my intolerance for people extends to friends and family after work. A day full of meetings and I can't focus on conversations my wife tries to pull me into and I have zero desire to hang out with any friends. I literally need time alone to recover.


Same. I could totally relate. Comfortable isolation sounds blissful.

After a long day I tend to zone out and my partner tells me it's like they're talking to a wall.


> It does not mean to be shy, nor uncomfortable with people.

introvert - noun - a shy, reticent person. [0]

At any rate, your comment is a pretty good example of what I'm talking about. Even if where I get my idea of it is off course from yours, you immediately become seemingly quite offended and start arguing your point in depth on trying to change what I understand as being a pretty global understanding of a word. You even kind of argue at the end that it is common usage.

[0] Oxford Languages via Google


That was a lot of words telling us all what introversion isn’t, but not a single word telling us what you think it actually is. Care to try again?


A nice example of introverted comment.


Introversion vs extroversion is more about how you recharge

Extroverts get energy from talking to people, so they are likely to do it more

Introverts are the opposite.

An introvert can talk more than an extrovert.


I'm an introvert. I talk a lot, I like being around people but they tire me. The day I'm in the office, I feel like dying in the last hour. Thank god it's 90% WFH.


I do believe that more communication (even useless ones such as "I have completed stage 1 and now moving to stage 2) are better than less or none.

This is especially true for juniors because they cannot fix stuffs quickly, so it's better to talk their thoughts loudly in the incident channel.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: