#process

One of the things that I thought they said during the talk was that they were using .dot (GraphViz) as the language that they are using as the formalization for new processes for their coding agent. It made sense to me. There's enough dot on the Internet that models can read and understand it quite well. And it removes a whole bunch of the ambiguity of English language specifications.

That's an... interesting perspective: "Kanban is a paternalistic project management theory that aims to set developers on the right path. It promotes the idea that the manager is the arbiter of success and the deliverer of change. And like its forbear Scrum, its major proponents are those who don’t code for a living."

That's an... interesting perspective: "Kanban is a paternalistic project management theory that aims to set developers on the right path. It promotes the idea that the manager is the arbiter of success and the deliverer of change. And like its forbear Scrum, its major proponents are those who don’t code for a living."

"Agile" is kind of a dirty word in some circles, but this describe some actually agile ways to deal with revision control using git. "When we started using git to manage our source code at work, we actually jumped in a little bit too fast. It seems like there is a lot of writing about how you can do lots of really neat things with git, but no real guide about one particular way of using git for your project. This post is going to describe how we use git day to day on a reasonably large “agile-style” project."

Cue the Tina Turner... o/` We don't need another hero o/` "Managers: stop rewarding people for pulling long hours. Don’t punish them, of course, but rephrase the conversation within your company. If someone is working at four in the morning, something is deeply wrong. Figure out what’s broken and delegate the work out evenly across your team such that it doesn’t happen again. Don’t pat your hero on the back for “pulling another late-nighter”. You’re clearly managing someone highly motivated, but you need to shape that motivation into something more constructive. That energy needs to go into design, architecture, planning, and testing, not late night patch sessions."

"Software should be designed, written, and deployed in small batches.Small batches mean faster feedback. Small batches mean problems are instantly localized. Small batches reduce risk. Small batches reduce overhead. "

"The key idea in this system is that the web site exists on the server as a pair of repositories; a bare repository alongside a conventional repository containing the live site. Two simple Git hooks link the pair, automatically pushing and pulling changes between them. "

"the opening gambit for the vast majority of development efforts I have participated in where I have not been amongst the first generation of programmers to work on the project."