HNHacker News
TopNewBestAskShowJobs

carl_sandland

238 karma · joined January 6, 2017

submissionscomments
carl_sandland··on Why do we fall into the rewrite trap?
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 running manifestation of everyone's understanding, of the architecture : it will and must change.

Viewed through that lens you can see;

* estimation is hard, as you are never really done.

* software has a very high maintenance cost, plan for it.

* architecture and design are important, longer term : spending more money on things with longer value life just makes sense.

* Interfaces are important and allow for rewrites on a smaller scale.

* you will always be releasing: focus on CI and devops to take the grind out of that.

Rewriting is a form of refactoring I guess: It's like chopping a leg off or something. One thing I like about microservices (or rather, strict boundaries) is that you can rewrite the worst part but keep the rest going.

Yeah and oh man I hate the "this code sucks" culture :(

carl_sandland··on Wildfires Are Raging Outside Every Major City in Australia
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 balance the environment with a healthy economy for all" I want to explode: what does that even MEAN. Economic activity is a function of human activity and humans need to like... breath?

I've been encouraged by some of the interviews and coverage with local government officials, they seem to be really shocked into a truth: I wish we could do better than a temporary 'concern' over the earth.

carl_sandland··on Wildfires Are Raging Outside Every Major City in Australia
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 we have to put them all out is not infinite.

* the transport network does not cover much of those areas.

* the population tends to cluster in or at the fringes of flammable regions.

* the weather and fuel load are combining into truly horrific, chaotic fire behaviour, that can create their own weather systems (fire storms).

It's a good question though! I wonder if we can invent some technology to solve this.

carl_sandland··on Wildfires Are Raging Outside Every Major City in Australia
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...) which has air pollution literally OFF their chart ranges.

Hearing the drivel spewing from our PM and other politicians; It's always the same pandering responses with no real strategic change. It's beyond frustrating. We will have to be destroyed (are being?) before anyone admits there is are real problems requiring real actions. I have noticed that at a more local level of government, the messaging has changed and is more serious now.

Here are some thought bubbles;

* more aggressive back-burning and fuel load management: managed at a federal level by law.

* stop all new coal, keep replacing with ?whatever?, including a reappraisal of nuclear.

* start retreating populations back towards cities: reverse the sprawl into protected urban bubbles.

* start requiring building to have ventilation and filtering systems that can handle smoke better, and are more efficient at sealing air: I've heard many people complain about smokey insides: happens to me too !

* stricter criminal penalties for any arson related crimes.

* restrictions on tourism to risky areas during the fire season.

Either that or we finally DO become a giant desert from coast to coast: should be safe enough then!

carl_sandland··on Things I’ve learned in 20 years of programming
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". I like to think of it as "chasing the white rabbit". One thing that can help is to write a detailed plan of what your coding session is going to achieve, with some stretch goals. If you do it right you will enter a cycle of achieving small goals leading to refactoring and bigger goals and then you.... look up and the whole team has gone to get Tacos without you again.
carl_sandland··on Things I’ve learned in 20 years of programming
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 formal sense, all day. Thankfully I just quit. I guess I prefer my coding to be less than extreme.

2. As others have mentioned, short term pair programming (never works >2 imo) is an excellent way of transferring knowledge (a model) to someone else, or to make progress on complex problems when you are stuck (the rubber duck effect is real).

3. I'm afraid I really must be getting old as I've never heard of "mob programming", and to be frank I've spent the last hours being horrified that such an idea exists. I guess in a way code reviews can be like that sometimes. lol.

carl_sandland··on Things I’ve learned in 20 years of programming
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, or maybe arrange.

2. never pass up a customer focused activity, volunteer and push to be involved.

3. ask a sales or business guy at your company to be a mentor.

4. talk to random people beyond small talk (parties?).

5. read books (mileage varies).

Something like "toastmasters" for coders would be so cool.

carl_sandland··on Things I’ve learned in 20 years of programming
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 until you look up and everyone has gone to lunch. I'm tilting at the open office windmill and idea that whilst I'm actually coding, I need to interact with others.

Being a "Developer" (planning, designing) is very social, however writing the actual code, for me at least, is a very inward activity and suits my quiet personality. The problem here is that non-coders don't understand this and it can cause a lot of friction when working in the usual group office environment.

It's a catch 22, people want me to code for them, but then they have a problem with me socially when I'm trying to code ;)

carl_sandland··on Things I’ve learned in 20 years of programming
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.
  3. there is no silver bullet (read mythical man month).
  4. fight complexity and over-engineering : get to your next MVP release.
  5. always have a releasable build (stop talking and start coding).
  6. code has little value in of itself; only rarely is a block of code reusable in other contexts.
  7. requirements are a type of code, they should be written very precicely.
  8. estimation is extrapolation (fortune telling) with unknown variables of an unknown function.
  9. release as frequently as possible, to actual users, so you can discover the actual requirements.
  10. coding is not a social activity.
carl_sandland··on Things I’ve learned in 20 years of programming
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 what API to build ? Because the code needs it. How we know the code works ? Because I just ran it.
carl_sandland··on Things I’ve learned in 20 years of programming
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 TDD is frankly ridiculous; I've seen many teams spending more money on gold-plating test lines of code than actual code. I've seen other, better teams spend all their efforts on full integration testing only. There are no golden rules, it's just hard work.
← PreviousPage 2 of 2