It makes coming up to speed on an existing codebase a slog because you have to trace through everything back to its source. Oh, and because there are magic methods and properties galore, your normal introspection tools in e.g. RubyMine get frequently stymied.
The example he gave where each dev gets a single feature done seems to skip over the opportunity that Dev A has - after she spends only "a couple days" on that feature to ship a simple solution, she now has the rest of that week to do another feature, and another... in fact, she could probably get 6 features done in the time that Mr. Complexity took to do his one feature (3 weeks in the straw-man example). Then the promo packet looks much better for Dev A - while it says "implemented feature X", it also says "implemented feature A, feature B, feature C...". Doesn't that seem more attractive?
Slightly related: I've noticed that there are lots of "ideas guys" (yes, guys) in our field who love to bloviate, and maybe even accomplish some stuff that looks really good. I have made a career out of just putting my head down and getting shit done. I may not have grand design ideas, and in fact have had to unlearn the "fact" that you need to come up with, and implement, Big Ideas. In my experience, people who "get shit done" may not get fancy awards, but their work is recognized and rewarded.
I think sometimes flip side is that the engineer looks like they just shipped a bunch of "small features" A, B, C... because the solutions were so simple
notable nitpick: calling DC a “federal entity” is mixing up the concepts of nation and state. (It’s also major erasure of the culture of people - mostly Black - who actually live there!)
The whole section around DC is..questionable. PG, Fairfax, and Loudoun counties are all in the Tidewater group that extends down to the NC triangle. Meanwhile Montgomery County, which is right over the Potomoc from Fairfax/Loudoun, is in a separate group that's shared with Philadelphia and Ohio? MoCo, Fairfax, and Loudoun are all incredibly similar both culturally and economically (i.e. wealthy DC suburbanites) and should either all be in the Tidewater category or in some separate "Capital Area" nation.
I'm not sure I'd extend it that far, but personally I could see at least to Woodbridge.
Another comment mentions this is based at least partially off original settlement/immigration patterns so I'm willing to be more leniant now, but at the very least inside the Beltway should be Federal entity/Capital area.
As a Sconnie native, the main thing that annoyed me about the letter system is that it's easy for the letters to rhyme; for example, near Verona (home of Epic!), there are (Dane) County roads PB and PD. Gotta enunciate carefully. :P This would qualify as a "usability issue" I would imagine. :)
Lots of things get weird in edge cases with SVGs. E.g., one thing that keeps biting me is that Firefox always snaps x="X" y="Y" coordinates on <use> elements to the nearest CSS pixel (even if the pixel size is very large), but allows transform="translate(X,Y)" to keep its full subpixel precision. I've taken to double-checking all my SVGs at 3000% zoom just to spot all the seams that implementations can create.
As in n+1 == n once you go past 2^24 on a float and here they are at 2^25-1. So it doesn't quite make sense as a reason to me.
There's a post above that browsers divide pixels into 1/64th of a unit which accounts for 6bits which puts this limit at precisely that of a signed 32bit integer. This makes much much more sense than the significand of a float.
The correct answer. In particular, up to 2 ^ 24 the float32 behaves like a regular integer, which can be important in some cases. Above that value, the integer starts to have missing values, and strange int behavior such as (n+1)+1 not equal to (n+2)
But why are 32b floats relevant? JS, the language famously representing ints as floats, uses 64b floats. Who puts ints into 32b floats and cares about precision loss?
I didn't say JavaScript anywhere in my comment. No relation to JavaScript. Rendering is typically done in tiles, in GPU, and the best precision that can be used across all GPUs is float32. Some GPUs don't implement float64.
“Craft” vs “delivery” is a false dichotomy. Someone who is “delivering” needs to understand what they are delivering! How can you support vibe-coded cruft that you don’t understand? This is why tools like TypeScript exist; TS by itself adds little in terms of functionality or in “deliverables”, but it makes the code more _understandable_. It’s worth the time to invest in making sure your types are correct because it makes you think about constraints. There are no shortcuts.
