I have absolutely no clue what on earth a browser for programmers is and why it would help me to 'think clearly'.
Contrast to Firefox and Chrome websites - both of which have a screenshot on their landing page.
It may help improve some tasks, but not exactly core product stuff.
If my capital were on the line, I’d be pretty annoyed seeing it spent that way.
I think you'll find you get a lot of mileage out of taking those particular glasses off from time to time.
I basically do this already with Firefox and TreeStyleTabs (but ad-hoc). Any middle mouse/ctrl+click I do on a link, opens in a new tab nested under the current one. So all HN stuff is under one tab that is collapsed, all GitHub stuff is under one and so one. Really effective when you do research, as you can do the initial search on Google, then every result you open goes under the existing tab, which is conveniently labeled via the <title> tag on the Google page.
https://www.businessinsider.com/how-to-organize-tabs-in-safa...
The apex of the argument came down to documentation quality, and at first I thought this conversation was over and A won a bunch of points. I forgot about it for almost a year and then it came back into my brain, moved into the upstairs room, and has been trying not to pay rent ever since. And this is what is playing in a loop in my head:
What if your documentation isn't shit because you are bad at explaining things.
What if your documentation is shit because you're bad at writing code that can be explained?
What if the process documentation isn't confusing and stupid because the author is bad at explaining things - what if the process documentation is stupid because the process is stupid and needs to be changed.
Another approach to this kind of thing is to reverse the sequence of "do it", "document it" steps and draft a rough version of the documentation up-front as part of an initial design, while it is cheaper to change the process or system, before work is done to implement it and roll it out.
Both groups fell into child-like glee when it was explained to them that SEI level 1 involves writing down your current process as it actually exists. Which meant they got to describe the dumb stuff they'd been putting up with for years, with various degrees of tongue-in-cheek humor, satire, and sarcasm.
- Send boss email
- wait 2 hours for reply
- bug boss about email
- find out IT Guy already left for the day
- Resume process in the morning
Things like that, and a good time was had by all.
I think it's great for greenfield work. Forget existing solutions, if you were looking for a solution, write out how you'd ideally like it to work, after it's written, figure out if you can create something that works like that