rgoulter

135 ms·

1531.
by rgoulter 8y ago
I'd guess episodic and spacial memory help. All the tabs I'm likely to access together are close together, & were opened at similar times. (So, you can remember what the page was about without needing the full title to associa
1532.
by rgoulter 8y ago
http://wiki.c2.com/?ConwaysLaw "Conway's Law" is something like "organisation of code will match the organisation of people". It's a neat description. I think it's more common to merge or
1533.
by rgoulter 8y ago
"Wizard, Engineer" reminds me of Yegge's "Software Liberal/Conservative" approach to risk. https://plus.google.com/110981030061712822816/posts/KaSKeg4v... Albeit, rather than "wi
1534.
by rgoulter 8y ago
AFAIU TDD, it's beneficial to have an automated test than can check what I'd check manually if I didn't have automated tests (since automated checking is quicker, and is consistent). One benefit of writing a test before fixin
1535.
by rgoulter 8y ago
I made use of ANTLR4 for parsing C to write a "worksheet" (like Swift's Playgrounds) tool: https://github.com/rgoulter/c-worksheet-instrumentor It's an example of what you can do with "specific
1536.
by rgoulter 8y ago
In terms of "value for effort", this sounds like a cool idea. I'd guess this approach also struggles with multiple-line input like if/else, loops, functions. I'm reminded of https://github.com/jcartl
1537.
by rgoulter 8y ago
WEwLC is excellent. IIRC, its definition of "legacy code" is "untested code". End to end tests are great for providing confidence that the code does what it says on the box. Though end to end tests are slower than unit t