The system should support this, e.g. via // @formatter:off/on tags
428 karma · joined January 8, 2019
- they have probably never worked on a codebase where files are edited by more than 1 person
- they have never done any significant amount of merging between branches
- they have never maintained a large codebase
- they have never had to refactor a large codebase
- they don't use diff/comparison tools to read the history of their codebase
- they have never written any tooling for their codebase
- they are not good team-players and/or only care about their own stuff
2 years ago I switched to a 55" 8k TV as my primary monitor.
While everyone was giving me the usual crap about it, this guy, when I showed him what it would look like with 400% Zoom, he went and bought one for himself at home.
He thanks me every few weeks, but still didn't dare to set one up in the office.
(ps I have mine standing on a normal height-adjustable table, so you wouldn't have to hunch at all)
Not that I would ever want to give up our monolith, but we do experience the problems you point out.
I would like to work with this person.
My most important criteria is: What does my social circle use.
About once a year I try to cancel all subscriptions, and then resubscribe to those that I miss.
I believe it will help me deal with the current doomsday news (and be more stoic in general).
Don't force 'clever' solutions if you're looking for readability, maintainability, changeability, debuggability etc.
On the other hand, our company doesn't do any technical interviews at all, so there's that.
I agree so much with the paragraphs about "Dependencies" and "Tooling".
Who knows how much it will cost... My theory for the low prices for the 55" 8k TVs is that most people in the TV market go for the 65" version.
Regarding reading distance: For me the important part is to sit straight and avoid hunching. Choose a combination of distance and screen scaling factor that works for you...
I have been using a 55" 8K QE55QN700BT ($1400) at home since Jan. 2023 and a 55" 8K QE55QN700C ($1100 on sale) at the office since August 2023.
I can tell you that I will never go back, but there is definitely room for improvement.
Biggest negative: Sitting close (~12"), the far areas are probably at >45° angle (and TV colors are not great at angles)
Eye strain is ok (lowest brightness & low contrast), but neck strain is a thing (which I never had before, but now I think my neck muscles start to be trained and it's getting better).
Price is amazing, compared to 4x 4K
Refresh rate 60Hz: not for ego shooters (but great for work)
I didn't think it was possible, but at work I operate an 8k, 4k, and a full HD screen from the same graphics card (i need the other screens for UI testing)
Glossy is not great (no matte TVs on the market)
Even at 12", I operate Windows at 175% scaling, so I still have pixels to spare. Next TV will be 65" :)
At the beginning I thought it was a failure, until I found the correct settings combination: TV Gaming Mode, disable all AI image gimmicks, set the correct refresh rate in the NVidia driver options (at first everything was extremely sluggish, until by chance I saw that the refresh rate was set to 30Hz by default). I also remember playing with the V-Sync settings until finally I didn't see visual pixel artifacts anymore. Now the quality is the same as my 4k monitor.
Work colleagues just can't see it... (just like they laughed at the 2nd monitor, and then at the 3rd, and now most use 3 monitors).
No hassle with monitor arms. Such set it on the table and done.
Microsoft PowerToys FancyZones is amazing to divide the screen into areas
Next: TCL unveiled the first curved 8k 65" TV, that's where I'm going :)
= Software consultants and free lancers. I don't like them because I am jealous that they get to do greenfield projects and make all the architectural decisions but never actually have to maintain their own creations (and therefore never really learn how to design a system for changeability and maintainability).
> What can we do about this state of affairs?
1st: be aware of these laws and that keeping a 20 year old system in production is a non-trivial task and to be proud of every additional year I can keep it running.
2nd: Instead of seeing it as a 'DoS attack on myself by previous developers', I try to see it as a neverending Sudoku that challenges and stimulates and pays me every day.