I’ve been a SOLID1 fan of TDD over many years and have spent a lot of time drilling myself in writing tests first to drive applications forward. I truly believe I have been at a place where my BIT has been FLIPPED. There are occasions though when attempting to write tests first have just been hard and completing a feature with test-first has been a record in will power and what felt like an eternity to deliver a feature. But if it was easy then everyone would be doing it.
Let me introduce you to Skybert (pronounced Sheeburt, for those of that haven’t grown up in Norway). He’s my imaginary developer-friend currently working at Mega Enterprise Inc Ltd Corp. He’s been butting heads with the lead developer, Jack, for a while now. They don’t seem to be seeing eye to eye on a feature that Skybert implemented. You see, Jack doesn’t like how Skybert writes his code. Formatting is wrong and he uses way too long variable names, and he doesn’t write a single comment and…(list goes on)! Jack hates reviewing Skyberts code. Skybert usually gets his code back from Jack, with a long list of TODOs. So Skybert goes off to re-do most of his work just to give it back to Jack…When Jack’s finally happy with the code; It adheres to his preferred coding style and uses the correct enterprise patterns that have been decided upon. He allows it through the magic gates to master. Continue reading
We’ve been joking a long time about the rate new technologies arise and how we as software developers need to keep abreast of the new so we don’t get completely outdated and irrelevant. With web development though, we’ve set a new standard. Continue reading
Recently I had the discussion with a colleague on how new code was being added to a code-base without maintainability in mind. The discussion was sparked by a code-review that had been ping-ponging between the reviewer and the developer where readability and ( as a result ) maintainability was an issue. Continue reading
I originally posted this on the dolittle blog.
There’s a new task waiting for you in your inbox… a bug in production! Maybe the bug is completely unrelated to code, you’ve created, but the report is there waiting for you. It’s critical, and has to be fixed “today” or “ASAP”! And with a number of consequences, like “this feature is vital!”, “support center is being called down by angry customers”, “we’re losing millions!”.
Norwegian Developers Conference (NDC) is a the largest conference in Norway targeting the .NET community. It’s a 3 day conference with 2 days of workshops beforehand. The speaker line-up was also awesome, and the topics offer something for everyone.
I’ve had the opportunity of attending the conference and have had 3 intense days of learning, networking and eating… yea, lots of food.
This has been the first time I’ve attended a large conference of this kind, and I didn’t really know what to expect. I hoped to be wow’d by speakers and technology. Mainly I hoped to gain some insight and inspiration…. I had no idea!
I had initially thought to summarize each talk I attended, but quickly threw away that idea. So this is a write-up of the impressions I’m left with after NDC 2012. Hope you enjoy it.
What an opening
He moved on to emphasize the importance of our roles as developers. We are all designers of software experiences. Emphasizing the emotional reaction people have consciously and sub-consciously to the using our software. He moved on to describe the process involved in product design, and that this has to come from the top-down. It has to be something ingrained throughout the company itself, and effects ALL business decisions. Design and experience is NOT about pushing pixels and changing a color theme on your home page, it’s about commitment to your customers and a shared vision.
Truly inspiring, if you’re open to it… watch it here.
Dan North had a really challenging session on how software architecture is based on trade-offs. There are no absolute best practices when designing software, but there is a need to make conscious decisions based on the real needs.
He debated certain topics with the audience, or rather, he debated with himself, and the bored norwegian audience just sat and hoped someone else answered 🙂
Even though what Dan said isn’t new, it put things into perspective. He made some good arguments around Test-driven vs Test-first vs Test after.
The big take-away here for me was the concept of product half-time. How implementing features without tests / tests after could add more value. This, however, requires the developers to have an extremely solid grasp of how to write software, and structure the code in decent way. It doesn’t give you the right to write crappy code.
Hadi had an awesome rant on what the software industry has become, and how developers put themselves on a pedestal above others. How we don’t know how to engage in customer communication, and expect people to understand our technical jargon.
At the end of the day, we don’t make software to have flame-wars on what technology to use, but to delivery good, working software to the end-user.
Also, I sat on the front row, and was addressed to as an Australian (something to do with whom I was sitting between).
Loved this session and recommend it to EVERYONE.
Billy Hollis had a couple of great talks on user experience. The first was about thinking outside the box. The time for features only is gone. Now the users expect features, but leveraged in an extremely easy to use way.
Billy took what Aral mentioned in his keynote and dove into theory and gave suggestions about how to take this back into the wild.
In his storyboarding talk, Billy emphasized the need to have lots of ideas or prototypes, and to not become attached to them. He showed some techniques and alternatives, and strongly suggested using paper / pencils for your creativity sessions. This reminded me so much about John Cleese’s talk about creativity.
He also made me promise to try storyboarding at home… I’ll save that for another blog post 🙂
To me, this conference has confirmed a lot of things I’ve been thinking and doing. It’s reinforced the fact that we, as developers, have to think about the user, even when “the business” gives us a defined user story / layout. It’s our job to say ‘no’, when people force us to remake the same old crap.
I’m inspired, I’m eager and I’m ready to focus on what’s important.
There’s gonna be frontend focus this meeting. I’ll be warming up the crowd with a session on “Forseti Driven Development”, and the main show is gonna be Marius Gundersen presenting “Building a 3D engine in Html5”.
More info on the talks, and the speakers on the meetup page.
Looking forward to it 🙂
Spread the word!
Yesterday, Einar Ingebrigtsen and I had a co-talk at NNUG Vestfold, titled: “Sugarcoating your front-end, one ViewModel at a time“.
It’s really a jungle out there, and there’s no lack of frameworks and solutions. There is one thing for sure though, and this is valid for all frameworks, they all focus on enabling Single Page Applications, and users are starting to expect that exact functionality.
Checkout the slides on slideshare. Please don’t hesitate to drop off a comment 🙂
Announcing NNUG Vestfold’s first meetup of 2012.
I’m pleased to get started with the first NNUG Vestfold session this year. Last year didn’t really turn out the way I expected, with a total of 1 meeting!
In an ongoing effort to push my comfort zone, I’ve decided to hold a session for this meeting.
After talking to a colleague of mine, my small talk suddenly became a 2-man-show!
Without further ado, I’d like to welcome you to my first talk: “Sugarcoating your frontend one ViewModel at a time” a co-session with Einar Ingebrigtsen.
In this past year at work, we’ve been in the process of developing a new platform from the bottom up with new functionality. One of the goals was to move away from an old unmaintainable solution to a new maintainable solution based on expected coding standards, and of course to meet the business’ needs about scalability and rapid feature development. With an overloaded domain, responsibilities were mingling with each other and business rules and validation was all over the place. Based on our needs, we felt it was that CQRS was the way to go. CQRS has been the talk in the DDD community for a while, and this pattern was something we could really relate to. In comes Bifrost!
Originally a helper-project for Einar Ingebrigtsen, we decided to leverage and contribute to Bifrost as an open sourced platform for web-app development. At it’s very heart Bifrost adheres to CQRS and is taking it “to the next level” by delivering a platform to deliver rich web applications.
Because of the way Bifrost as a platform was conceived, it has evolved in parallel with the product we are building. As project needs arise, amendments are made in Bifrost. This enables steady, controlled development on Bifrost without introducing features (too far) ahead of time. Though this is a good way of driving the project forward, it isn’t building out all the aspects of Bifrost. On the plus side, the platform is well-tested, thought through, and works well (with some known limitations and needed improvements).
On the web aspect of things Bifrost supports ASP.NET MVC and works well with the framework. Validation and binding of commands is something that just works, and I’m sure it’s something that people will appreciate. The next natural step is to actually not depend on MVC, and build out the client-side aspect of the platform. For this Knockoutjs comes in handy.
Bifrost has its implementation of CQRS quite well done already, and with it you can go in and whip up a great app with what’s there now, but you’re going to get little, to no help in regards to client-side features. There’s a clear focus on developing for the client-side aspect of things as well, which will enable Bifrost as an application platform. It’s a great convention-based platform that can solve many business needs, and its future looks bright 🙂
I hope to write more about the different aspects of Bifrost in the coming weeks. Until then, here’s some further reading: