3 ms·
If you genuinely think you have a better way to do it, propose it. Don't sit back with the terrible attitude of "my company does it this way which sucks" - why
by whalesalad 4y ago
If you genuinely think you have a better way to do it, propose it. Don't sit back with the terrible attitude of "my company does it this way which sucks" - why not try to make things better?
There are two possibilities - a) you are right, you know something your company doesn't, and by proposing your new plan in a constructive manner you might make life better for everyone b) you are wrong, you don't fully comprehend the surface area of the software you are working on, and your suggestion is short sighted and doesn't account for all of the requirements.
Either way it is helpful to put it out there - so long as you do it from the right place, with the right intention. Either you'll humble yourself, or you will eliminate an unnecessary dependency and make life easier for your team.
- grosswait 4y agoThey lead by saying how much they liked asdf vs docker. Ergo: proposed solution is asdf no?
- counttheforks 4y agoThen why does their company still use docker for that? Did they fail to convince anyone else? Did they disagree? Did they not even bother bringing up their frustrations? People love to complain, but rarely try to contribute to actually make things better.
- waboremo 4y agoIronic, it would have been far more helpful to just ask OP "what are the reasons your company still uses Docker?" instead of mindlessly complaining.
- anonyme-honteux 4y agoCounter argument: your version is fine and may have helped to solve one particular issue in one particular company. But countless developers in countless companies have each their own set of frustrations where they sense that something could be improved but don't know what to do with the frustration. Frustrations are a useful symptom but learned helplessness is a terrible thing that can lead to anything from being annoyed to leaving your job to depression. I would argue that the response was in fact a very valuable lesson.
- viraptor 4y agoThe tool doesn't have to be just better. It needs to be so much better that it's worth: changing defaults / what people use now, changing documentation, verifying it works for all projects, ensuring that nobody has use cases that asdf doesn't address, and actually spending time with the decision maker to present your idea. For a larger company that may mean days of work.
- bipson 4y agoDays? In the "big 'ol" companies I worked at, something like that takes months! If even possible...
- searealist 4y agoHuh? The whole comment is comparing asdf to docker and saying asdf is better.
- Scarblac 4y agoHe's talking about doing something about it in his job, instead of complaining about it on HN.
- firecall 4y agoThat right there is text-book Ad Hominem fallacy! It is totally valid to point out failures in something without knowing how to put them right, or being in a position to do so.
- jfabre 4y agoExactly, let's first acknowledge there is a problem, then we can find a solution. Complaining for complaining is not helpful, but don't dismiss problems because no one can think of a better solution at the same time.
- verdverm 4y agoSometimes the problem is more that the grass looks greener on the other side. When you realize there are a bunch of day 2 problems for the "better" solution you didn't uncover beforehand, many will enter sunk cost territory