Live data from Hacker News

From Belonging to Burnout, Five Years at Airbnb

news.techworkerscoalition.org

151–153 of 153 posts

Re: From Belonging to Burnout, Five Years at Airbnb

#151

Earlier quoted context omitted.

I’m a cynic but I wish that were true. In my past experience it has usually been the opposite, the bulk of engineers are making unnecessary tools, re-inventing wheels, and designing systems that shouldn’t exist and serve as roadblocks to the minority of engineers who are miraculously getting things done in spite of all that.

The biggest cost of bloat comes from people being nice, it is emotionally hard to replace/rewrite code when the author is still there and not disliked by the team. Basically it sucks to make people redundant, so we try not to, and that makes it look like people aren't redundant even when they are. For example, lets say you give a project to a competent engineer, he writes a clean and maintainable solution quickly alo…

Yes, but it’s done on a project basis. Kill the project, move the good people to a new project, release the others. Later, resume/restart the project.

It’s really hard to be surgical about this because who wants to be the good engineer that has to pick up the barely functioning pieces of code left behind. Who wants to reward a solid engineer with a big refactor job on an already late/failing project? The optics aren’t great. I’m not saying it never works, but as a general rule, deferring the project is often a better option.

Re: From Belonging to Burnout, Five Years at Airbnb

#152
post #137

Earlier quoted context omitted.

TWC is literally what it says on a thin: all workers, no backers, just being honest about our experiences. You can call us entitled, but insofar as we're propagandists, each individual is only pushing our own personal "narrative." "Building power" is _definitely_ political activism but, again, the way we build power is, primarily, by exposing ourselves to eachother's personal experiences in the tech industry. That kn…

Discussions about working conditions are welcome. Make it a cover for something else is not. It would be nice to talk to the generations you mentioned. Not sure you did, but I did a lot. Workplace was a lot worse in the 50s, from working hours to safety. Still, people had liberties, could create friendships and gather and talk openly and free. These days the same people that you the words in the article are the ones…

> a cover for something else

What are you accusing me of? I am literally just a technology professional who likes to compare notes about important aspects of my career with other professionals. It's not a cover for anything else. I am just one individual trying to stay informed and so are the people I have met through these channels. I can't imagine for what "something else" an autobiographical blog post might cover.

>It would be nice to talk to the generations you mentioned. Not sure you did

I am a third generation software developer, as it happens, so I have more-than-average familiar with the history of the information technology industry (to say nothing of the history I've read). Of course, there is a LOT of ground I haven't covered, and of which I remain ignorant. This is one of the many reasons I like articles such as these, autobiographical works and conversations with other technology workers.

> Workplace was a lot worse in the 50s, from working hours to safety

Not in every way and while, yes, we've seen improvements—so what? Are we done? There's still much unnecessary suffering. I don't think we're done. Ours is an industry of innovation, of development. Why should employee relations stagnate? Why should working conditions stagnate? And, in some cases, get worse?

> Still, people had liberties, could create friendships and gather and talk openly and free. These days

These days, we alter our language to evade censorship algorithms from private for-profit corporations who've enclosed the public forum. We create mere token "friendships" in undemocratic virtual reality, or undemocratic workplaces — where a friendship is terminated when employment is terminated: at the whim of a boss. It's the legalistic corralling of human behavior by undemocratic software media that's "killing free speech," and "forcing agendas" written in code. Read some Kafka, for crying out loud. To go online is to "stand before the law" as much as in any analog bureaucracy of which I've read an account — including Solzhenitsyn's!

The "atomizing [of] society" comes from a hollowing out of our social institutions by television, by the commercialization of public space and of free time. Read Putnam's "Bowling Alone" for the details.

"Friction between races, sexes, classes and everything" has always been here, but now that the internet's letting us peer into one-another's lives, we're noticing it. And we're going to have to resolve it. We can't sweep it under the rug for another generation.

> With one hand they complain, with the other they cause the situation

Famously: we didn't start the fire. ;)

> there is no honesty there

I don't know who you're talking about, but probably not the author of this post, and probably not me. Again, I am just a 3rd generation software engineer trying to make it in the industry just like my parents and grandparents, except conditions have changed and what worked for them isn't working any more.

Thanks for the opportunity to exchange perspectives.

Re: From Belonging to Burnout, Five Years at Airbnb

#153
post #93

Earlier quoted context omitted.

Imagining boatloads of complexity involved with the blinking cursors according to markets, profiles and geographic locations and whatever else really doesn't make it sound any better at all.

> Imagining boatloads of complexity involved with the blinking cursors according to markets, profiles and geographic locations and whatever else really doesn't make it sound any better at all. These basic everyday requirements are oblivious to those who have zero first-hand contact or experience with professional user-facing problems imposed by business requirements. However, just because you're oblivious or unfamili…

>These basic everyday requirements are oblivious to those who have zero first-hand contact or experience with professional user-facing problems imposed by business requirements.

Could you paint me a realistic scenario for such multifaceted complexity revolving around this blinking cursor in a particular field? I can see how this might depend on a language/writing system but kind of get lost beyond that.

I do have experience with such "professional user-facing problems imposed by business requirements" btw but they tend to be more related to desktop and factory software each used by hundreds which is probably a few zeroes less than what we're talking about here.

>And I'm not even touching hard technical probs which most developers aren't experienced or competent in, such as security and reliability.

I know more than most that software can behave in weird ways but don't you think if there's a reasonable worry that altering this blinking cursor affects security that something is off?

Post reply on HN