Earlier quoted context omitted.
This is why linters are configurable; if your team doesn't care about consistent use of semicolons, ignore that linter. Right?
I have similar feelings as GP about Black (probably the most popular python code formatter), which goes by the philosophy that linters should not be configurable because that just moves conversations about styles from the code to which rules to use.
Woodworking as an escape from the absurdity of software
541–545 of 545 posts
Re: Woodworking as an escape from the absurdity of software
#542Earlier quoted context omitted.
I've lost my cool one time when a very young "manager" asked: "Do we have a backend resource on this call?" It really got my blood boiling and I've said something very similar to: "No we don't have a resource on the call, we have engineers, colleagues, employees, humans and friends on this call. Resources are air, water, memory, cpu and time, please don't call people like that". This followed by silence, and a lot of…
But resources are what you are, hoss. Sounds like the youth of this manager got you messed up. Old head move is to pull him to the side, with the sotto voce, give him a chance to show you he is open to feedback. How can he change now without losing something? This is workplace 101 stuff.
You can keep calling yourself whatever you like, or more to say, swallow whatever little pride you still have. But I don't subscribe to that and I won't be called a tool/object/resource in my presence.
Re: Woodworking as an escape from the absurdity of software
#543Earlier quoted context omitted.
It sounds like modern day slavery, or perhaps more precisely "corvee" labor. You have to toil away on your master's land before doing your own thing. I find it unbearable, but sadly much of the world has to deal with it.
You are mocking the suffering of actual slaves by comparing a modern highly compensated office job to slavery.
Re: Woodworking as an escape from the absurdity of software
#544Re: Woodworking as an escape from the absurdity of software
#545Earlier quoted context omitted.
That desire is in conflict with a desire for the reviewer to see only the changes and many of the diff tools don’t diff this reformatted code against that reformatted code but rather work on the pre-reformatted. It could obviously be done, but involves a yak shave that isn’t clear that it brings enough value to be worthwhile.
That's my main concern, I want to review the changes, not formatting opinions.
If it is formatted to the formatting rules before every commit, how can there ever be formatting opinions?
What am I missing?