(...) Economies of scale are the cost advantages that enterprises obtain due to size, output, or scale of operation, with cost per unit (of output) generally decreasing with increasing scale as fixed costs are spread out over more units of output.
This sounds so reasonable & generic, it's has been also empirically proven for traditional (related to "physical" goods) industries. No wonder that
If you haven't yet, check the part I first.
Where were we? We've figured out that your job may wave you good-bye & go to Fareastan. But it doesn't conclude the consideration just yet ...
Is the growth inevitable?
Are we completely sure that software development is on permanent rise?
World is crazy about software, everyone wants to build new "digital" services, but if you
These are great times to have a software developer career & I've written a lot about that already. There are tons or open positions available & they are all very well paid, when compared with other industries - we all know that. But the key question is - when will this bonanza end (and how)?
"India is now producing almost one million
Do you recognize any of the following scenarios?
- Continuous influx of requirements put you into permanent death-march - you're always struggling against deadlines, there's never time for refactoring, unit testing, etc.
- Firefighting is your bread'n'butter - issues pop up on daily basis here & there, so there's never time to fix (or even locate) the root cause or go through thorough post mortem.
There's a common saying:
The truth will attend to itself.
Quite naive one, I'd say. Sadly, it sometimes doesn't work even in the world of IT (supposedly based on scientific & engineering fundamentals), especially near the boundaries between engineering & other disciplines where everyone considers himself an expert (or at least pretends to be one).
So, frankly speaking, bullshit is everywhere. Plenty of bullshit.
We tend to think about software development as a very special & unique "discipline", positioned somewhere in the middle between science, engineering, craft, even art. And in the end we keep finding out that the same patterns & behaviours we observe everywhere else, apply in software development as well. One of the truly interesting (& to some degree - surprising) cases is ...
There are more and more open software developer positions in the market. And it's not just about quantity - breadth & variety of roles, technologies, platforms & languages continuously increases - to the satisfaction of all of us. But if you look carefully at the full spectrum of offers available, you'll notice that NOT ALL job offers are about ...
- ... technologies / platforms considered "modern", "promising"
Some time ago I had an interesting discussion with one of my colleagues regarding what is the typical thing that goes wrong when software delivery project turns out to be unsuccessful. Many of the reasons we've identified were not really revealing:
- new, unknown, bleeding edge, unproven technology - comments are unnecessary, but let's assume we play safe (just for sole purpose of this article)
I play a lot with new stuff - frameworks, libraries, tools, whole platforms or languages. Development toys, operations toys, process tooling toys even. And there's a lot of goodies to play with as new ones appear pretty much on the daily basis. I do it because I like it, but there's a more serious reasoning behind that as well - one could say that
No, I'm not switching to polish permanently, this post is just an exception. Stay tuned.
Ten post wyjątkowo jest po polsku? Dlaczego? Bo to nie jest post skierowany do wszystkich, tylko pewnej konkretnej grupy ludzi działającej przy tworzeniu oprogramowania - ludzi, którzy ciągle nie mogą zaakceptować faktu, że język angielski to 'lingua franca' tej branży.
Who of you hasn't heard that from a more senior colleague / boss?
Software development hasn't truly changed at all in past 5/10/20/30 years. It's about all the same patterns / models / approaches that keep having their highs and lows alternately in cycles.
It may be an oversimplification, but it's true in surprisingly many cases - keep in mind recent renaissances of:
What if ... a hypothetical company published a hypothetical job ad like that ...
(this is not a real job ad, I'm not representing anyone or looking for any people - I'm just wondering whether industry is mature enough to call some things by their true names ...)
We're looking for a software developer (technology X). Background, experience, past projects are irrelevant as long as you know