tonnydourado

I seriously doubt, since there actually is evidence that, for adults, psychological safety is a major factor in productivity at work, specifically at knowledge work.

Where's the big eraser from looney tunes when we need it

> same as my parents and theirs, which really suggests a genetic component

Does it? Could be as much a product of a privileged upbringing and generational welth reproducing themselves. Do you have an adopted sibling you grew up with, that had the same environments and opportunities, but turned out to be a moron? As a control group, you know.

I find odd how people are so quick to jump to genetics to explain a thing so complex as a human being inside a society. There's SO many forces acting on it at all times, picking genes over all the others feels like an oversimplification.

Short answer: no.

Long answer: fuck, no.

Longer answer: Even if he wasn't the big douche he is, I don't like his work philosophy and the kind of workplace that he seems to build, and I don't share his beliefs that they are necessary to build great things.

We have some templates for gitlab issues at work, and it always bothered me that all the colons had a space before it. Both because it triggers the same annoying emoji feature, and also because it looks weird to me. Now it all makes sense: although the templates are in English, they have been authored by a French person, so the rule just bled into English writing.

Things like chrome, or Linux, are so complex, and interact with so many different variables that it's completely understandable that it can have tens of thousands of bugs, and yet most people won't ever notice one.

Can you elaborate what exactly is the nuance I missed?

I'm sorry, I genuinely do not understand your point. If I think something you say is incorrect, and I say "Hey, I think this is not right. Not 100% sure, but I think it isn't", you're saying that this is not "saying that something is wrong"? English is my second language, so, I might be missing some nuance.

Maybe I'm not expressing myself well enough, but I'm not sure why you jumped from "telling someone they are wrong" to "antagonize and attack". I feel like you can almost always do the first without incurring in the second.

I 100% agree that if you tell people they are wrong aggressively and arrogantly, that will backfire, and they are probably justified in ignoring your correction.

But some people, and particularly some organizations, seem incapable of accepting even the most thoughtful correction, and that's the kind of place/people I'd rather keep a distance.

Saying that something is wrong doesn't imply (at least for me) that you're 100% sure that it's wrong. I always consider colloquial affirmations to carry an implicit degree of confidence, which is rarely 100%, and I often try to make that explicit by phrasing it like "I think that ...", etc.

So, yeah, I don't see a conflict on thinking something is wrong, pointing it out, and arguing for change, and at the same time be open to be convinced that it wasn't, in fact, wrong.

What other way there is to tell someone that they are wrong then, well, telling them?

> it’s better to be liked than right.

Broadly, maybe. At work, I don't care about being liked by people that can't admit they are wrong.

That doesn't being a dick to anyone I think is wrong. The whole point of telling someone that they're wrong is to correct course and fix things, and bullheaded, righteous, approaches never accomplish that.

But it does mean you don't keep quite. You don't give up. You ask questions, you try to learn. Because part of the process of saying that something is wrong is being willing to learn that maybe you are the wrong one.

I understand being unwilling to bulge to people that come in thinking they know better about everything. But I do not accept not even listening to someone that disagrees, that's a red flag,and I am out asap.

Well, it is a damn good story. People might have gone overboard on 2010, but every 18 months seems like an acceptable rate, to get new people introduced to the tale =)

One of the fake packages is called `felpesviadinho`, which looks like calling someone named "felpes" with a homophobic slur in Brazilian Portuguese.

The `@inlineCallbacks` decorator from Twisted. Not the implementation, even, just what it does. Understanding it was what finally made async click in my head.

I would add a "zero" best practice: don't. If you're thinking about writing enough shell script that it is worth putting it in a file, consider other languages or tools.

I'm not saying *never* write shell scripts, but always consider doing something else, or at least add a TODO, or issue, to write in a more robust language.

So, you've been screwed with in several levels, and I think that there's very little chance you get any payback. It happens. Put it in the lessons learned column and move on.

More precisely, move on to looking for a new job. If you have been very productive and have had lots of responsibility, that can go a long way to improve your resume. Update it, and start hunting. As someone else suggested, "Drop productivity, but no engagement", and use the extra time to job search.

One particular tip: if they put such ridiculous terms in the contract, you should probably do all job searching in your own hardware (phone, computer). Just in case.

Something Awful. That's what SA stands for. Makes much more sense then my first thought, Sexual Assault forums.

> Finally, the CCC appeals to the manufacturers of the connectors to look for honest ways of earning a living.

This is fucking brilliant XD

Not even in the same city of right.

How many software developers do you think can work in a kitchen? Or clean houses? Or work on construction?

Not gonna lie, I was triggered by the no CI/CD and shared database between staging and prod. But those concerns where very satisfactorily addressed. I'd miss some form of CI/CD if it was a team, but I suppose that for a single person show, running tests locally is enough.

I do miss infra as code mentioned. If shit goes tits up with the infrastructure and everything was setup with clicking around in control panels, ad-hoc commands and maybe a couple of scripts, your recovery time will be orders of magnitude bigger than it has to be.

I have Crohn's disease. My gut has been fucking with me since I was 12. I never trusted the bastard, and never will.

I tried to invent docker and kubernetes with LXC back when docker was super alpha and kubernetes was barely a fetus. I failed, obviously, but learned a lot. It's kinda the only reason I managed to pick up kubernetes later on, honestly. Sometimes, not knowing what you're doing is an asset.

A previous employer had the same issue, and solved it by writing the application to kubernetes and deploying minikube to the clients that didn't have their own kubernetes cluster.

To be fair, the situation ended up being: bunch of clients running minikube, 1 major client with their own kubernetes cluster, and a lot of other clients using the multi tenant, cloud hosted, offering. Made it a bit of a pain to support that one client with a cluster we could not control, but it was one of our biggest clients, so, them the breaks.

The "In my shoes?" bit was hilarious

Those are great examples

I don't. I just care about boxes and lines, most of the time. When I need to differentiate between types of boxes, I use shapes or stereotypes.

I've used Plantuml extensively, and still use it a bit, now and then. I don't remember ever needing or even wanting bi-directional editing. There's a lot of interesting things in terms of syntax and semantics here, but I really do not see WHY they are tackling a very hard problem on top of an already not easy one.

> For example, if you run

> stty intr '^X'

> then your interrupt character sequence will be Ctrl+X instead of Ctrl+C (!).

I have a feeling that if you actually do this in a real Linux system, a sysadmin will hunt you down and dismember you alive, but I might be wrong.