We're looking for a ninja angular agile devops craftsman obsessed with TDD and OCD.

"Well technically.. you don't even really work, right?"

Germany.

Nobody in my family understand what I do for a living. My dad's reaction was; "that's not a real job". He's a craftsman/painter. But that's okay, I make more money then him 😊💵

are you a software craftsman or a software engineer? 🤔

This started as an update to my cover story for my Linked In profile, but as I got into a groove writing it, it turned into something more, but I’m not really sure what exactly. It maybe gets a little preachy towards the end so I’m not sure if I want to use it on LI but I figure it might be appreciated here:

In my IT career of nearly 20 years, I have worked on a very wide range of projects. I have worked on everything from mobile apps (both Adroid and iOS) to eCommerce to document management to CMS. I have such a broad technical background that if I am unfamiliar with any technology, there is a very good chance I can pick it up and run with it in a very short timespan.

If you think of the value that team members add to the team as a whole in mathematical terms, you have adders and you have subtractors. I am neither. I am a multiplier. I enjoy coaching, leading and architecture, but I don’t ever want to get out of the code entirely.

For the last 9 years, I have functioned as a technical team lead on a variety of highly successful and highly productive teams. As far as team leads go, I tend to be a bit more hands on. Generally, I manage to actively develop code about 25% of the time to keep my skills sharp and have a clear understanding of my team’s codebase.

Beyond that I also like to review as much of the code coming into the codebase as practical. I do this for 3 reasons. I do this because as a team lead, I am ultimately the one responsible for the quality and stability of the codebase. This also allows me to keep a finger on the pulse of the team, so that I have a better idea of who is struggling and who is outperforming. Finally, I recognize that my way may not necessarily be the best way to do something and I am perfectly willing to admit the same. I have learned just as much if not more by reviewing the work of others than having someone else review my own.

It has been said that if you find a job you love, you’ll never work a day in your life. This describes my relationship with software development perfectly. I have known that I would be writing software in some capacity for a living since I wrote my first “hello world” program in BASIC in the third grade.

I don’t like the term programmer because it has a sense of impersonality to it. I tolerate the title Software Developer, because it’s the industry standard. Personally, I prefer Software Craftsman to any other current vernacular for those that sling code for a living.

All too often is our work compiled into binary form, both literally and figuratively. Our users take for granted the fact that an app “just works”, without thinking about the proper use of layers of abstraction and separation of concerns, Gang of Four design patterns or why an abstract class was used instead of an interface. Take a look at any mediocre app’s review distribution in the App Store. You will inevitably see an inverse bell curve. Lot’s of 4’s and 5’s and lots of (but hopefully not as many) 1’s and not much in the middle. This leads one to believe that even given the subjective nature of a 5 star scale, users still look at things in terms of either “this app works for me” or “this one doesn’t”. It’s all still 1’s and 0’s.

Even as a contributor to many open source projects myself, I’ll be the first to admit that have never sat down and cracked open the Spring Framework to truly appreciate the work that has been poured into it. Yet, when I’m in backend mode, I’m working with Spring nearly every single day.

The moniker Software Craftsman helps to convey the fact that I put my heart and soul into every line of code that I or a member of my team write. An API contract isn’t just well designed or not. Some are better designed than others. Some are better documented than others. Despite the fact that the end result of our work is literally just a bunch of 1’s and 0’s, computer science is not an exact science at all. Anyone who has ever taken 200 lines of Java code and reduced it to less than 50 lines of reactive Kotlin, anyone who has ever hit that Utopia of 100% unit test coverage in a class, or anyone who can actually read that 2-line Perl implementation of the RSA algorithm understands this simple truth. Software development is an art form. I am a Software Craftsman.

#wk171

Uncle Bob paraphrase: You're a professional craftsman, act like it.

When the company hires freelancers who proclaim themselves craftsman and they don't care about quality.

Bloody Liers.

"The critical distinction between a craftsman and an expert is what happens after a sufficient level of expertise has been achieved. The expert will do everything she can to remain wedded to a single context, narrowing the scope of her learning, her practice, and her projects. The craftsman has the courage and humility to set aside her expertise and pick up an unfamiliar technology or learn a new domain." - Dave Hoover

I'm so fed up why stupid fucks who yell to everyone "You must do TDD, because... Reasons!!!!". The fuckers even dare to call themselves " agilists" or "craftsman"...

The only reason to do TDD is to create Good Unit Tests. But by not stating the main purpose, you add a stupid process without add value.... The solution just became the problem!

So what if something goes wrong? Well, you didn't really followed TDD, because TDD never fails!!

So fuck ignorant stupid fuckers!!!!!

Having Good Unit Testing is the aim. TDD is one way to do it. Not THE WAY!!!

Also, stop using the word " coverage". It doesn't mean fuck!! If you know what kind of coverage you are completing, there could be some value...

Someone from top company (German Automobile) commented that Indian coders are good but are not Craftsman in their development. I was very confused about that comment .. but if it's true . How should I improve it.

Why do modern Europeans like to wear wigs?

The prevalence of wigs is closely related to the social life conditions at that time. Because in the 17th century, Europe, it was very inconvenient for people to bathe and wash their hair. Louis XIV, the famous Sun King, took only seven baths in his life. Not taking a long bath and shampoo, it is easy to breed parasites, especially hair, hair thick, often sweat, it is easy to grow lice. The best way to solve this problem is to cut the hair short or shaved, but the hair is cut short or shaved, and can not reflect the identity of aristocrats, it is better to wear a wig, have the best of both worlds.

In addition to the aristocracy as a fashion, the real problem for a wig to become a status symbol, is that the wig is expensive and the average person cannot wear it. In the 17th century, the wig was very elaborate. At that time, there was no machine production, so it depended on labor. A skilled craftsman needed a few days to make a wig. A judge's wig costs £1,800, and a regular wig costs £300. This money is a huge expense today, not to mention Western Europe before the Industrial Revolution. Therefore, wearing wigs is not something that ordinary people can afford. And at that time, the wig was quite bulky, also uncomfortable to wear, often working people naturally will not wear.

In addition to being expensive and inconvenient to wear, the embellishment and maintenance of wigs are also quite cumbersome. The 18th-century wig often had some pollen and some paint added. Pink wigs are easy to drop powder, and they are difficult to take care of. So, it is naturally not favored by ordinary people. By the late 18th century, young men simply added powder to their hair. The wigs worn by women were large and striking, but they were heavy and contained wax, powder and other ornaments, becoming a sign of luxury.

However, with the beginning of the Industrial Revolution in the middle of the 18th century. Natural hair without wigs is slowly being accepted by more people. In Goethe's masterpiece, "The Trouble of the Young Witt," Witt's natural hair triggered a natural fashion trend at the time. After the outbreak of the French Revolution, the revolutionaries tried to establish an equal society, eliminate class differences, and the wigs representing their status were naturally among the objects of changing customs.

In addition, in 1795, the British government began to tax the hair fans, which hit the wig and hair fan fashion, and began to decline in the 19th century. By the 19th century, the wigs became smaller and grave. In France, wigs are no longer a status symbol. But wigs remained as a status symbol for some time. After the French Revolution, French wigs, which no longer became a symbol of status, were associated with professional prestige. Some industries and fields use wigs as part of their professional clothing, such as judges and lawyers. This habit continues to this day. Judges and lawyers in the Commonwealth wear wigs in court or at major ceremonies, a tradition in previous British colonies, but it makes them a mark of colonial rule.

The popularity of a generation of fashion, it must have its historical background, once