carl_sandland

10 ms·

31.
by carl_sandland 7y ago
This notion of code being "done" is the root problem. This idea that you write something and ship it and that's over is wrong. Code is never done, it is almost biological in its emerging complexities. The current code is the
32.
by carl_sandland 7y ago
Yeah it's depressing, but have you not noticed a change or shift in tone at least in the media ? I'm hopeful this swings the focus back onto science and mitigation, and away from the economy. Every time our PM says "we must b
33.
by carl_sandland 7y ago
Have a look at the regions involved; https://www.rfs.nsw.gov.au/fire-information/fires-near-me * the number of active fires is high. * we have no proper rain and the ground is like DEAD dry. * the amount of resources w
34.
by carl_sandland 7y ago
Here in Canberra, it feels like I'm living in a space station on a toxic planet; I haven't seen blue skies in a month. See this chart ( https://air-quality.com/place/australia/australian-capital-t... ) whi
35.
by carl_sandland 7y ago
I was going to type a more detailed response, but the people below have done an excellent job already. The body has to be balanced, distractions at a minimum, the mind open and curious and the problem "not too easy and not too hard&quo
36.
by carl_sandland 7y ago
Some thoughts; 1. At some point in the 90s there was an "Extreme Programming" movement, or XP as it were. I distinctly remember the dogma built up around this, to the point where I started being forced to do pair programming in a
37.
by carl_sandland 7y ago
That's a really good question; I'd pay good money for developer focused communications training. Some practical ideas; 1. try to engage at work with more activities, you'd be surprised what activities you can help out with, o
38.
by carl_sandland 7y ago
np. The "Stuff" that surrounds coding is very social (point 1), but the actual activity of writing code is very inward focused and ideally uninterrupted. The idea of FLOW is a very real thing, its very zen: hours just fade away un
39.
by carl_sandland 7y ago
Some things I've learned after 35 years; 1. learn how to communicate: being a good developer requires as much (more?) social as it does technical skills. I would recommend formal training and practice. 2. question all assumptions
40.
by carl_sandland 7y ago
If I was arrogant enough to consider myself a good programmer after 30 years of doing it, I would suggest as humbly as possible, that perhaps TDD is something better coders can do in their heads and 'skip over'. How do we know wha
41.
by carl_sandland 7y ago
This is not the best advice I've ever read, some of it smacks of "silver bullet" thinking. For example, it's sometimes better to duplicate than couple. Within the same component sure don't copy pasta. Also I think T