Gearóid Crowley is a Lead Consultant at Readify.
He's from Ireland, based in Sydney these days, and passionate about helping organisation build quality products with the power of automated release management.
Today I gave Gearóid a call to talk to him about his first line of code, his many years in the industry and what he enjoys most about working at Readify.
- My first Amstrad. 1992. Ireland.
- First line of code.
- Building a chess game in assembly.
- Solving a problem is often about how it's setup.
- First job in tech.
- How did Readify appear on your radar?
- Life and thinking of the team at Readify.
- Changing landscape of cloud computing and the resulting rise of Devops, discipline and quality.
- Busy Queues. Idle Queues.
- Books. The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr. Personal Kanban by Jim Benson.
- Xmas cooking kanban board.
Luke Drumm is a Senior Consultant at Readify.
He's based in Sydney, an author, a speaker, a coder, and he's passionate about building awesome software.
Today I gave Luke a call to talk to him about his first line of code, his many years in the industry and what he enjoys most about working at Readify.
- Was there a specific moment when you realised you can use magic to make computers to do crazy things?
- First computer. First line of code. 1985.
- Learning tech at a tiny little international boarding school.
- First job. Selling computer Hardware.
- Working at Fujitsu. Making the transition to Development.
- First year at Readify, aka Monash.Net.
- Teaching is a great way to learn.
- 13 years at Readify is a pretty long slog. What has kept you here for so long?
- What sorts of connections do you see between Art and Technology?
- What's behind your approach to public speaking and presentations?
- Books, magazines, and saving games onto cassette tapes.
Mitch Denny is Readify's Chief Technology Officer.
He's based in Melbourne and passionate about cloud computing, mobility, devops, 3D printing, IOT and solving real world business problems.
Today I gave Mitch a call to talk to him his first line of code, what he's been up to this past week and what he enjoys most about working at Readify.
- Growing up in the country, local computer stores and first line of code.
- Our origins as Monash.Net and helping organisation get technically "ready".
- Starting out at Readify as a Consultant.
- Winning the presenters award at TechEd.
- Starting one of the world's first .net user groups in Melbourne.
- Dev pod.
- Three different ways Readify operates.
Parma Juss is the National Telstra Sales Manager at Readify.
He's 46, based in Sydney and passionate about helping businesses capitalise on the potential of technology.
Parma is the sort of guy who walks into world class organisation, makes friends, cuts deals and brings a kickass team of technical specialists to a real world business problem.
Today I gave Parma a call to find out more about how he found his feet in the technology industry, what he's been up to this past week and what he enjoys most about working at Readify.
- 10 one liners about you.
- Parma's origins.
- How the brand has changed.
- What clients are looking for.
- Open culture.
- Being part of the team.
- The next generation of cloud solution development.
- Product and service diversity.
Tatham Oddie is the Head of Software Development at Readify.
He's 28, based in Melbourne and passionate about solving complex business problems using technology.
Today I gave Tatham a call to talk to him about his pathway into his work, what he's been up to this past week, some of the changes he's seen over the years and what he enjoys most about working at Readify.
- 10 one liners.
- Pathway through school into technology.
- This week.
- SIO and Software Development Management.
- Readify roles.
- The formation of our mission and culture.
- The hive mind and reaching out for help.
- Public speaking tips, events, user groups, presenting, community participation and other fun adventures.
Music: Podington Bear
Thanks for tuning in. My name is Kahne Raja. This is episode 2 of Getting to know our consultants.
Ryan Hayward is a Senior Developer at Readify.
He's 25, based in Brisbane and passionate about building awesome products using .net, ios and web technologies.
Music: Scott Gratton
Jake Ginnivan is a Senior Consultant at Readify.
He's an open source enthusiast, blogger, speaker, microsoft MVP and a fan of good beer.
He is a contributor to a number of open source projects including AutoMapper, Shouldly, NSubstitute, XBehave, DbUp and Funnelweb.
The best way to get in touch with Jake is to flick him a tweet.
Today I gave him a call to talk about his latest efforts on a project called GitVersion.
GitVersion is an Easy Semantic Versioning solution for projects using Git. We started the conversation by taking a quick look at what Semantic Version.
Jake is taking the lead on the next release of GitVersion. To give you some background. GitVersion has been on GitHub since August 2013. Since then it's had 22 releases with 54 contributors and it's used by the team NServiceBus and Octopus Deploy.
I got to using GitVersion on a project this week and I found it interesting to see how many different ways it can be used for different solutions.
GitVersion works on many levels. It can assess your commit messages, tags and branches. It gathers up all that data and creates a useful version number. Depending on your configuration it will then include that version number in your solution.
GitVersion is useful for whatever pipeline you've got going on. Whether it be Team City, Visual Studio Team Services, Chef, Puppet, Octopus Deploy. It's going to work because at the end of the day it can be encapsulated into a single simple to use command line tool that can be plugged in whereever you like.
GitVersion is a tool that will help your project remain semver compliant. Thinking about what this means and how this sort of standardisation can help your project continue to evolve whilst others depend upon it got me thinking...
Spending some time exploring semver has got me thinking about transitive dependencies and how this sort of idea is often at the core of backlog management, grooming and prioritisation. Perhaps semver could be a useful tool early in the scrum cadence. Perhaps the idea of semver could be useful for versioning many things, not just released packages of code.