tekx – continuous inspection and integration of PHP projects

“Countinous Integration is about preventing your developers from burning in Integration Hell” – @s_bergmann Integration Hell My code is perfect,…

“Countinous Integration is about preventing your developers from burning in Integration Hell” – @s_bergmann

Integration Hell

My code is perfect, yours is pretty good and then Martin…well, he’s a fucking idiot. (lost where he was going with this story). D=

Team member should integrate their work frequently. This reduces errors when managing multiple team members. The value (ROI) is in:

  • reducing risk
  • reduce repetitive processes
  • generate deployable software
  • enable better project visibility
  • establish greater product confidence
  • helps with late discovery of defects
  • prevents low quality software
    • coding standard adherance
  • prevents lack of deployable software

This practice focuses on software design that uses unit tests to prevent and detect defects. This all significantly works to provide significantly better quality software.

tekx – code release & management

Image of EliW @eliw starts off laying down his street cred. He’ll be covering how to control the process of…

Image of EliW from Twitter
Image of EliW

@eliw starts off laying down his street cred. He’ll be covering how to control the process of version control. As we’ve been going over the past week, use version control. The talk will be focusing on subversion as the technology but the talk will be dealing with the higher level concepts.
Basic Version Control Terminology

  • commit/check-in
  • branch
  • tag
  • trunk
  • merge

tekx – date and time with derick rethans

Image via Wikipedia We’re starting with a map of the world showing the 24 major timezones. Timezone changes (daylight savings…

This is an SVG version of the Time Zone map fr...
Image via Wikipedia

We’re starting with a map of the world showing the 24 major timezones. Timezone changes (daylight savings times) make things tricky. The abbreviations for timezones aren’t enough to determine the user’s timezone. EST can mean different things.

The 64-bit signed integer used internally provides more than enough time for us to use (+/- 90 billion years if I heard correctly). strtotime() and functions with timestamps have been replaced with classes (such as new DateTime()).

The bundled timezone database has 564 zones so far that isn’t dependent on timezone abbreviations. They have the format Continent/Location or Continent/Location/Sublocation like Europe/Amsterdam. Updated database is released 20 times a year. Some changes are very sudden. Basically, you’re timezone database is probably outdated.

tekx – zend_form

Image of Rob Allen Trying to record @akrabat‘s talk about zend_form but didn’t get good camera placement. Won’t be able…

Image of Rob Allen from Twitter
Image of Rob Allen

Trying to record @akrabat‘s talk about zend_form but didn’t get good camera placement. Won’t be able to put up the video I do have until after Amsterdam. Will need to get a voice recorder instead.

Filters are destructive. This is important to know that. Validators only reject data. Decorators are used for form rendering. Apparently I’m not the only one confused by it because Rob Allen said we’ll go over that extensively. Zend_Form decorators are a combination of Decorator and Strategy Pattern.

tekx – opening keynote (lost art of simplicity)

Josh Holmes is giving the keynote and is very insistent on enthusiasm. Talking about simple projects and used twitter as…

Josh Holmes is giving the keynote and is very insistent on enthusiasm. Talking about simple projects and used twitter as an example. Twitter may have been been written in a weekend by most of us, it is successful because it filled a niche. Seems like part of the talk will be analyzing why we say “I could of wrote that in a weekend” with an air of disdain.

Looking at the definition of simplicity. First few definitions talk about foolishness and naiveté but the last definition is where we focus on “clarity of expression” and “Austerity in embellishment.”

tekx – best practices

tekx stream of though on best practices tutorial.

Visualization of the "history tree" ...
Image via Wikipedia

Starting off the best practices with source control @lornajane asked who is using source control and how much of that is using distributed source control. I’m 2/2 so far. woot. For those who aren’t familiar with source control, it creates a history and is a great collaboration tool.

Using source control is being discussed. You create a repository, add your project, check out your project, make changes. You can update to get changes from others then you commit it all back to the repository.

We’re looking at an svn log and will be discussing distributed vs non-distributed systems. Demonstrating a sample diff.

Source control Tool

* Subversion (svn)

* Git (git)

* Bazaar (bzr)

* Mecurial (hg)

Difference ways to interact with source control. Lorna gives a shout out for all the command line user people and is now mentioning IDE plugins, Trac, Tortoise[SVN|Git|Bzr|Hg]. I need to see if there’s a tortoiseBzr for OSX. I’m thinking of moving to Git since that gives my team more GUI tools, love Bzr but haven’t found many tools. Done with that sidebar. On to Centralized Source Control.

tek – bad guy for a day

stream of thought on the #tekx “bad guy for a day” tutorial. writing may resemble note-taking…because it is.

fuck per programming language chart
Image by gpuliatti via Flickr

K, trying a bit of live(ish) blogging. This will be interesting since this will be stream of thought on the tutorial as it goes on.

Todays tutorial is given by Arne Blankerts.

We’re starting off with an over view of websecurity and what we’ll be doing today. Looks like I missed questions, good thing I didn’t have any.

We’ll be getting source to look at, makes me wish I wasn’t lazy and had set up an environment.

Starting off with types of security. Transport layer,infrastructure, data warehouse,interface design, user level and application level…those sort of things.

Remember to secure your infrastructure. Anecdote about a setup with default root of database was given. Keep in mind how you train users. Example error alerts training people to accept errors as ok and to click through.