my tweets
- @shanecorning it's about everything after that (pushing code live, monitoring then making decisions quickly and automaticall) 4 mins ago
- @shanecorning agreed, most people aren't good enough programmers to actually do this to be honest, it's not just abut writing your app (cont 5 mins ago
- @shanecorning wait til he talks about the deployment process, how they monitor and stagger the rollout. 6 mins ago
- @shanecorning I mean if you commit and all your tests are green, why not deploy? 6 mins ago
- @shanecorning reason: if you can deploy that fast, you should be able to roll back even faster. 7 mins ago
-
RSS Links
Archives
Blogroll
Author Archives: jonezy
so
i tried upgrading my blog here to 2.9.1 but i couldn’t because the version of mysql 1and1.com is using is too old.
completely fucked i tell ya.
Posted in Uncategorized Leave a comment
Infecting a team with Agile: Part 3: Educating Management
In part 2 of the series we reviewed some ways to bring an inexperienced development team up to speed on some of the core concepts and fundamentals of agile. This week we will talk about the same topic but with a different target audience. Management.
Now a good friend of mine, and colleague that I learned [...]
Posted in agile, agile-series, work Leave a comment
Infecting a team with agile “Part 2″ – Education
In part one of the series I covered some of the preparation I had to go through to start on the journey of getting my new team infected with agile. Things have been going ok, there are some improvements to some of the tools I would like to see, but hey that’s the point right? If it doesn’t [...]
Posted in agile-series, work Leave a comment
Infecting a team with Agile: Part 1 – Preparation
One of the core tenants of agile is:
“Individuals and interactions over processes and tools”
But anyone that has done any work in an agile shop knows that to achieve many of the goals of agile you need to have certain types of tools in place to facilitate the process. This past week I have been preparing [...]
Posted in agile, agile-series, richmondday, work 3 Comments
Infecting a team with agile
Part of what I’m doing at my job is getting the development practices we use internally up to date. Previous to my current job i worked at a company that went through adopting agile as it’s primary development practice. The result was a fantastic working environment and that is my goal here, to create a [...]
Posted in agile, agile-series, richmondday, work Leave a comment
Connecting to different database on the fly using Subsonic 2.x
Recently I started working on a project at work that requires me to connect to more then a single database at a time (different parts of the app connecting to different databases at the same time). I figured this should be pretty straight forward, Subsonic is relatively mature and should probably support this out [...]
Posted in development, programming, work Leave a comment
subsonic won’t update my bit field?
I recently ran into a really strange problem while using SubSonic. I had a bit column in my database that was set to not allow nulls and had a default value of false. Pretty standard stuff in the world of database design I guess.
When it came time to start saving my entities to the database, [...]
Posted in Code, SubSonic, programming, work Leave a comment
xcopy won’t copy .css files
I use xcopy as part of a build script to copy a bunch of files and directories from a subversion checkout directory to another directory so that I can zip them and upload them to a server.
I have an exclude file that I use to tell xcopy to ignore files like the obj directory and [...]
Posted in agile, programming, work Leave a comment
If your gonna fuck up, do it early
I’ve worked in the online industry for the last 12 years or so, one thing above all else I’ve learned in my time in this industry
You are going to fuck it up
Now I use the phrase “fuck it up” in place of fail for effect, for impact, ya know if this was a power point [...]
Posted in agile, development, programming, work Leave a comment
Infecting a team with Agile: Part 4: