News for hackers. Stuff that matters.
Re:What it was like working for Gitlab by cousin_it on Sunday February 11, 2024 @04:32AM (#39333763)
So, he joined as employee #28 reporting directly to the CEO, then gradually more managers were slotted in above him, then one of the managers put him on a PEP, then he got the hint and left. I wanna say this story is pretty standard, and probably a big part of the reason why people in big companies often don't do great things.

Heck, even if you start a project within a company and it gets successful, the company can just slot in people above you, so you become employee #n in a project that you started, and then these people can say you underperform and so on.

Re:What it was like working for Gitlab by mawadev on Sunday February 11, 2024 @04:58AM (#39333888)
I have that at the current company I work at. Some manager started a successful project with me and the management is too greedy and busy trying to replace me and the manager by bringing in politics, social dilemma and putting layers of management between everyone. Truly a sad state to be in. I learned my lesson as to why you should never truly care about what you do at work. Feels like the project will rather go belly up and disintegrate because of that.
Re:What it was like working for Gitlab by flir on Sunday February 11, 2024 @07:04AM (#39334451)
Not my circus, not my monkeys.

Words to live by.

Re:What it was like working for Gitlab by loloquwowndueo on Sunday February 11, 2024 @06:59AM (#39334430)
Why haven’t you moved on?
Re:What it was like working for Gitlab by slickrick216 on Sunday February 11, 2024 @10:01AM (#39335415)
You should care about the work you do. Just remember who you are doing it for. They own the work they being the company. If the company wants to reward incompetent kleptocrats then I salute them as long as I get PAID the second they stops happening they can with the greatest of respect get f’d. then you just take your trade and apply it somewhere else having learned expensive lessons they paid for about what worked.
Re:What it was like working for Gitlab by pas on Sunday February 11, 2024 @07:16PM (#39340171)
> to replace me and the manager by bringing in politics, social dilemma and putting layers of management between everyone.

sorry, this seems ... too vague for me to understand what's going on, and how it connects to their greed.

are they trying to 'scale up' this project? why aren't they keeping you? replace you how? in what capacity? are you currently wearing too many hats according to them? can you please give some details?

Re:What it was like working for Gitlab by Aeolun on Sunday February 11, 2024 @06:43AM (#39334360)
I recognize the feeling of shouting into the void trying to get people to care about something.

You’ll be telling, showing, raw stats, massaged stats, appeals to authority, what have you, but if the only thing the directors care about is features, it’s all for nothing.

After 3 years it finally became a problem because they noticed that releases kept failing, but I don’t think it had anything to do with me so much as someone typing ‘how to stop my releases failing’ into Google.

I don’t know how to solve that, as I’m going through the same thing again now (with a different subject).

Re:What it was like working for Gitlab by spense on Sunday February 11, 2024 @04:41AM (#39333808)
are you suggesting a better way?
Re:What it was like working for Gitlab by itronitron on Sunday February 11, 2024 @06:34AM (#39334319)
A better approach is to have separate career tracks for 'people' managers and 'project' managers.

People managers do the performance evaluations and various HR administrative tasks (signing time cards, hiring, firing, etc.) but they rely on feedback from their group which are both individual contributors and project managers.

Project managers lead the projects and have to select/attract the right combination of individual contributors to their project if they want it to succeed.

A project that 'gets more management' will usually have to justify the addition of PMs from a cost-benefit perspective. And a project that is overburdened with management types will usually see the ICs migrate to other projects in order to improve their impact.

All this happens organically, so individual contributors are empowered instead of being disenfranchised through organizational changes.

Re:What it was like working for Gitlab by marcinzm on Sunday February 11, 2024 @06:49AM (#39334384)
That sounds like basically matrix management which has many well documented issues. The biggest one in my experience is that the people managers need to be themselves judged on some rubric. If that rubric is success of projects then it tangentially aligns with business goals. If it's something else or they don't have power over projects then they are encouraged to play constant politics.
Re:What it was like working for Gitlab by itronitron on Sunday February 11, 2024 @07:04AM (#39334449)
The general rubric should be that their group is performing well. Depending on the organization that could mean a number of different things.

>> If it's something else or they don't have power over projects then they are encouraged to play constant politics.

Why would they need to play constant politics if they don't have power over projects? Not everyone is motivated by the same things.

Re:What it was like working for Gitlab by marcinzm on Sunday February 11, 2024 @08:06AM (#39334725)
> Why would they need to play constant politics if they don't have power over projects? Not everyone is motivated by the same things.

They do have power over the projects. Being able to PIP someone is power over everything that person does including which projects they work on. Including which projects no one works on. Except it's not their direct power which means to leverage it they need to play politics. Adding layers doesn't remove that power but simply increases the amount of politics they play to make up for it.

Re:What it was like working for Gitlab by itronitron on Sunday February 11, 2024 @10:42AM (#39335721)
The goal with the matrix management is to distribute the risk. If your people manager puts you on a PIP then at least your project managers will have some ability to push back on that.

But there is no good reason for the People manager to care anything about what projects have people working on them. If they start to care about which projects are successful instead of all projects are successful then they're not a good fit for the job. And yes I have experienced that, as well as it's opposite.

Re:What it was like working for Gitlab by pas on Sunday February 11, 2024 @07:26PM (#39340223)
and this leads to 4 engineers and 6 managers sitting in a meeting, and nobody actually being responsible for anything.

no, of course, there's a lot of value in providing escalation/descalation/rehoming processes, and dedicated ways for org-wide feedback on people's and projects' impact, but people are not just three orthonormal roles on top of each other in a trenchcoat, if there's not clear hierarchy then - as others pointed out - the informal chaos takes over (because it's the human default)

Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @04:48AM (#39333847)
Management is mostly needed for two things [*]:

- Organising the work and steering it in the right direction

- Ensuring that people work well together, help them grow, deal with "people problems"

If and when both of the above is achieved without a person holding the title "Manager", you don't need them.

This can be achieved by hiring 51%ers for example [1] and by actively monitoring the health of your organisation.

[1] https://news.ycombinator.com/item?id=39333921

[1-1] https://www.amazon.com/Setting-Table-Transforming-Hospitalit...

[*] YMMV: the hardest problem in any organisation is the "people" aspect, there's no silver bullet.

EDIT: Added the link to my other comment about 51%ers

Re:What it was like working for Gitlab by isbvhodnvemrwvn on Sunday February 11, 2024 @04:55AM (#39333878)
Do you have any practical experience with companies running as it's described in this motivational book?

Many of those books are selling well because they are well written and say exactly what reader thinks might work, but if you ask anyone else who worked with the author, the reality can be quite different.

Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @05:02AM (#39333906)
> Do you have any practical experience with companies running as it's described in this motivational book?

I do not have experience running it at a company level, but at a team level (I have been an engineering lead in two companies for the last 6 years).

From all the books I've read (I read a lot), this is the one that was most "spot-on" about treating other humans and making them feel valued and therefore building a team with strong bonds.

> Many of those books are selling well because they are well written and say exactly what reader thinks might work, but if you ask anyone else who worked with the author, the reality can be quite different.

Absolutely agree.

In my experience I resonate most with any books when I have already, unbeknownst to me, been applying what they preach (which has been the case with Setting the table that I'm currently in the process of finishing).

I believe that it requires a lot of introspection to be able to apply new knowledge (ie, if you haven't thought about it or experienced it before reading about it)

EDIT: formatting

Re:What it was like working for Gitlab by The_Colonel on Sunday February 11, 2024 @06:24AM (#39334270)
That's what I like about "agile roles" like Product Owner or Scrum Master, they take a slice of traditional manager's responsibilities, but they don't have any reporting authority over other workers. My EM has like 30 direct reports and it works fine because he doesn't really have anything to do with our day to day work.
Re:What it was like working for Gitlab by xorcist on Sunday February 11, 2024 @07:47AM (#39334634)
Those semi-managerial roles are the biggest problem with that model, in my opinion. Sure, it works as long as everything is peachy. But as soon as there are any real conflicts of interest, it will show who is the real manager. And it's not the product owner or scrum master.

With authority comes responsibility for your actions. Without responsibility, no authority. The product manager is a manager in name only, and product owner even less so.

That doesn't mean you can't have several direct reports. The classic matrix organization for example. But it means semi-managers without real responsibility have no real mandate for doing a good job at the slightest hint of trouble.

Re:What it was like working for Gitlab by The_Colonel on Sunday February 11, 2024 @02:43PM (#39337932)
> But as soon as there are any real conflicts of interest, it will show who is the real manager. And it's not the product owner or scrum master.

If there's a conflict of interest, it needs to be discussed based on merit, not based on who has the bigger authority.

If there's no agreement, it needs to be escalated to somebody who has the authority (manager). But IME this doesn't happen very often.

I like this model, because the default position is that none of the engineering, product, process is the "master", so you need to negotiate. If one of the roles also has reporting authority, that automatically skews the decision making towards yielding to them.

Re:What it was like working for Gitlab by higeorge13 on Sunday February 11, 2024 @07:07AM (#39334468)
30 direct reports? And doesn’t have to do anything with your day to day job?

So what is his job then?

Re:What it was like working for Gitlab by The_Colonel on Sunday February 11, 2024 @02:35PM (#39337851)
Hiring, performance evaluation, vacation approval, team direction/strategy, managing up etc.
Re:What it was like working for Gitlab by FireBeyond on Sunday February 11, 2024 @05:58PM (#39339660)
I'm not sure how you can evaluate 30 people you don't interact with closely.

NIMS, the National Incident Management System, talks of ICs having between 3-7 direct reports, when there is a need to be connected to what they are doing, because beyond that, you can't reconcile things easily.

Re:What it was like working for Gitlab by The_Colonel on Sunday February 11, 2024 @06:29PM (#39339877)
I don't know the exact process, but AFAIK managers pull the evaluation from many people you do interact with (outside and inside the team).
Re:What it was like working for Gitlab by eddyg on Sunday February 11, 2024 @07:59AM (#39334687)
Thanks so much for the “51%ers” reference!

That list of “skills” is spot on. I also especially like his use of the term “skunking” to describe how somebody’s personal opinions/problems/issues impact the rest of the team. “51%ers” are exactly the kind of people I want to work with.

Re:What it was like working for Gitlab by higeorge13 on Sunday February 11, 2024 @04:54AM (#39333870)
51%ers?
Re:What it was like working for Gitlab by mkl on Sunday February 11, 2024 @06:40AM (#39334344)
https://duckduckgo.com/?t=ffab&q=51+percenter&ia=web

Someone "whose skills are divided 51-49 between emotional hospitality and technical excellence" [1]. Seems quite bizarre to me to define it so precisely. Even if skills were measurable in such a way, how many people will be exactly 51% emotional hospitality, and why is 52% or 50% not suitable?

[1] https://www.nrn.com/corporate/meyer-51-percenters-have-five-...

Re:What it was like working for Gitlab by chasd00 on Sunday February 11, 2024 @11:55AM (#39336292)
i think the implication is if a 51%'er has to decide between technical excellence and emotional hospitality then, all other things equal, they will use emotional hospitality since that's the majority of their skills (51%). It sounds like preferring to hold a hand vs rejecting incompetence. I don't really agree, i get not being jerk is important but i would flip it to 51% technical excellence 49% emotional hospitality.
Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @05:06AM (#39333921)
I hope I'm not violating any copyrights – page 143 of Setting the Table from Danny Meyer [1]

> To me, a 51 percenter has five core emotional skills. I’ve learned that we need to hire employees with these skills if we’re to be champions at the team sport of hospitality.They are:

1. Optimistic warmth (genuine kindness, thoughtfulness, and a sense that the glass is always at least half full)

2. Intelligence (not just “smarts” but rather an insatiable curiosity to learn for the sake of learning)

3. Work ethic (a natural tendency to do something as well as it can possibly be done)

4. Empathy (an awareness of, care for, and connection to how others feel and how your actions make others feel)

5. Self-awareness and integrity (an understanding of what makes you tick and a natural inclination to be accountable for doing the right thing with honesty and superb judgment)

[1] https://www.amazon.com/Setting-Table-Transforming-Hospitalit...

Re:What it was like working for Gitlab by lazyasciiart on Sunday February 11, 2024 @05:41AM (#39334090)
For future reference, you are certainly not violating US copyright law, because quoting a few sentences from a book falls under fair use. https://en.wikipedia.org/wiki/Fair_use
Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @05:50AM (#39334138)
Thank you!

That's why I love HN so much: a helpful answer with a source to boot!

Re:What it was like working for Gitlab by nightlyherb on Sunday February 11, 2024 @07:05AM (#39334455)
I was curious why the author decided to call them "51 percenters." A google search of the term suggests that the skills of this group of employees are divided by 51% hospitality and 49% technical excellence. Please feel free to correct me if there is anything wrong in my interpretation.
Re:What it was like working for Gitlab by mavamaarten on Sunday February 11, 2024 @05:28AM (#39334029)
Sounds like a combination of open doors and corporate mumbo jumbo to me.
Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @05:48AM (#39334128)
I'm sorry you feel that way

This description helped me put words on the type of people I enjoy working with

Re:What it was like working for Gitlab by eddyg on Sunday February 11, 2024 @08:04AM (#39334710)
Exactly! I’ve never been able to express a succinct list of why some teams and/or companies feel better than others, but “51%ers” explains it perfectly.
Re:What it was like working for Gitlab by DANmode on Sunday February 11, 2024 @06:29AM (#39334298)
Not a manager, right?
Re:What it was like working for Gitlab by soneca on Sunday February 11, 2024 @05:09AM (#39333938)
What is a 51%er?
Re:What it was like working for Gitlab by nip on Sunday February 11, 2024 @05:10AM (#39333948)
I updated my comment once I was home (and able to get the exact definition from the book):

https://news.ycombinator.com/item?id=39333921

Re:What it was like working for Gitlab by coffeebeqn on Sunday February 11, 2024 @11:19AM (#39336032)
I thought it was a great write up of the lifecycle of a successful startup. If you stick around you get to see a lot of change. Some positive some negative. Of course at 1000+ people you can’t have everyone reporting to the CEO
Re:What it was like working for Gitlab by Aurornis on Sunday February 11, 2024 @11:24AM (#39336063)
> Heck, even if you start a project within a company and it gets successful, the company can just slot in people above you, so you become employee #n in a project that you started, and then these people can say you underperform and so on.m

The trouble with these stories is that they’re n=1 anecdotes and we only get one side of the story.

There’s an implicit claim in many comments here that we need to assume that the employee was actually a higher performer, didn’t need managers, didn’t deserve a PEP and so on. That’s understandable given that we tend to put ourselves in the shoes of the person writing a piece and being anti-corporate is always popular on HN.

However, those aren’t safe assumptions in cases like this. I’ve worked at a couple early stage startups that acquired early employees who couldn’t (or wouldn’t) grow with their role and the company. It’s common to keep early employees around out of respect for their past work, a belief that they hold difficult to replace historical knowledge, or simply because they’re well connected to founders and other early employees who have grown into leadership positions.

But in reality, simply being an early employee and being involved with early important projects doesn’t necessarily mean that person is the best person for the job or even a good fit for continuing to do it. Some of the early stage employees I worked with were great at cobbling something together from scraps and keeping it functional with a collection of cron jobs and manual interventions, but their operating style doesn’t work at a bigger company at all. If they can’t adapt and change or they become disgruntled about having to work on things the way you have to at a bigger company, they start to become more detriment than help. That’s just one example of many different potential failure modes of early employees as companies grow that we don’t like to talk about.

> I wanna say this story is pretty standard, and probably a big part of the reason why people in big companies often don't do great things.

It’s “standard” in the sense that every early company has a number of early employees who don’t grow with it, but it’s not the only or even a common fate. GitLab has plenty of employees who have been there for a long time, but you’re not hearing about them from disgruntled blog posts. Consider the selection bias when reading this.

As for the claim that they can’t do “great things”: I’ve used GitLab for a very long time and I disagree. The product continues to evolve. It’s not a stagnant product at all.

Re:What it was like working for Gitlab by kevin_nisbet on Sunday February 11, 2024 @12:17PM (#39336504)
I largely agree, especially with the sentiment that there are two sides to any story.

I think one angle I'll nitpick though is this doesn't have to be related to whether or not the employee was a high performer or had particular leadership needs or whether they're adaptable to the current maturity level of the org. There can and likely are many other elements such as whether the manager/employee even get along, or agree on direction, strategy, problems, etc.

And the difficulty is, these types of issues can often show up as performance issues. In lots of cases, is the performance issue the employees fault or the leaders.

In my anecdotal experience where a job went from the best role I ever had to one of the worst happened over a very short week or two with the change in a manager. And I think to the point you're making, when I resigned I outright said... each of us is going to blame the other for my departure. The hard truth is the answer is likely if either of us had been different people I'd still be in that role doing work I really enjoyed, but in that particular leader/follower relationship we simply didn't get along well at all.

If I ever did a what it was like or why I left post, I'd probably have plenty of arguments for my side, because I think to your point, I'll be the hero in my own story.

Re:What it was like working for Gitlab by julik on Monday February 12, 2024 @02:08PM (#39348901)
> In my anecdotal experience where a job went from the best role I ever had to one of the worst happened over a very short week or two with the change in a manager.

Two managers in my case, both of whom were, let's say, not successful in their roles. And a glass ceiling so that I had to do most of the work _and_ be a tech lead, yet "could not manage the team because reasons".

Sudden reorgs + hire above + glass ceilings = golden ticket for horrors like this.

Re:What it was like working for Gitlab by metricspaces on Sunday February 11, 2024 @12:04PM (#39336374)
‘He worked remote’ thought popped into my head. He wasn’t there to “grow into leadership role” with the rest of the early employees. I do agree with your read of the situation.

btw, that restaurant in Amsterdam is apparently the go to place for startups. I am certain I sat in one of those chairs (was this on 2nd floor facing the canal?) with another fabled startup.

Re:What it was like working for Gitlab by Aurornis on Sunday February 11, 2024 @12:27PM (#39336608)
> ‘He worked remote’ thought popped into my head. He wasn’t there to “grow into leadership role” with the rest of the early employees.

GitLab is fully remote. Everyone works remote, including leadership.

Re:What it was like working for Gitlab by rzzzt on Sunday February 11, 2024 @02:42PM (#39337927)
It's hard to do if the company is still small. Too many lead cooks leaves the kitchen unmanned.
Re:What it was like working for Gitlab by throwboatyface on Sunday February 11, 2024 @12:20PM (#39336543)
My read is that he was one of those early employees that is a huge pain to manage. They want to do what they think is fun and interesting and they have strong opinions about shit that is ultimately inconsequential. It's a nightmare to manage an IC who is friends with the CEO and doesn't think you're making the right choices. But ultimately they don't accept accountability for any decisions, they just move bop around and cause problems.

One tell-tale sign is endpoint security and using his own device. It's the kind of permissive cultural thing that does not scale because of compliance issues and developer productivity overhead. But it's very hard to wrench these long-time devs away from their preferred Linux distribution which requires conditional build stuff everywhere to support. Use a work computer for work, let them monitor the updates and stuff, as long as they're not using the webcam to record you who cares?

The database backup story - my guy you were on the database team. Backing up the databases is job 1. You can't just passive-voice away "oh there were no backups". But of course he's more interested in fighting about sharding architecture than actually keeping the site running day-to-day.

His big takeaway is that Gitlab didn't spend enough time on performance for their hosted offering which was a huge money loser. Just because he thinks performance stuff is fun to do, if the hosted offering is a money pit of course they're not throwing more resources at it. You have to make an actual business case for why your thing is more important and makes money more than another project. You don't just engineer in a vacuum for the fun of it.

Re:What it was like working for Gitlab by returningfory2 on Sunday February 11, 2024 @01:06PM (#39336939)
Your read lines up with another point in the article that I found to be stated in strangely absolute terms:

> you need to be able to deploy your code fast, i.e. within at most an hour of pushing the changes to whatever branch/tag/thing you deploy from.

This sweeps under the rug all of the potential issues with fast deploys. I guess it depends on the product. I work on a managed database service, and one category of potential bug is that we accidentally delete or corrupt customer data. We have to be much more careful and can't just deploy what was submitted to mainline in the last hour without doing significant regression and performance testing.

But anyway essentially the main reason they give for fast deploys is:

> being able to see your changes live is nice because you actually get to see and make use of your work.

I think this is true. But, it lines up with this negative interpretation of this article. The author seems to prioritize themselves over the health of the product they're working on.

Re:What it was like working for Gitlab by cousin_it on Sunday February 11, 2024 @03:23PM (#39338293)
Sure, you could argue such people are needed only at the early stages of a company, and counterproductive when the company gets bigger. But I don't buy that. Why then are big companies asking all the time: "Oh, where's our internal startup spirit? How can we bring it back?" Right after firing the people who encapsulated that spirit, for being "hard to manage".
Re:What it was like working for Gitlab by SheddingPattern on Sunday February 11, 2024 @04:28PM (#39338932)
Because sometimes all they're after is for slideware on GenAI. The people they fired encapsulated a spirit of innovation that doesn't fit the operating model and therefore is of no value to them.
Re:What it was like working for Gitlab by depereo on Sunday February 11, 2024 @05:22PM (#39339353)
I think this trend to talk about startup practices in large orgs is more executive nostalgia and a complaint about all the processes put in place to catch mistakes that have been made before.

The same people as developers would be pursuing rewrites of rock-solid 20+ year mature software projects because there's a trendy framework.

Large organizations don't have 'startup spirit' because 'startup' companies fail. Employees of large mature orgs with 6000 employees didn't sign on to a company that's got a good chance of not existing next quarter. They're not taking massive risks and throwing halfbaked features into a brand new product with 1 client hoping to get bought by facebook or maybe an insurance company.

If those big companies are really complaining about not having startup spirit maybe they should provide an exit for the VCs and aquihire (briefly because the engineers will all leave asap) a startup!

Re:What it was like working for Gitlab by ParetoOptimal on Monday February 12, 2024 @01:01AM (#39341919)
You make it sound as if big companies are generally really effective and its enabled by their bureaucracy.
Re:What it was like working for Gitlab by depereo on Monday February 12, 2024 @03:14AM (#39342662)
Not my intention, sorry!

Big organisations are stable, mostly due to the often frustrating inertia and lack of risk taking coupled with their existing, mature revenue streams.

Re:What it was like working for Gitlab by julik on Monday February 12, 2024 @02:04PM (#39348852)
Sometimes it is not even about the "startup spirit", but more like "why is it that we didn't do any projects of significance in the last year, and why is our incident rate 3x from what it was just 3 quarters ago, and why are all these migrations not finished yet?"
Re:What it was like working for Gitlab by Rapzid on Sunday February 11, 2024 @03:05PM (#39338134)
Such an interesting article because there are two main reasons I never thought to apply at GitLab:

* Even in the USA the col based pay made them non competitive compared to what I could get elsewhere.

* Incidents like the database backups, and others, lead me to believe they weren't executing at a high enough level.

Re:What it was like working for Gitlab by LtWorf on Sunday February 11, 2024 @12:59PM (#39336883)
Who makes more career? The guy bullshitting about architecture or the guy ensuring stuff works that nobody notices even what he's doing?
Re:What it was like working for Gitlab by grogenaut on Sunday February 11, 2024 @02:05PM (#39337556)
The dev who makes shit work and and tracks measures the ops gains / reduced headcount needs and reports their impact up the chain. Who also gives talks on how everyone can make their stuff run as simple as they do.
Re:What it was like working for Gitlab by LtWorf on Sunday February 11, 2024 @03:04PM (#39338120)
You can give talks without do anything. That works just as well.
Re:What it was like working for Gitlab by YorickPeterse on Sunday February 11, 2024 @04:37PM (#39339005)
I can assure you that me being a pain to manage wasn't the problem, nor was it ever brought up. In fact, the only negative/improve-upon-this-thing kind of feedback I got once or twice was to adjust my communication style to be less blunt/harsh, something I agreed with and did end up improving upon.

I can also guarantee you that the work I did very much did good work instead of "cause problems". Feel free to ask anybody that worked at GitLab during the same time (or is still there) and see for yourself :)

Re:What it was like working for Gitlab by throwboatyface on Sunday February 11, 2024 @06:13PM (#39339777)
> I didn't get along well with this manager,The resulting conflict lead to a "performance enablement plan"

Respectfully, in your post you literally say you got a new manager who PIPed you for being hard to work with. The whole tone of the article feels like rehashing old disagreements.

Re:What it was like working for Gitlab by YorickPeterse on Sunday February 11, 2024 @08:55PM (#39340609)
Respectfully, I didn't. I specifically wrote the following:

> I didn't get along well with this manager, The resulting conflict lead to a "performance enablement plan", a procedure meant to get things back on track before the need for a "performance improvement plan" (PIP). A PIP is meant to be used as a last attempt at improving the relationship between an employee, their work, and their employer.

Not getting along with someone doesn't imply or mean that a person is difficult to manage. Instead, it means there's simply friction between two people.

In this specific case, the main source of friction was that my messed up working hours resulted in me performing tasks later than expected (though still within any deadlines), though I recall those time frames not being well specified to begin with (i.e. it was more of an implicit assumption that X would be done by hour Y).

I believe I was also a little late for a meeting because I'd overslept. That's not good, but it certainly isn't a case of "Wow this person is so difficult", instead more of a case of "This person needs to get his schedule back together".

Either way, you seem to be interpreting the story in a way different from what's written down. I doubt I can change that, so I'm going to leave it at this comment.

Re:What it was like working for Gitlab by pas on Sunday February 11, 2024 @07:11PM (#39340144)
how can you assure that? it seems like a classic self-fulfilling prophecy of arrogance.

changes bring some adjustment uncertainty, and sometimes it goes well, things get better, sometimes it gets worse. with enough time you'll draw a short stick. it sucks.

Re:What it was like working for Gitlab by YorickPeterse on Sunday February 11, 2024 @08:44PM (#39340571)
> how can you assure that? it seems like a classic self-fulfilling prophecy of arrogance.

Because colleagues have told me so, and the annual employee reviews were positive as well. In fact, outside the PEP the only actionable/to-improve feedback I got was essentially "Sometimes you can be a little harsh/blunt", which is vastly different from "this person is difficult to work with".

Re:What it was like working for Gitlab by julik on Monday February 12, 2024 @02:05PM (#39348863)
Yorick, your article struck me as incredibly reserved and thoughtful. Props to you, honestly.
Re:What it was like working for Gitlab by julik on Monday February 12, 2024 @02:02PM (#39348827)
> It's a nightmare to manage an IC who is friends with the CEO and doesn't think you're making the right choices

Since I find this take harmful, let's rotate the scene: what if you have no business being in the manager's seat above that IC in the first place, and you are effectively being used as a tool by someone who is not the CEO, but, say, a newly-appointed CTO? What if you _are_ making the wrong choices? What if that IC is one of the few people in the org having the experience and the knowledge to tell you that you are? What if that IC is making the right calls and suggestions, but your implicit directive you got from the newly-appointed CTO is actually to manage that IC out "because they are such a pain for everyone"?

I have been on both ends of this situation and I do believe most scale-ups are _not_ doing a good job retaining and nurturing their early-stage staff+ ICs into their larger era. This has multiple reasons, but it does often feel like there is a lot of value to be had if just those staff+ ICs weren't so horribly mismanagemed. A hire-above-from-the-outside is prime example.

And if I sound bitter - let's just say I have experience being "that IC". It wasn't pretty, and no - I was not an asshole.

Re:What it was like working for Gitlab by throwboatyface on Tuesday February 13, 2024 @11:01PM (#39366306)
In every startup I've been in, there was undue deference to long-time ICs. They didn't normally stir up public fights with execs but they would openly undercut line managers and then move around in the org as people tried to stop being responsible for them.

It's not really clear what you do with a staff+ long-term IC. A lot of them don't want to manage or be involved in leadership, but they want to pull down a huge salary and just do work that is frankly replaceable by a senior eng.

To be clear I do believe there are levels of IC experience above staff, but being 21 and joining a startup doesn't make you a Principal Engineer just because you hung around until you're 30. Especially if you've only worked at that one startup.

Re:What it was like working for Gitlab by julik on Thursday February 22, 2024 @04:35PM (#39473597)
> It's not really clear what you do with a staff+ long-term IC

Set clear expectations in the first place. "I want to run things my way here, I'm the new management and I don't like you" is not an expectation - and that's what I have observed happen all too often.

Re:What it was like working for Gitlab by zelphirkalt on Sunday February 11, 2024 @03:23PM (#39338290)
From my own experience as very early employee, I know how it feels, to have them slot in more leads and managers above you and step by step losing the mechanisms, that enabled you to be very effective early on, when you just got things done. Later every step needs to go through some slotted in manager position, making sure you don't work on something "wrong", no matter how much your early ideas and contributions enablef the company to rise in the first place.

I wonder if this is what is behind years old stale issues of gitlab, especially regarding Gitlab CI. From the outside you get the impression, that they completely lost ability to build great things, since they do not seem to care to fix years old bugs that still come up again and again.

Re:What it was like working for Gitlab by SergeAx on Tuesday February 13, 2024 @12:40PM (#39360329)
But what if they really became underperformer? Times change, people change.