sale softwareSoftware Craftsmanship Conference

on August 1st, 2018 by admin - Comments Off

Later on when I read clean coder it really hit home that being a good developer is not just about the code you write, but how you react to interactions and having a bar for your professional behaviour. This is the side of Software Craftsmanship I really enjoy, the psychology and professional best practices.

We have long been interested in creating correct software by a systematic process, rather than by haphazard programming and later debugging and bug fixing. This is an obvious craftsmanship issue, but goes beyond the usual craftsmanship techniques. The technologies for creating software that is proven correct have existed for many years, but their poor usability put them out of reach for many developers. This is changing Thats what the talk is about.

Founder/Director of RK Research Conveyance, an experienced consultant and the author of Working Effectively with Legacy Code.

Coaching How does a Technical Agile Coach improve work in a development team? For years Ive helped set up Coding Dojos as a space for teams to learn the theory and practice of TDD. All too often the initiative fizzles out and the dojos stop happening when Im no longer there. Without technical practices like TDD and Rectoring, agile adoptions can also fizzle out. The latest research into DevOps shows that organisational culture, team collaboration and learning is really important for success. Recently I have been using Mob Programming as a way to improve team culture and spread healthy technical agile practices in a teams production codebase. Ive found that this in combination with shorter dojolike daily learning sessions is really effective at changing behaviour. In this talk Id like to share my experiences of what Ive found to work in real teams.

Regarding meetings, members, subjects being discussed, and community aspect, I have mixed feelings. At the beginning we were a much smaller group deeply interested in Software Craftsmanship, Extreme Programming and Software Design. We had a lot of things in common and learned tons from each other. As Software Craftsmanship became more popular, more people joined the community but not because they really wanted to get deeper in Software Craftsmanship but mostly because it is one of the many new things out there. That had an impact on the meetings and subjects being discussed. On one hand, LS continues to help many developers to learn the foundations of software development and instigate that desire to do things well. And that is awesome. On the other hand, that aspect of a small community where everyone knows each other and that feeling that we are always looking forward to see each other again to continue the conversation doesnt exist anymore. But yes, it is still a vibrant community and it is always a pleasure to attend the meetings whenever I can.

A design study is a of deliberate practice focused on improving design skills. Through a deliberate exploration of the solution space, design studies result in multiple solutions for the same problem. This allows designers to understand tradeoffs and compare solutions in a very deliberate manner. In this talk I will walk you through the idea of design studies, how we can apply them to software design, and provide enough examples to get you started. We will also discuss about applying the concept in a learning environment.

Mostly on Twitter sandromancuso and theCodurance blog.

Renown speaker, writer, trainer, and consultant on dev patterns, programming, practice and process.

So r the focus of the Software Craftsmanship movement, mainly inside the communities, has been on technical practices. The work the communities around the world have been doing on teaching, learning and practicing XP practices like TDD, Pair Programming, Continuous Integration, alongside Clean Code, Rectoring, DevOps, Functional Programming, software design, and a few other things must continue. As more experienced craftsmen start mastering these practices, they should start looking forward and try new things. Good practices are only good until we find better ones to replace them and that is the Software Craftsmanship mindset. We need to detach Software Craftsmanship from specific technical practices. Our job is to always look for better ways of doing things, discover new practices, and share them with the rest of the community. This way we can guarantee our industry will evolve on solid grounds.

Developers should be getting more involved in how businesses operate and applying craftsmanship to the bigger picture. Craftsmanship will have its part in digital transformations. Digital Transformation is basically transforming the organisation around software delivery, as software is the main medium for communication with the customer. That in turn sets a focus on software and craftsmanship. As we see more and more transformation like Spotify we will see more emphasise on craftsmanship within organisations.

The world of software development has changed so much and in so many ways since that its difficult to imagine what we could learn from then, but its learning rather than imagination thats the constraint. There was no shortage of imagination, insight and inspiration in the s and s, and in many ways the apple of stcentury software development has llen disappointingly close to the tree of the past.

CoFounder of Codurance, author of The Software Craftsman, and founder of the London Software Craftsmanship Community.

Software Craftsmanship means you have the capabilities to talk to nontechnical people, to translate what they want into working software and to translate back improvements or reasons why things may need to change from the coding or framework level. Software Craftsmanship means good communication at all levels; all developers being able to understand the code and all team members being able to understand the developers.

Involved in Agile Software Development since . Strong believer in transparency, openness and decentralised decision .

So sit back, relax and take a sneak peek. Oh, and if you like this and want more then you should also check outsclondon, where you can immerse yourself in twodays of talks; discussions and networking with the authors of the blogs…

I might have answered a little already. If we relate back to the manifesto, I see craftsmanship as, not only iniduals and interactions, but also a community of professionals and not only customer collaboration, but also productive partnerships. For me, this means showing others in your team, or showing the client that developers/engineers are not just their to code heads down. We shouldnt just leave the business of why the product potentially wasnt what the company wanted to others.

If a participant engages in harassing behavior, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.

The panel is going to discuss the importance of Software Craftsmanship and technical practices. What are the technical practices development teams should adopt? Why should they adopt? What is the business value they bring? How to create a culture of learning that is embraced by developers and business?

For a few decades, one of the most common approaches to software design is to first focus on the domain model application layer, then persistence data layer and finally the user intece presentation layer. But what are the pros and cons of this approach? Are there other alternatives? Are they viable? In this presentation, Sandro will be talking about different design biases and the impact they have. He will then focus on OutsideIn Design, explaining how our domain model can emerge and evolve when driven by the needs of external systems or users, avoiding speculation and wasted effort.

Take advantage of our Early Bird ticket before th June and secure your place at SC London

When were having an architecture discussion, well talk about abstractions, using terms likecomponent,moduleandlayer. These abstractions reflect our mental model of a software system, which are useful when describing our architectural ideas and intent. These same abstractions dont typically exist in the programming languages we use though. Theres nolayerkeyword in Java, for example. To implement these abstractions, we need to use a combination of the constructs available in our programming languages; such as classes, inteces, objects, functions, packages, namespaces, files and folders. In many cases, the code that is written doesnt end up reflecting the model. This is themodelcode gap. The modelcode gap manifests itself in a number of ways. In obvious cases, the code doesnt match the architecture diagrams. Sometimes the problems are more subtle though. This session is about the modelcode gap, and particularly how it relates to applications that are built from a single monolithic deployment unit. Regardless of how we choose to structure our code layers, vertical slices, ports and adapters, etc, our best design intentions can be destroyed in a flash if we dont consider the intricacies of the implementation strategy. The devil is in the implementation details.

Yes immersion, conversation, presentation giving and receiving, reading and writing. In other words, the traditional other ways of refining and exploring skills and knowledge.

International speaker. Experienced Trainer, Software Developer. Author of The Coding Dojo Handbook and Pluralsight courses.

Tickets include refreshments at designated times, a light lunch, access to the evening reception plus access to all conference sessions. Accommodation and travel is NOT included in the ticket price.

Technical Demo BlogSharing Talkingblundell_appsThoughts Insights Blog

Please note that once booked, Conference tickets cannot be cancelled and are non refundable. However, a substitute may be enrolled in a delegates place provided we are notified in writing before the first day of the event. Also note it is one ticket per delegate ie no sharing. While Software Craftsmanship London strives to maintain an up to date schedule, session list, and speaker list, these may be subject to change. If Software Craftsmanship London has to cancel the conference for any reason, then we will refund of any prepaid conference ticket fee, but we will not be liable for any other costs incurred including for example travel charges or any consequential damages, even if we were advised of them.

The Craftsmanship mindset wont survive in a hostile environment. The adoption of a Software Craftsmanship mindset is much easier when a company already has some sort of Agile culture people working collaboratively, short feedback loop, inspect and adapt attitude. Without this foundation, it will be hard to change the culture and introduce new ways of working.

DomainDriven Design, patterns, BDD TDD enthusiast. CTO Arollafr Founder of the Paris Software Craftsmanship Community.

The future is hard to predict and maybe Im rambling a bit, but I see the future of Software Craftsmanship in embracing more pragmatism and people starting to talk about outside influences and quantifying value gained from each practice.

I first came across Software Craftsmanship when I was working as a graduate software engineer in the web space, this was before I moved to mobile. A colleague had a copy of the just published clean code by Robert C Martin. I was struck by the perscriptive nature of an answer to every scenario, and it intrigued me to seek out these scenarios and apply the practices to learn and improve.

Pragmatic in your approach to software development?

So sit back, relax and take a sneak peek. Oh, and if you like this and want more then you should also check outsclondon, where you can immerse yourself in twodays of talks; discussions and networking with the authors of the blogs…

Given the complexity of modern processor architectures, for the application programmer to understand what goes on at the lower levels has been hopeless for a while now. Witness the troubles resulting from undefined behavior in C, which are a result of this development. So its not a function of the tools getting smarter, its a result of growing complexity overall.

We expect participants to follow these rules at conference and workshop venues and conferencerelated social events.

SC London will bring together over software professionals, passionate about continuous learning and improving their ntact usto find out how you can help support engage with our amazing community.

Q. Google and Apple recently added support for testing in IDEs. How do you see these ecosystems developing for XP practices and what more could they do?

Want your company to adopt the Craftsmanship mindset?

From the organisational point of view, as the group grew, we had different challenges. At the beginning our meetings were small and we had them once a month at a place I used to work. They were easy to organise. As we grew, we had to decide to either make our meetings bigger or have more meetings. We decided for the latter. More meeting also brought an overhead of organisation. Although many people helped over the years, we recently decided to bring the whole organisation of LS to Codurance. This made things a bit easier as we can have dedicated people to make sure the meetings are scheduled and organised.

The other side of the future is how inclusive is the word craftsmanship and should the whole idea be reinvented/reworded to allow for ersity and difference.

To me Software Craftsmanship is our innate desire as humans, to do a job well for its own sake. It is the goal of creating software that provides value for its users and the business allowing us to support the business in a reliable and timely manner. Like any other craft we value the skills and practices needed to create great software. Last but not least, it is about a culture of teaching and learning.

Consultant with Zuhlke Engineering, agile development pioneer, and coauthor of Growing Object­Oriented Software Guided by Tests.

Client acceptance for Software Craftsmanship, we always found clients not convinced by our methods but soon they see the value in the results, including the speed of delivery and lack of bugs and regressions. Its hard to quantify software craftsmanship, clean code and best practices to a business and most the literature out there is aimed at convincing developers. So turning software craftsmanship values into explainable value for the business was the biggest challenge.

Back then I was an active member of the London Java Community LJC. Although I learned a lot there, I wanted to create an environment where developers with different s Ruby, C, mobile developers, etc. could come along and discuss how they build software. I was not interested in language specific stuff. I was interested in the fundamentals of software development practices, design, architecture, programming paradigms, automation, any thing that every developer need to learn regardless which programming language they use. I got to learn a few things about Software Craftsmanship from some people in Chicago and UK and I loved it. I could totally relate to it. So the need to learn more and the immediate connection to the Software Craftsmanship principles led me to speak to a very good friend of mine called David Green and together, with the support of our friends from LJC, we started LS in August .

I help run the Liverpool Google Developer Group. I have a dream of a big tech city in the UK outside of London and you can contribute a small step towards this. We are always looking for monthly meetup speakers, you can get in touch at gdg and see more here

The substance and focus will remain and evolve, but I suspect that it may find itself going by another name or becoming allied or integrated into other bodies of practice.

CoFounder of Codurance, a pragmatic software craftsman, and founding member of London Software Craftsmanship Community.

Developer Advocate for JetBrains, Java Champion, expert in high performance systems, and leader of Sevilla Java User Group.

This an on going struggle within every craftsman and not just the Software Craftsman. Understanding that the software is not the end goal but the value it provides helps us balance the perfect against the practicable. To quote Richard Sennet from The Craftsman, to the absolutist in every craftsman, each imperfection is a ilure; to the practitioner, obsession with perfection seems a prescription for ilure.

We caught up with Mashooq Badar, cofounder of Codurance and frequent blogger on a range of Craftsmanship topics, to get his opinion on Software Craftsmanship, and the balance between pursuing perfection and pragmatism.

We caught up with Sandro Mancuso, author of The Software Craftsman, founder of the London Software Craftsmanship Community and keynote speaker at SCLConf, to get his thoughts on Craftsmanship and growing supporting a community of nearly , members

Organised by Codurance All Rights Reserved  

These days its relatively easy to find accounts of what its like to adopt agile for the first time things to consider, suggestions of what might go wrong, and promises of what will be better. Less so for Extreme Programming XP, whose star has waned but perhaps may be waxing again. However, its much more difficult to find accounts of what its like to have applied agile practices, particularly XP, for protracted periods in growing organisations. As usual, while there is enlightenment in the journey, nirvana is elusive. Steve will talk about XP as its practiced at Unruly, a video marketplace founded on XP principles more than a decade ago, and which continues to build on those principles across the organisation, but particularly in the software development teams. Pairing or mobbing is the norm, continous delivery and testdriven development are simply givens, and decision is distributed, combining both topdown and bottomup elements, but there are still plenty of challenges. Steve will be reflecting on how Unruly compares to other organisations and teams that hes encountered in his years of software development, both agile and not, and the aspects of the process that are still evolving at Unruly. Hopefully youll be inspired to change, regardless of your starting point, and you may also learn a few things youd like to avoid in your journey. Steves XP journey officially began when he was asked to be a reviewer of the first edition ofExtreme Programming Explainedin . After many years of encouraging teams to be more agile with varying degrees of success, the journey has taken him to Unruly, where he has been CTO since September . Steve was also a cofounder of Cogent, an Australian company founded on the principles of transparency, collaboration and software craftsmanship values. In between, hes worked in investment banking, a Silicon Valley startup, and a variety of small companies and consulting commitments.

Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

I see them being used as warmups, as a social activity, as a way to kick the tires of new tools, languages and practices. At the most common introductory level they seem to be, unsurprisingly, about learning TDD and pairing. This remains true at other experience levels, but with other levels people seem more likely to use katas as vehicles for other ends, such as experimentation.

Novoda is a real believer in open source, we have many OSS repositories including helper libraries and demos. You can check them out here pull requests are always welcome.

That theres more to katas than just deliberate practice. Katas and small wellframed problems offer an opportunity to experiment, to deepen knowledge, to get creative and think laterally, to find simplicity, elegance and aha! moments in something miliar or seemingly trivial. And fun.

Attendees, speakers, sponsors and volunteers at our conference are required to agree with the following code of conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to help ensure a safe environment for everybody.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. Conference staff can be identified as theyll be wearing branded clothing and/or badges.

Polyglot programmer, and experienced trainer and coach at Mozaic Works. Frequently cilitates coding events accross Europe.

I feel many developers stay at stage conscious competence and rigorously apply what they deem as craftsmanship without thought for what else is going on on the team or around them. When you get to stage four unconscious competence you have the freedom to consider other things and understand that perhaps…because of other ctors some pragmatism is needed in your practices. This allows for deadlines, demos, unforeseen outside influence and shipping dates.

It definitely got bigger. LS went through quite a few changes of the years.

I would like us to start focusing on Software Craftsmanship as a mindset where we value good practices, skills, and technologies but also understand that these are a means to an end for creating software that is timely, flexible, and valuable to the business. I would like to see us steadily raise the bar of professionalism within our industry.

There are many and different places have different problems. A common one is the its not my job attitude. This can be found in all levels of an organisation including among developers. Another one is the traditional topdown commandandcontrol management . In an environment like that, Software Craftsmanship wont flourish. A small bubble pocket may be created in a team or department but the rest of the organisation after sometime normally crushes it when one or two people leave the company or move to another area. The inflexibility, arrogance, and religious attitude of some craftsmen when it comes to certain practices can also put people off.

We are programmers who aspire to be worthy of the title ofCraftsman. So whatisa software craftsman? What promises do software craftsmen make to their fellow craftsmen, their employers, and society at large? In this talk, Uncle Bob presents, for your consideration, an oath for all who desire to serve society through the design and implementation of computer programs.

Were busy gathering anamazing lineup of speakersincluding vourites from SCLConf . From your valuable feedback we were pleased to see the quality of the talks was judged to be extremely high even better than we had hoped for! Launching the Software Craftsmanship Conference in was an experiment. Looking back, we are very proud with the response and to see the interest that exists for the craftsmanship mindset.

Our conference is dedicated to providing a harassmentfree conference experience for everyone, regardless of gender, gender identity and expression, age, ual orientation, disability, physical appearance, body , race, ethnicity, religion or lack thereof, or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and ry is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.

At some point soon I plan to start collecting contributions for Things Every Java Programmer Should Know. Like Things Every Programmer Should Know before it, I will be looking for short contributions on anything from the mechanics of the code to the people and practices that surround it.

Passionate about Clean Code Extreme Programming?

In this series of minute QAs we give you an insight to some of the worlds leading thinkers and doers in the world of Agile and Software Craftsmanship. We asked SCLConfs speakers Nicole Rauch and Michael Sperber about Software Craftsmanship, whether smarter tools may lead to developers losing knowledge about lowerlevel abstractions and where they see the Software Craftsmanship movement going in the future. So sit back, relax and take a sneak peek. Oh, and if you like this and want more then you should also check outsclondon, where you can immerse yourself in days of talks, discussions and networking with the authors of the blogs…

Properties can be written as execule parts of a program, and verified with a little help from the programmer.

Besides technical practices, many companies are now realising they are or are becoming a technology company. They may sell clothes, they may handle financial transactions, they may book hotels, they may stream videos, but at their heart, they are a technology company. A technology company should not be managed and structured in a traditional way. The Software Craftsmanship movement, that means, craftsmen around the world, must become more connected to the business world and understand that from a business perspective, our technical practices are a means to an end and not a goal. Craftsmen need to step up and start truly collaborating with the business, providing ideas, alternatives, and solutions. But for that to happen, we also need to learn new skills. The same way we put a lot of energy to master technical practices, we should also start learning how a business is run, how companies make money, and how we can help them to be more successful. Being empowered is great but empowerment sucks if we dont have the necessary skills and no one benefits from it.

Nicole I first came across Pete McBreens classic Software Craftsmanship and immediately I liked the idea so much that I even cocreated a whole conference and subsequently a user group around this topic. The conference is SoCraTes Germany Software Craftsmanship and Testing which has given rise to similar events all over Europe in the last couple of years, and the user group is Softwerkskammer, with currently members and regional chapters across Germany, Austria and Switzerland.

Industry leading experts, thought leaders and software craftspeople who shape and drive forward the craftsmanship community.

Sponsors are also subject to the antiharassment policy. In particular, sponsors should not use ualised s, activities, or other material. Booth staff including volunteers should not use ualised clothing/uniforms/costumes, or otherwise create a ualised environment.

Software Craftsmanship _is_ the future It is already noticeable today that for many companies it has started to become a game changer, introducing a shift in the mindsets that allows to slowly get and keep the old and often crufty codebases under control. Combine it with likeminded methods like Specification by Example and DomainDriven Design, add welleslished development strategies like stronglyd functional programming, and you get a powerful toolbox for clean and maintainable code.

Although almost years old as a movement, Software Craftsmanship is yet on its inncy and still trying to bring to developers more awareness about professionalism and the importance of constantly hone our skills. The good news is that more and more developers and companies are trying to adopt the Software Craftsmanship mindset in their organisations and it feels we are going in the right direction.

I love working with legacy code! Its great fun to e into a system that we didnt write and figure out how to improve it. Last year, I jumped at the opportunity to work with a startup on a Ruby on Rails code base where developers had left and business users needed support. As I ed down into the code, there were a few surprises lying below the suce but my experience was not a miserable one. I enjoyed the challenge of an incredible learning experience. Ill be sharing my key insights from this project in my presentation at SC London. Come along to this talk to hear some practical strategies for getting to grips with an ageing code base while setting realistic expectations about whats possible.

Developers, in general, should consider functional programming as a means of reducing complexity in their code, and good craftsmanship vastly easier So the projects people should be aware of are the programming languages that let them do that, such as Haskell, OCaml, F, Racket, Erlang, Scala, Clojure, Swift, and others.

Developers have a responsibility to share knowledge and enable others on their team to understand the why and how of their reasoning and this is what I enjoy improving for myself and enabling in others.

Author of the first Agile Coaching book and an invited speaker to software conferences worldwide.

Harassment includes offensive verbal comments related to gender, gender identity and expression, age, ual orientation, disability, physical appearance, body , race, ethnicity, religion, technology choices, ual s in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome ual attention.

I came across Software Craftsmanship around when Sandro Mancuso and David Green were considering starting the London Software Craftsmanship Community.

A community of knowledge and practice applied in the detail to benefit more than oneself.

Perhaps the future of Craftsmanship will be some backlash to this stage three perfectionism, every now and then I see people Mob programming and this is all about a whole team agreeing on ideas and setting out a rough framework of the code. Its not crafting but it should be a tool in a craftsmans toolbox.

That is a hard question. As Ive matured and gained experience my feelings towards craftsmanship have also changed. Its like the four stages of competence, you start off unconscious and incompetent, not crafting very well and not recognising you need craftsmanship. Conscious incompetent, you learn about craftsmanship but you il to apply it consistently. Conscious competence, you know what you are doing but you have to concentrate when applying it. Unconscious competence, craftsmanship is second nature, you apply it without thought whilst taking other things into account.

For me, Software Craftsmanship has different aspects. The first is the mindset, a more ideological way of to see our profession, the desire to do things well, and an eternal journey towards mastery. The second aspect is professionalism. The realisation that our first goal is to delight our clients, helping them to achieve whatever they want to achieve in the best way possible, eslishing a productive partnership instead of client/supplier or employer/employee. And the final one is career ownership. Craftsmen own their careers, investing their own time and money to improve their craft and also taking control of their own professional destiny.

Codurance has definitely become my biggest project. For . years Mash and I have been focusing all our energy on creating a company we love to belong. Its the first time we are running a business and we are having to learn a whole new set of skills to do our jobs. It can be quite scary sometimes. And as we were getting comforle, we decided to open an office in another country, which brought a completely new set of challenges.

Author of many influential books, coauthor of The Agile Manifesto and a founding member of Software Craftsmanship movement.

I heard about it in early , when the first Software Craftsmanship conference was announced. I could relate to the values straightaway and in I started the London Software Craftsmanship community, the first in Europe.

Author of Software Architecture for Developers, consultant, speaker and creator of the C software architecture model.

Thenimmerse yourselfin thisday conference, and get an insight into the mindsets of some of thegreatest thinkers and doersin the Software Craftsmanship world.Speakers

Subscribe here for updates on speakers, sessions, and special events.

Software Craftsmanship means to do the right thing and to do it right. Also, we think that it is important that everybody involved in a software project raises their awareness beyond their own horizon, keeping the big picture in mind and engaging wherever necessary. In Software Craftsmanship, there is no such thing as a coder who just codes, a tester who just tests etc. Everybody should be involved from the first meeting with the customer to the end of the maintenance cycle.

In this series of minute QAs we give you an insight to some of the worlds leading thinkers and doers in the world of Agile and Software Craftsmanship.

Programmer, trainer, coach and cofounder of Commited to improving his craft and helping others improve theirs.

I see the ecosystems developing slowly. There is always a big emphasis on acceptance/UI testing when it is enabled inside an IDE, but the real benefits of testing come from the unit tests and the lower levels which dont get so much of a n re. I think the next steps for IDEs especially in mobile is to make the loop of testing ster, ster build and execution cycles as well as more sle emulators gives people less excuses to avoid testing. Id love to see unit tests executed on every save for mobile IDEs like Android Studio or XCode.

The panel will discuss how modern software companies look like and how they should be structured. Flat structure? Decentralised decision? Empowerment? The panel will share their experience in how theyve been running their own companies and also how they are advising their clients.

of the birth of Software Craftsmanship movement!

London and major cities around the world have vibrant communities based on specific areas of software development, not to mention Software Craftsmanship communities. Our active involvement in these communities will help us all further software creation as a true craft.

In this series of minute QAs we give you an insight to some of the worlds leading thinkers and doers in the world of Agile and Software Craftsmanship.

Developers should think about their programs as having general properties as opposed to just functioning test cases with inidual examples, and make those properties explicit.

Things are settling down now, and I have plans to write one or two small books and hopefully start recording screencasts again.

That learning is a journey, you meet people on the way, share and grow together. Continuous learning is what keeps life exciting and your brain active.

This year is special. Our conference coincides with theth anniversary of Software Craftsmanship movement. In , a number of aspiring software craftspeople met in Libertyville, Illinois with the intent of eslishing a set of principles for Software Craftsmanship. We believe this is a wonderful opportunity to celebrate the moment that started the Software Craftsmanship movement.

Participants asked to stop any harassing behavior are expected to comply softwareSoftware Craftsmanship Conference