Applied to an L5 software engineering role via e-mail and without any other contact I received back a bunch of questions that clearly look like they're aimed at L6 or even L7. Not sure what to do with that so I withdrew. Briefly considered answering them but was weirded out.
Any conversation
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
๐ฒ๐ ๐๐ฐ๐ฏ ๐ฆ๐ฏ๐๐๐ฒ๐ผ๐ ๐ ๐๐ซ๐ ๐ฅ๐น ยท๐ก๐จ๐๐ฉ๐ฏ๐ฐ๐ ๐๐ต๐ ๐ค๐ฑ๐๐ค๐ฆ ๐๐ด ๐ ๐๐ฆ๐ฏ๐ผ ๐ฒ ๐ฅ๐ฑ๐ ๐๐จ๐ฅ๐ฉ๐ฏ ๐๐ง๐ฎ๐ฆ๐๐ญ๐๐ฐ, ๐ฅ๐ฐ๐๐ด ๐๐ต๐, ๐ฎ๐ฒ๐, ๐ฏ ๐๐ฆ๐๐ฉ๐ค๐.
Iโve been inspired to cook more Japanese food lately so for dinner I made salmon teriyaki, miso soup, rice, and pickles.
Ikea has rules for naming products (so in theory, you could figure out what it is from the name) -> www.ikea.com/โฆ/6f564c4d-2ccc-46de-โฆ545a3948dc79.html
Sharing a link to my music blog: crusty-metallian.net
Not a lot of content yet, it's a work in progress :)
I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
