> another developer is seeing the code different than you.

but that's the whole damn point ... I like substantively indented code, you prefer minimally indented, we should both be happy (and we can be, by using tabs).

▲

jedberg a day ago | parent [-]

You could certainly make that argument. You could also make the argument that all the developers on a project seeing the same view of the code enhances collaboration and team cohesion, especially if your team does pair programming.

This is often why dev teams have more specific style guides that include things would be considered bike-shedding, like how many spaces an indent is.

▲

phplovesong 15 hours ago | parent | next [-]

Everyone is diffrent, some people might be visually impared, and having a bigger indent helps them out. The opposite also applies.

▲

rkomorn a day ago | parent | prev | next [-]

So are we also going to have team themes, team syntax highlighting colors, team fonts, team dark/light mode, team screen resolution, etc?

Why not bikeshed the bikeshedding?

▲

Lvl999Noob 7 hours ago | parent [-]

FWIW, team screen resolution is pretty much already there when the company provides the laptops (+ screens).

	▲	rkomorn 4 hours ago \| parent [-]
		People run different UI zoom levels with modern laptops and (especially 4K) screens.

▲

PaulDavisThe1st a day ago | parent | prev [-]

It seems that you don't understand what a tab character is ...

▲

jahewson a day ago | parent [-]

Wait, no, if there is an 80 character line limit and you like 4 space tabs but I like 2 space tabs, we’re going to have a problem. My code will exceed the line length on your screen or be forced to wrap prematurely on my screen to suit your preferences.

▲

sokoloff a day ago | parent [-]

I'm not at all convinced that an 80 character line limit makes sense on modern equipment.

On punch cards, teletypes, or VGA CRTs? Absolutely. On SVGA CRTs? Probably. On anything modern? No.

▲

jahewson 18 hours ago | parent [-]

Personally I use a 100 character limit. Anything more and the ability to have two editor windows side by side gets impeded upon. The point is, there is a limit.

	▲	sokoloff 12 hours ago \| parent [-]
		Eh. If 1 line of code in 500 has a trailing bit of punctuation scrolled off the side for 1 in 8 coders who have chosen to have both narrow windows and wide tabs, that hardly seems like a deal-breaker, but if it is, enforce common settings/standards. (I'm fully converted to Team Spaces, but I also don't get too wrapped up in treating what seem to be soft limits as hard limits.)