Live data from Hacker News

Confessions of a Software Developer: No More Self-Censorship

kerrick.blog

261–270 of 372 posts

Re: Confessions of a Software Developer: No More Self-Censorship

#261
There is so much wrong with idealistic approach that I actively oppose “good practice cottage industry” like Uncle Bob.

Not remembering sql or details of different joins - after looking it up how much time does it take to kick back in?

I don’t remember a lot of stuff by heart but as once I worked with it I can go back rather quick, if you need it just brush it up. If you don’t need it who cares.

Polymorphism I can do stuff with it and it hurts my brain yes when I see switch statements that should be objects - but on the other hand it is much easier to understand switches or ifs for a lot of folks.

Re: Confessions of a Software Developer: No More Self-Censorship

#262
post #261

There is so much wrong with idealistic approach that I actively oppose “good practice cottage industry” like Uncle Bob. Not remembering sql or details of different joins - after looking it up how much time does it take to kick back in? I don’t remember a lot of stuff by heart but as once I worked with it I can go back rather quick, if you need it just brush it up. If you don’t need it who cares. Polymorphism I can do…

Putting stuff in a switch means all the logic for what would be a function overload is in the same place, unlike objects where that logic would be scattered across multiple files. Variants can work better here but are less well known.

Re: Confessions of a Software Developer: No More Self-Censorship

#263
post #175

Earlier quoted context omitted.

> I have encountered people who are scared to post in large public channels. People weren’t assholes and/or snowflakes in those days. Implicit in being on the net was that you were fairly well behaved.

How far back are we talking? 90s? 80s? 70s? For the 70s, I would agree with you. But the moment home users, and particularly kids, gained access to the internet, you started to see a subculture of trolling. Source: I was one of those 80s kids. It’s not something I’m proud of, but writing bots to troll message boards and scrapers for porn and warez played just as significant role in my journey into my IT profession as…

Depends on a size of community and where.

Early 2000s, public channel on a LAN with ~3k people in a post soviet country – say something stupid to a wrong person and you'll find yourself with a broken nose, because the guy/gal is a friend of the admin.

Re: Confessions of a Software Developer: No More Self-Censorship

#264
post #22

Every time that I read this about remote work, all I can think is how much I miss IRC and the culture that came from it. We were doing remote work effectively decades ago. Don't have hallway conversations to fix bugs? Easy, just post your problems on the team chat and someone (often one of several people) would love to drop by to help. I'm not sure exactly all of the forces that have led to this changing so much, but…

I have encountered people who are scared to post in large public channels. Part of growing up in chatrooms was an implicit bravery of saying something out loud in a room full of thousands of people. There seems to have been a shift, somewhat, in the comfort level of different generations about saying things "out loud" in large public rooms. Chatrooms have evolved in a really interesting way. I think the first generat…

The "water-cooler" chats are in the same place/app as the more important conversations. I don't like getting pinged constantly for people just chatting, but I wouldn't want to mute it in case someone actually has something urgent to say. It's weird to have that all in one place with one set of notification settings on all of it.

Re: Confessions of a Software Developer: No More Self-Censorship

#265
post #121

Earlier quoted context omitted.

I think it's largely that as this became more of a business, the "yappers" who want to talk things out got more leverage as PMs, etc. It sounds like a caricature, but they honestly seem to get super antsy only typing and sitting in one spot.

I've never seen it put this way but I think you've hit the nail on the head. Text requires correctness to some extent; bullshitters will just yap away for hours and nobody can point to one piece of text and say "Here, this is where you are objectively wrong, and/or misrepresenting things". The unfortunate reality of remote work is there's a lot of zoom meetings where yappers in high places will BS away -- a lot more…

You seem to discount that the yappers are good and convincing writers as well

Re: Confessions of a Software Developer: No More Self-Censorship

#266

Well written article full of humility and vulnerability? I love it. My reaction: you don't need to feel ashamed of not knowing something, there is far too much to know and I'm still learning new techniques and concepts 37 years in, so I would never judge you for it. I would also not judge you for having your own preferences and opinions. I too prefer working in an office to remote work, but when I say this out loud o…

> I would also not judge you for having your own preferences and opinions. I too prefer working in an office to remote work, but when I say this out loud other developers take it as advocating RTO or saying remote work is worse when it just doesn't suit my personality. I get that it's a touchy subject but there is no need to get up in my face about it.

You ever wonder why? Serfes finally got freedom after corona, but apparently some actually prefer to be in a serfdom instead of having freedom to choose for yourself. You're being a useful idiot for managers, that's why you get backlash.

Re: Confessions of a Software Developer: No More Self-Censorship

#267
post #249

Earlier quoted context omitted.

His opinion on remote work is an opinion. The reasons he gives for having that opinion are not presented as opinion, but as fact.

Is your reasoning for your opinion that he didn’t preface his opinion as “in my opinion”? His words read the same as any editorial I’ve seen.

I am pointing out the fact that he is using factual statements in support of his opinion. "Remote work sucks" is an opinion. "Pair programming is less fruitful" is a statement of fact (regardless of the veracity of the claim).

"It is my opinion 7 x 9 = 63," wouldn't be an opinion in the sense that opinion was being used in the thread. Yes, we can question the veracity of a statement of fact, but that isn't the same sort of opinion as whether something is subjectively good or bad.

Re: Confessions of a Software Developer: No More Self-Censorship

#268
> Remote Work Sucks

> Remote work eliminates a lot of problems with office work: commutes, inefficient use of real estate, and land value distortion. But software development is better when you breathe the same air as the folks you work with. Even with a camera-on policy, video calls are a low-bandwidth medium. You lose ambient awareness of coworkers’ problems, and asking for help is a bigger burden. Pair programming is less fruitful. Attempts to represent ideas spatially get mutilated by online whiteboard and sticky note software. Even conflict gets worse: it’s easy to form an enemy image of somebody at the end of video call, but difficult to keep that image when you share a room with them and sense their pain.

Buddy, that's either a you problem or a problem of the software culture around you.

I've thoroughly enjoyed remote work. I thoroughly hate being in the office.

In the office, I can't type out notes nearly as quickly. I can't read people's inquiries two or three times to understand what they were asking in the first place.

Why should I form an "enemy image" at the end of a video call? I don't. But in a conference room? That is easy. I can see their faces, see when they're lying or hiding something, and it only ever builds drama.

Attemps to represent ideas spatially doesn't get mutilated by online whiteboard and sticky note software. Unless you don't know how to use online whiteboard and sticky note software. You need integration, you need training to use the integration, and you need to keep focus on the topic. You need to identify the ancillary information and objects. You can do all of that online while someone else is leading or speaking. Everyone can. It's a hell of a lot harder to do that when everyone is sitting in a conference room staring at the speaker instead of typing in their computer screens.

Asking for help is only a bigger burden if your culture allows information silos. Encourage your team to speak up into a common chat room. Let anyone answer the question instead of just whoever was asked. It's easier to develop empathy and watch someone grow when everyone is given the shared burden of answering questions. It's easier to identify what processes are causing the biggest problems when everyone can see the amount of questions or frustration about it. It's harder when that information silo is real.

Remote work is way better than in-office work. If you disagree then you are a very different person than I am, and/or have very different experience than I have.

Re: Confessions of a Software Developer: No More Self-Censorship

#269
post #195

Earlier quoted context omitted.

The question is whether enough of the other people around you have the same characteristic you describe that it's reasonable to require it for everyone, including the ones that don't. For those of us who don't work better that way, being required to go into an office in person to provide ambience for our coworkers is extremely dehumanizing.

You've brought in "require" from nowhere. Neither the parent comment nor OP's article mentioned _requiring_ in-office attendance for everyone on earth. Many people make this leap, so I don't mean to single you out. I think this is one reason this topic is so touchy -- it's hard to even express an opinion without someone assuming you mean to impose that opinion on everyone else (e.g. mandatory RTO), and then taking of…

[deleted]
Post reply on HN