Most human systems would rather fail together than succeed. Most systems are built for nothing but subsequent failure (even if it's 300 years into the future). Think about that.
Where did you got that? Is some reference? Did you mind to share?
Don’t point out something wrong immediately
161–170 of 180 posts
Re: Don’t point out something wrong immediately
#162Earlier quoted context omitted.
Who said anything about yelling...
Fair enough. I think I may have misread the tone of the post I'm responding to because it happened to sound similar to a line I had just heard in some media - which was used by the character to justify yelling at people. In that case, it's one of those weird brain associations that pops up. I stand by the rest, that being unpleasant or hard to work with will make it harder to do cool things. Unless you are literally…
[deleted]
Re: Don’t point out something wrong immediately
#163Earlier quoted context omitted.
I think it is most often wrong to use the word 'wrong'. That implies there is the right way and the wrong way. But in fact there are only better ways and worse ways, to do things. The "right way" somebody envisions to be THE right way can be worse than something even better. So instead of saying "Hey you are definitely doing it wrong" you can say "I can see an alternative way of doing this which might be better in so…
We just have a guy in the team (he's smart, but very abrasive) who instead of using the word "wrong" uses "antipattern" for everything. And usually those are mostly his unfounded opinions on something but taken as a gospel as it sounds authoritative.
I know that guy
Re: Don’t point out something wrong immediately
#164Just be careful, because, as a manager, you can easily lose your best people, if they constantly have to review bad code from "productive" junior developers, need to manage how/when to deliver the review and then they are expected to work on the same code-base. This needs to be balanced.
Re: Don’t point out something wrong immediately
#165Earlier quoted context omitted.
I think it is most often wrong to use the word 'wrong'. That implies there is the right way and the wrong way. But in fact there are only better ways and worse ways, to do things. The "right way" somebody envisions to be THE right way can be worse than something even better. So instead of saying "Hey you are definitely doing it wrong" you can say "I can see an alternative way of doing this which might be better in so…
> I think it is most often wrong to use the word 'wrong' agree, that's why the word "wrong" in in quotes in my post. I usually say "I see a potential problem here" and explain why I think it could be.
It is just one of those words, like never say never.
I think the article has a good point, it's not good for team dynamics if we are often and overly critical of other people's accomplishments. It is their baby after all.
Re: Don’t point out something wrong immediately
#166Earlier quoted context omitted.
The other side of this is how nearly every engineer is going to trash talk the prior coders, when they inherit a codebase. So I already know to ignore it.
> trash talk the prior coders This is one of the things that make the software life worth living! It's even better when you realize that the prior coder was, in fact, your own damn self.
Its so embarrassing
Junior engineer logic
Re: Don’t point out something wrong immediately
#167Earlier quoted context omitted.
I appreciate the sentiments. i think the cert for https://cieloconnects.com/ is expired.
It isn’t expired, look more closely at it. (And, cough, see thread topic)
take your own advice. i noticed a cert was invalid or broken and mentioned it to a person who might care or know how to deal with it appropriately. In the meantime the site is less secure than it could presumably be. i'm not a paid consultant for the site so i didn't bother digging in and finding out which policy violation triggered a browser warning, but since you did, you can share it here or you can continue to add zero-value comments.
Re: Don’t point out something wrong immediately
#168Earlier quoted context omitted.
> we never got the time to fix it The older I get the more convinced I become that this is Learned Helplessness. "We didn't have time." is essentially the same dodge as "C'est le guerre" was in France. "We don't have time" is a conversation killer. "We are working on that bit by bit" is essentially the same statement once you've subtracted the helplessness. Nobody is ever gonna schedule time for you to have integrity…
The goal of writing software is rarely to produce a piece of well-engineered software. More commonly, the goal is to produce a product in a given time frame using the team of engineers available, which may be of variable quality. If you’re trying to make the software perfect, you’re likely doing something very wrong.
This is basically fixed-time vs fixed-scope. You're detailing fixed-time, but fixed-scope projects do also exist.
Re: Don’t point out something wrong immediately
#169Earlier quoted context omitted.
It isn’t expired, look more closely at it. (And, cough, see thread topic)
take your own advice. i noticed a cert was invalid or broken and mentioned it to a person who might care or know how to deal with it appropriately. In the meantime the site is less secure than it could presumably be. i'm not a paid consultant for the site so i didn't bother digging in and finding out which policy violation triggered a browser warning, but since you did, you can share it here or you can continue to ad…
How did you even find that site in the first place? It's not in their profile, it's not in the top duckduckgo results for "CIELO Enterprise Solutions". How long were you digging around to find something, anything, to try and pwn them about their high engineering standards comment?
Re: Don’t point out something wrong immediately
#170Earlier quoted context omitted.
The goal of writing software is rarely to produce a piece of well-engineered software. More commonly, the goal is to produce a product in a given time frame using the team of engineers available, which may be of variable quality. If you’re trying to make the software perfect, you’re likely doing something very wrong.
Businesses are in business to stay in business. Frequently nobody notices how much decline in capability the team is struggling with because 1) the change comes slowly, and 2) people are getting 'better' at taking calculated risks that keep the tempo up, masking the real situation until the company hits a brick wall and all estimates go from 3 weeks to 3 months overnight. As a customer these sorts of changes in behav…
> Businesses are in business to stay in business.
Most of them do that quite regardless of whether they have any integrity or not.