Skip to main content

CraftConf 2016 Review

Last week I have attended Craft Conference for the first time and I've decided to share my experience.

My favourite presentations:

  • Dan North - "Embracing uncertainty"
  • Jez Humble - "You Can Have It All: Software Development at Ludicrous Speed"

Some other worth mentioning:

  • Adrian Cockcroft - "The Evolution of Microservices"
  • Marty Cagan - "Great Product Team, Successful Product"
  • Doc Norton - "The Technical Debt Trap"
  • Yao Yue - "Toward Better Design and Code"

Most important takeaway:

Most important lesson for me was to be reminded about happiness and job satisfaction. The best way to make sure that something will be done is to let people have fun doing it. For example: if a developer can use this new language or framework she is enthusiastic about it's more likely she will do it just because it will be fun for her. No one likes to do chores, and getting money for that is not going to help much.

Other interesting themes/ideas:

Microservices - they are everywhere, and there are lots of tools that I haven't even heard about. A lot of innovation happens in this area but on the other hand, most companies don't need microservices and they actually might introduce more problems than benefits.

Pair Programming - it was inspiring to see about 90% of the attendees to raise their hands when asked if they program in pairs.

Relay/Falcor/ - I was sceptical but it might make sense to speed up development if everyone is a full-stack developer and maybe if different clients have really different needs - so that one REST API would be really inefficient. I still think most companies can do just fine without them.

Full Spectrum Developers - the main idea is that developer should know something about everything in the business. Some UX, finance, design, operations, management, estimation etc. At the end of the presentation with this idea, there was this really good question: how do you convince business people to be "Full Spectrum"? It was a brilliant question, but it showed up to late so it's something I think about after the conference.

Quality - a lot of talks were about the quality of what we do. Most speakers were convincing us that we should always create hight quality code (some even presented proofs). Yao Yue even told us to refactor while doing business features and just add this artificial time to the features. Some may disagree but in my opinion she's right. Most of the time business don't really know what it means, and what are the consequences of cutting corners. Most professions have government imposed acceptance criteria with inspectors and tests - if we want IT to stay how it is we should make sure to create quality code and be moral in the code we write. I recommend reading: Being A Developer After 40 by Adrian Kosmaczewski.

Thanks to Mateusz Kwaśniewski for reading drafts of this post and letting me know about Craft Conf this year.


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.