About a year old – http://peridot-php.github.io/ – Clean and refreshing. Assertions library at http://peridot-php.github.io/leo/expect.html .
Installed it with:
composer global require peridot-php/peridot:~1.15
composer global require peridot-php/leo:~1.0
And had to add it to the PATH ( $HOME/.composer/vendor/bin ).
I’m pretty excited to let you know I’ve finally started working on my next presentation ( after taking a break for about 8 months from meetups and presentations ).
It will be about agile fluency, and all I’ve gotta show for it so far is a ( hi-res ) photo of my whiteboard wall with some thoughts.
- Got in touch with Chris Brower, the Program Co-ordinator for Digital Media Design and 3D Computer Graphics at the Red River College. It seems that the best fit for my further education would be a selection of courses from the digital media design, graphic design, and creative communications programmes, though I still really don’t haven’t looked into it enough to know whether that makes any sense, so I will take a close look at those programmes to understand it all better.
- Wrote this and previous blog post
- Followed up with a new technical writer acquaintance I made on Wednesday at the WordPress meetup.
- Got an appointment with Mario Tomberli, a local software developer recruiter, who reached out to me after I tweeted about being laid off
- Set up job alerts at the Job Bank website. Used location Winnipeg, no job title, and keywords: web software app mobile developer programming programmer
- Signed up for an orientation session with the YMCA Business Training Centre, for joining their Self Employment Program
- Signed up for an orientation session for the E.A.R.S. programme offered by the Winnipeg Transition Centre
- Signed up for an orientation session with Opportunities for Employment
I still plan to try to set up my computer further for work on WordPress websites, an initiative I’m hoping will provide lucrative self-employment opportunities, and perhaps even a product with passive income opportunities.
I’ve set up a version-controlled repository for the code retreat.
This time around I have branches with the boilerplate/scaffolding code for several testing frameworks including:
* DocTest for Python
* PHPUnit & SimpleTest for PHP
Just a new face I got. Jus’ sayin’
Got my new glasses from http://goggles4u.com. The lenses are so clean that the world looks new and shiny! I need a haircut/makeover. 🙂
<?php echo “Remember me next time”; ?>
I consider the progress I’ve made from “That is unacceptable” to “I need to be more accepting of that” one of my greatest gains in 2013.
IRCMaxell, a fellow PHP developer and Freenode user, wrote an article on his blog, entitled Beyond Clean Code.
For me, the good point in this article is about re-thinking how much investment to make into trying to make better code, which I think is very important for a software developer to learn, so that they are able to create the highest ROI possible for their employer. No question this is an important lesson that we all need to be reminded of often. As often as every week, really.
I’ve had the opportunity to talk to IRCMaxell on ##php on Freenode IRC before. I think that he is a cool guy, with interesting depth of experience and laudable focuses on security and writing code that delivers business value. Here’re some corrections I would make to the article:
- Dirty and Clean code are not absolutes. In my experience, some code can produce low business value specifically because it is poorly written, even if it addresses a problem that would have otherwise brought good business value. Of course, any code that manages to avoid failing to deliver the business value because of how badly it is written, is by definition good enough. At the same time, perhaps there is opportunity to maximize ROI by investing into teaching the developers how to produce better code in the future, through minimizing technical debt.
- He understands and defines TDD as “understand the code you’re trying to write before you write it”, which is not actually TDD from what I understand based on the clarifications in places like TDD as if you meant it . In that article Keith Braithwaite calls the approach IRCMaxell describes as “Pseudo-TDD”. It seems to me that DIRTI is basically TDD, except with unit tests after the code. I would venture a guess at the choice for doing it after the code because he does not really get unit testing. I am also not very good at unit testing, and it seems extremely hard to get good at, and there is a lot of misguiding material out there, and not a lot of good material.
- He calls TDD and Pair Programming “Methodologies”. They simply are not methodologies, because they are tools, or rather practices. An example of a “Methodology” that incorporates ( and birthed ) those two practices is eXtreme Programming.