3 ms·

Fantastic insight, really top-notch. Just some random thoughts in no particular order - curious what you make of them: - On the subject of incremental pieceme

Fantastic insight, really top-notch. Just some random thoughts in no particular order - curious what you make of them: - On the subject of incremental piecemeal changes over time with no requirements: don't you all find that in your workflows (when you're doing something for yourself), it is hard to step back and "architect" something? It is easier to just let it evolve. - Likewise it takes real work and thought to organize something as simple as a spice rack. (I just keep opened packages of spices in the cupboard.) The knowledge that company is coming is one of the few pushes. But it kind of feels like it's being done for show. - It's hard to add architecture when you know there's no team that is coding against it as an API. It's just you. It feels like that extra power is, kind of wasteful. - The other thing is that it may be the case that you know there is some deeper level of architecture. In the case of my spices, for example, most of the opened spice packets I mentioned are actually mixes. (Such as grilled chicken spice mix.) - If I had to architect my own spice rack, I should start by learning which spices I'm actually using more of. And since what I'm doing works, I don't actually care. Plus, it would be a step down: the first time I mixed my own spices, I would probably end up with a worse dish than pouring some out of a premixed packet. - The first time you architect a "proper" framework rather than let your machine learning algorithm "overfit", the result is probably demonstrably worse. - That is a lot of pressure on not architecturing, and just continuing to (over)-fit.

jacob019 8y ago
well-constructed != over-architected
kthejoker2 8y ago
This is where good logging helps. The lifehack is to throw all your spices in a box and only pull hthem out when you need them and then leave them on the rack. Then throw away any spice you haven't used in n months and add it to a blacklist. The ones you use frequently should be prominently displayed and texted with extra care and possibly set up for autorenewal from the grocery. Only introduce new spices when there's a recipe, and buy just the amount you need. So too with code. Log your code paths, prune little used features, optimize the hell out of the most frequently used ones, introduce features sparingly and with purpose... I like this spice metaphor, thabks for it.

jacob019 8y ago

well-constructed != over-architected

kthejoker2 8y ago

This is where good logging helps. The lifehack is to throw all your spices in a box and only pull hthem out when you need them and then leave them on the rack. Then throw away any spice you haven't used in n months and add it to a blacklist. The ones you use frequently should be prominently displayed and texted with extra care and possibly set up for autorenewal from the grocery. Only introduce new spices when there's a recipe, and buy just the amount you need. So too with code. Log your code paths, prune little used features, optimize the hell out of the most frequently used ones, introduce features sparingly and with purpose... I like this spice metaphor, thabks for it.