This blog post is all about: that Ninja doesn't differ from Rockstar, why Fullstack != Versatile, is switching tech stacks a failure, what does the tech swap's success depend on, why bother re-specializing if job market is a paradise for any tech, how learning Elixir changed my C#-fu.When browsing programming job offers you're getting attacked by very different position descriptions:nouns that depict position vary: Engineer, Software Engineer, Programmer, Developer, Ninja, Rockstar, ... :)seniority adjectives vary: junior, mid, regular, aspiring, senior, lead, leader, principal, ...the only part that remains the same (& always appears) is the name of the technologyApparently…
All posts in Software Engineering
Tym razem nietypowo, bo po polsku. Ale również w nietypowej sprawie i poza "standardowym" cyklem publikacji - otóż dzisiejszy blog post to ... ogłoszenie - z kategorii "praca szuka człowieka". Nie będzie to pierwszy raz - zdarzało już mi się publikować info o rekrutacji w tej formie i ... szczerze mówiąc wyniki były zastanawiająco pozytywne. Spróbujmy więc jeszcze raz ...W związku z rozwojem firmy, ale również zwiększeniem zakresu moich obowiązków ;D, poszukuję osoby na stanowisko ...(Software) Engineering ManagerParę suchych faktów na początek:firma/produkt: http://www.shedul.com/ i https://www.fresha.com/ (to dwa brandy tej samej platformy: SaaS + Marketplace)lokalizacja:…
This is a blog post about blitzscaling, difference between marines & soldiers & police officers, which of them are getting the shit done, why do the "code ninjas" & "programming rockstars" fail and how you can turn that all into your advantage.Few days ago I've started reading "Blitzscaling" by Reid Hoffman. I'm not done yet, book is OK, I do agree with a lot of things (but I still do not with some), however today I've found something really worth sharing. A classification of attitudes (mindsets?) of people that are the most desired/beneficial at various stages of modern…
This blog post is all about how spoiled we are when it comes to our salaries :), why theory alone doesn't make you a "senior", that stepping back may be the best way to make a meaningful step forward, who is Salva Ballesta, why you need to start finishing & why skills make only 1/3 of proper candidate evaluation.Disclaimer: not all companies are alike, not all hiring managers are alike & there's always someone desperate enough to break all the rules :) What I present here is my point of view & the rules I follow personally. Feel free to…
This blog post is all about ... designing nuclear power-plants, insatiable desire to put CQRS, eventsourcing & microservices in every software product, engineers' maturity, what's more important: problems or solutions & how JIRA can help (yikes!).There are some terms in IT you'll probably never learn at any CS University course. Yet, they are too important to omit & one of them is "bike-shedding". Frankly, I haven't heard this particular term until last year's outstanding presentation by Jimmy Bogard.But let's assume that for whatever reason you haven't so far & don't want to watch Jimmy's vid. Basically ...Bike-shedding happens when…
TL;DR In majority of scenarios real technical mastery has a tertiary degree of importance - being just solid, playing it safe & avoiding accidental complexity is just enough until market gets very dense, interest reaches viral levels or competitive factor is about pure tech (very rare). Very few companies (excluding some unicorns) compete with just tech as their primary weapon - it's usually all about the product, idea behind it & how fast it has been delivered (before the competitors ...). Disclaimer: keep your seatbelt buckled up, we're going to get a bit controversial here & you may not like…
TL;DR Building software while "on auto-pilot" doesn't work well - operational automation is more than advised, but understanding (in-depth) why-you-do what-you-do is absolutely essential. However, there are certain practices many stick to, without really understanding their purpose & descendant effects. One of them is "staging" - an anti-pattern that should in general be avoided, but when applied properly, can temporarily reduce the risks & help in transformation towards more mature delivery model. However, too many thoughtlessly treat it as a permanent element of their delivery pipeline, w/o thinking about its consequences & accompanying "…
TL;DR The entry threshold in software development industry gets lower & lower - it's a great opportunity for so-called developing countries to spur the "close-the-gap" efforts towards more advanced ones. Some approach it more naively (ehhh, India ...), some approach it smarter - I had a chance to take a peek into how it's done in Tunisia, perceived as the most open & progressive Arabic country. My general impression is that Tunisian software developers have strong enough foundation to be competitive / cooperate as equal (depends on whether you see them as competition or associates) with their European / American…