Breaking the rules of consulting
We do things that seem crazy from the perspective of traditional IT consultancies. We are not crazy, but just in case you think we are, let me explain why we do things differently.
Our key principles are:
Employees are pets, not cattle
Our customers want to change
We don’t chop wood, we sharpen axes
We don’t sell CV’s
We invest in ourselves
We invest in the community
There is a popular term in the DevOps world that we should treat our servers and environments like cattle rather than pets. The ideal infrastructure should be made of mass-produced units destined for destruction at our will, rather than individually hand-raised with care.
Unfortunately the attitude that employees are resources to be mined also prevails in the consulting world. We take a different view on this.
In Praqma, there are no bonuses for slaving away long hours on customer projects. We expect to see you in the office regularly, collaborate with your Praqma colleagues, and in general contribute to the Praqma culture.
We don’t commit our consultants to more that 80% on client work
We encourage work on internal projects
We develop graduate talent together with senior experienced consultants who’ve “seen-it-all”. Nobody should ever feel on their own in Praqma, even if we do throw our consultants in the deep-end.
Many of us have had frustrating working experiences in teams and organizations that simply cannot or will not change. In Praqma, things are different. Our customers are ambitious, want to improve, and are actively asking for us to help them.
We help organizations sharpen their axes, and we believe there is no better way to build a career.
This is a proverb we’re using internally in Praqma. What we mean by this is that we’re not just hired to make up the numbers - we are there to improve teams and organizations.
We work together with the customer’s own employees - we don’t replace them. Slowly and surely we teach them everything we know through daily work routines and by turning everything into code so it becomes persisted, executable and maintainable.
Our customers don’t buy people from us, they buy services. Our quotes and contracts with our customers are very explicit about this. We have the motto “Buy a consultant, get a team”. What we mean by this is that to best serve our customers we need to be able to bring the full experience of our team to their problems.
Why do we do this?
The nature of what we do involves way more skills and experiences than any one person should rightly have. An expert at introducing Test Driven Development to teams would probably not also be an expert at setting up a HA Kubernetes cluster on bare metal. But it could be that a customer needs all those skills to succeed in improving its organization’s ability to deliver change.
By delivering a service rather than the CV we can:
Better serve our customers
Increase collaboration and knowledge sharing in Praqma
Increase collaboration and knowledge sharing with our customers
In general live more authentic lives.
How does this work in practice? In general each customer has a Senior Consultant to plan, organize, teach and direct the change process, together with one or more other consultants to help on the implementation.
Many of the technologies and skills we are delivering today did not exist two years ago. This means we need to spend a lot of time learning new technologies, sharing this learning both internally and through our events.
We frame our company culture in terms of knowledge and experience and we believe that teaching what we learn is the best showcase for our talent.
Training: alongside our diverse training catalog, we are actively developing new training material and sharing it with our customers. We even work together with many universities to help develop the next generation of experts in our CoDe Academy and other collaborations.
Events: we host several events every month, relatively small meet-ups all the way up to full blown conferences bringing together the thought leaders in our field.
Even from the very beginnings, Praqma has taken its role in the community seriously. Starting with the Scandinavian Jenkins community many years ago, we have now grown into running many conferences, community events, and meet-up groups. We are often speaking at international conferences and are always on the lookout for how we can contribute and participate in our field.
Each year we teach hundreds of students free courses in Continuous Delivery, version control, test-driven development, Docker and much more at our CoDe Academies.
We host several meet-up groups every month.
We are active organizers in the Scandinavian DevOpsDays scene.
We welcome interns into the company and give them a real chance to shine.
We release all of our tools and software as open source.
Praqma is soon turning 10 years old, but most of these values were present even from the founding of the company. The co-founders of Praqma, Lars and Leif, wanted to build a company they actually wanted to work in, a place that is fun, and that makes a difference in the world.
We believe this is not only the right way to contribute to the software world, we also believe it is the best way.
If Praqma sounds like a place you can thrive in, we want to hear from you. We are always looking for consultants, developers and sales persons in all locations. Reach out to us on email@example.com and tell us what you can bring to Praqma!
We’re hiring! See our open positions
Familiarize yourself with our on-boarding process: Get Your Orange Wings
Do you work on any hobby coding projects in your free time? Practice code katas? We all wish we could, but making time for learning away from work isn’t possible for everyone. So, who should pay for learning time?
A write-up on learning away from work
Consultants are valued for their expertise and the fact that they’re outsiders. In this post I’ll argue that the single most valuable skill a consultant can bring to the table is to break the mental barriers in the client’s organization.
Overcoming mental barriers to help your clients succeed
In the past we had all kinds of software specialists: requirements specialists, build specialists, configuration management specialists, and test specialists. Those days are over. We are now in the age of the Full Stack Developer.
Praqma - The Knowledge Company
Slack is great, but it gets really rowdy as your team grows. I’ve compiled a list of useful settings and features to keep you from drowning in Slacktivity.
Essential Slack settings to shield your sanity
Developers still suffer task estimates, despite knowing they’re just fudging numbers. Here’s how we escaped the crystal balls and horoscopes.
We're not psychic, so why do we bother predicting the future?
Developers love writing code because they get to invent things. But someone else has to use the code, operate it and even pay for it.
No developer is an island
We all complain about Legacy Code. We are limited by the leftovers from previous developers. But are we not guilty ourselves of leaving Legacy Code behind?
Leave no legacy code behind
The life of a consultant has drawn me back, but perhaps surprisingly, this time it’s not a return to my one-person firm.
High hopes this will be my most fun job yet
This is the bloody but ultimately edifying tale about “The Bonnie Situation”; I use this story as a metaphor for what consultancy is all about - solving problems. You’ll be introduced to Mr. Wolf - ‘Winston’ for those on first name terms - and you will see why we consider him a role model for any consultant.
A bloody yet edifying story about consultancy
Very often developers are engaged in multiple projects. So as an individual you’ll often have more than one milestone to work on in parallel. Learn how we have organized ourselves with issues and milestones in a Kanban style approach with frequent Office Hour sessions.
The planning approach at Praqma
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps