HNHacker News
TopNewBestAskShowJobs

0xblood

81 karma · joined August 26, 2022

submissionscomments
0xblood··on Holonforth
Neat, but not more. I prefer to define my own context (splitting into files as I see fit) and using code folding etc. which can achieve a similar result without fundamentally changing workflows (as others pointed out - editors, git, grep, ..). Each time you want to write a new function ("word" I guess) requires somewhat of a context switch as you have to navigate through a GUI to where it should go, where just swapping files in my editors buffers feel more naturally. But then again I have never tried working like this and maybe I'd have to try
0xblood··on Europe is in danger of rolling electricity shortages
>found during inspections in October 2021

That's a year ago, would you say they scheduled them for this year?

0xblood··on Please don't be spooky
The problem is that this becomes more difficult the more unpleasant the topic is. If you have to talk with somebody because there was a complaint about them, and you send the invite "Re: X project issues" because that's where the original complaint originated from you end up in the same situation - that was what I was trying to say in my OP, because then people will say again that it is too broad and anxiety inducing. If you are upright "Re: Complaints about your behavior in project X" you get the employee all riled up and panicking, potentially overreacting and not getting any rest until the meeting actually happens

EDIT, NB: E-mails are typically archived and have to be produced in case of a litigation, or could be requested by HR. You might be fully on the side of your employee and don't want keep an explicit record of this as it might be misconstructed ("Well there were records that XXX misbehaved before" etc)

0xblood··on Please don't be spooky
Yes, that's what I mean with establishing it to be normal and not only when there a bad news. That way you don't automatically assume it's bad when someone just wants to pull you by the side for a quick conversation about something complex but harmless.

I'm curious, how would you suggest people higher up in the org chart start the conversation with you otherwise? Would you prefer them outright telling you the bad news directly with a quick summary, maybe even in public? Don't get me wrong, a lot of the typical HR procedures for bad news are pretty messed up, but then again I don't have any better idea which is why I'm asking

0xblood··on Please don't be spooky
>Who is "we" here? Everyone?

Regarding your other points, of course I try to be specific, already because it makes context switching easier and is generally more productive. However, in some situations you want to be vague. If you want to get the opinion from someone and don't want to discuss this with everyone else around for example, or if you want to hear their immediate idea right now without overthinking it, etc. Not very common, but also nothing bad about it in my opinion.

The problem is that the actual scary conversations are always masked as an innocent one for exactly the reason to not induce panic, nobody will say "you have a moment to discuss your performance wrt/ the layoffs that will be coming?". This sucks but that's how things are. If we change our language and interactions to make it impossible to take somebody aside without being explicit about that it's not scary - how do you take somebody aside for an actual scary conversation? These should be anyways rare and typically not coming out of the blue and if somebody is constantly anxious that they might have done something terribly wrong there are deeper problems in your employment relationship

0xblood··on Please don't be spooky
For obvious reasons I avoid this as well. However, sometimes it's just simpler to take somebody aside without specifying context (or very vague), because somebody else in the group might feel VERY STRONGLY about that new deployment, overhear that it's about that and try to inject themselves
0xblood··on Please don't be spooky
My point was that we can just establish that "have a sec?" is (typically) never spooky, this is a different way to combat anxiety and ultimately makes working together more straightforward and simple.

The scary stuff is always meant to exactly resemble an innocuous request in the attempt to exactly not panic the employee even though they have all right to be panicking

0xblood··on Please don't be spooky
The more we become overly sensitive, the harsher it will feel if we accidentally miss being overly sensitive. Now you tell me I shouldn't use "you have a sec?" ? if this goes on where are we going to be in 10 years? No personal communication at all anymore because it might make somebody feel anxious and I can only have a personal discussion with them if I send a week before a full agenda and rundown?
0xblood··on Factorio is coming to Nintendo Switch
I also find it rather obvious to the point I consider the game a masterpiece in satire, in a very dark and twisted way. I think it's the most cynical game I have ever played and I love it for that
0xblood··on Pushing Back on the Expanding Universe Theory
>I want to state up front that I believe the Earth is not flat, [...] and that Joseph R. Biden won the 2020 U.S. presidential election without rigging the outcome.

Stopped reading there, not because I think the "election was stolen" but because I have no idea what petty US politics have to do in an article about astrophysics

0xblood··on My Surreal Experience with COBOL
>I am fascinated by how this 70-year-old creature has kept many similarities to today’s stacks, for example with IF and SWITCH

If you like that, I recommend you take a look at a language called FORTRAN (2 years older than COBOL and still used). And if you enjoy legacy and good design still being alive, LISP (1 year older) will blow your mind.

← PreviousPage 2 of 2