Sneak peak – Team Geek

When communicating with other people (not only with your colleagues), remember the golden rules which I picked up reading this fairly amazing book (a complete review will follow later) :

  • Ensure that your email can be read in 10 seconds.
  • Your explanations should be covered by three paragraphs at most
  • You should end with a call to action

It is amazing how this simple rule is not followed in most cases of everyday non-verbal conversation.

Motivating your team out of nowhere

Surviving crisis in IT

Lately I’ve been wondering that my posts are maybe a bit too general. This is why I want to share some really existing problems with you and my attempts to solve them.

At our company we had a rough time during the last year. On worst months we had only around 500 EUR income for the whole company, however we managed to survive and here are some hints on how to achieve it.

  • Transparency is the key to everything. If you are forced to delay payments to your employees, make sure they know everything about the situation. Hiding information can only lead to negative aspects, revealing it may lead to even positive reaction (for example almost all employees will just think, that you keep more money for yourself instead of paying them. Nobody will believe you, that you’re out of money too)
  • By your commitment to share the status quo you call in two outcomes, which are good for both sides – people, how really rely on regular payments (for example if they have to support non-working family members or pay credit rates) will leave as soon as possible, so you will avoid conflicts with them in future (and believe me, conflicts with this kinds of people are the most terrifying) and they receive a possibility to look for a „steadier“ job as soon as possible (which will mitigate their financial drawbacks).
  • The second outcome will result in a win-win-situation – some people will still say „okay, I’m staying, you can pay me whenever there is more income“. For you, as a company owner this is good because of two reasons – these people commit themselves to their job, meaning they will really work (since if they don’t, there is no point in staying, they will want their money). The second reason is simple – you can rely on those people in future. Both sides will know, that there are ups and downs, and if you survived together, this will strengthen your bond.
  • Next key point is the presence of a „leading idea“. And by that I understand some higher goal which your company should ideally have and try to achieve. Let’s consider an example – say, your company creates only generic websites for clients (shops and landing pages). Chances are, when in trouble, people will think – well, there is nothing special in my job, why should I even stay? Instead, if you are developing an interesting SaaS solution, which could impact thousands or millions of people, well – it’s almost everytime worth suffering for.

Last but not least

Don’t forget to reward people for their loyalty. If you survive the crisis together and you behave like an asshole at the end of the day, the most loyal employee will be your most terrific nightmare.

Business – fucked up style

Recently I stumbled upon such an interesting book, however it’s only available in Russian (Бизнес в стиле Ж). I would strongly recommend every project manager (not even in IT field), every business owner and other „higher“ positions to read this book. It contains only 200 pages and can be read in one breath.

One can freely say this book is focused on business survival (as the title suggests) and several ideas are worth to be remembered. Author is not the last person on Russian media landscape and owns Gameland which is responsible for multiple print and online media (car tuning, computer games, cinema etc.)

Few useful tips I gathered from this book:

[readolog_blockquote ]Be ready to denounce your previous experience, even if it was good and successful. Especially during crisis times.[/readolog_blockquote]

[readolog_blockquote ]Crisis times are similar to war times – pay no one, collect from everybody, care only for the fighters.[/readolog_blockquote]

Be ready to drastically change your business attitude (for example author, who was printing a 240 pages shiny magazine switched over to 160 pages magazine, printed on cheap newspaper paper (no pun intended)). Do not let any money leak – freeze (temporarily) all your debt flows. It’s better for each party (you and your creditor) to invest this money into further business development, because it’s the only way you can earn money and for your creditor to get his money back. Try to restructure your debts (most creditors are willing to give you discount if they will see payments from you). For the best employees (and most motivated ones) rise their motivation – if they suggest a new project, give them 100% of project’s income first year (sink it later on…).

[readolog_blockquote ]Always pay your debts (like Lannisters) – even if it takes you years.[/readolog_blockquote]

[readolog_blockquote ]Try to be as open minded as possible – talk to people, follow latest trends. You can never know what might be the next hit during or after the next crisis.[/readolog_blockquote]

Just imagine – Russians are generally hostile towards Muslim culture, however this didn’t affect their love for hookah at all! Or sushi – Japanese culture is considered as weird, raw fish is a no-go, rice isn’t that popular… but sushi you can find on almost every corner.

[readolog_blockquote ]All your employees are divided into three categories: Predators, Parasites, Owners and Sheep.[/readolog_blockquote]

While almost all your ordinary employees can surely be tossed into the sheep category, proceed with caution when creating a profile for your top management. You should avoid having predators and parasites at any cost and should encourage owners or owner-like behavior. Predator’s real goal is to snatch. For his own profit he will without a wink put your company in danger. Parasite is all about creating a busy impression – his input is extremely low compared to salary, and all his energy goes only into persuading you, that he is busy doing stuff. Owners are the most rare category of top personal – they treat your business like their own and are really willing to do everything to make it prosper. While during peaceful times predators and parasites will most likely successful hide their nature, giving themselves as owners, crisis time reveals such characters very quickly. Non-loyal employees have no right to be in your company. Your best guess would be if a top manager declines your offer to decrease his salary during crisis time in exchange for a higher share in company’s revenue – it simply shows that they don’t believe in your success and your clearly don’t need such people.

[readolog_blockquote ]Share more information with your key employees.[/readolog_blockquote]

Most likely, your general employee won’t care what is happening with your company – they simply care for themselves. Thus, sharing negative information with them won’t make anything better – this category of employees won’t be able to influence anything at all. However, the higher you climb on the position ladder the more information you should share. You simply can’t expect owner-like behavior if you hide important things from your top people.

I hope you enjoyed this short summary, feel free to (learn Russian and) read this book by yourself!

The Software Development Edge – Book Review – Part III/III

Finally I gathered all the strength required to finish this review. It’s a little bit tougher than back in the school days, however I hope it might serve some educational purpose.

As explained in the last post, this review part will not continue the previous path, but summarize the whole book (in a shorter way). You can regard this as a kind „best of“.

Core idea – Politics

[readolog_blockquote ]“Developing software is such a unique and complicated process, I can’t make an estimation how long it will take and I won’t take the responsibility for my due dates“ – this is utter bullshit. Software development is just as unique as any other professional field (just ask your friends). If someone refuses to take over responsibility it’s is clearly not because he/she is such a genius.[/readolog_blockquote]

Core idea – Crisis

[readolog_blockquote ]Act – that’s the main point. Regardless if you’re a hired crisis manager or were just moved to another project which is deep in the shit, your main goal now is acting. It will stink for a while, so don’t bother with keeping good relationships (with customers, other employees, anyone…).[/readolog_blockquote]

Core idea – Project

[readolog_blockquote ]Keep your project within the given due date. Do it at any cost – mostly you will be cutting off unnecessary features. However you can’t fit any project in any time frames. Take your time in advance and get an honest opinion from your team members how they estimate the whole project. You really need those honest opinions and people you can trust. If you can’t, it’s time to say goodbye to those.[/readolog_blockquote]

Core idea – Developing

[readolog_blockquote ]It might be some de facto standard right now, but still I see even in my team how things can quickly get out of control if you don’t invest time into concentrated continuous releases, called iterations. Force everyone to deliver something each week. It will require a lot endurance from you, but there is just no other way…[/readolog_blockquote]

I promised to keep it short and simple and here we go. Four core points which should awaken your interest in this book. If you want to intensify the review reading I would recommend you part I and part II, however more than that I would just suggest you go out there and buy this amazing book.

How to write useful technical specs

I might be not that wrong in assuming that a lot of IT people out there encounter same problems regarding tech specs all the time – they become obsolete sooner than they are written. Mostly created to show the client – hey, we’re doing stuff here, here is the result, 100 pages of pure informational power. However, the result is often the same – after one glance, each team member will soon forget that this spec ever existed.

So how make specs more useful? In this article I won’t show how to formulate your spec, but more how (technically) to manage, that your spec stays up to date.

Use LaTeX

No, not in the bedroom with your girlfriend (on the other side – who am I to judge you?), but the document markup language (according to Wikipedia).

LaTeX is not only cool – writing specs feels almost like writing code – but it allows you to maintain a healthy development process considering your spec.

Problem No. 1

When your specs are starting to get bigger and you add stuff here and there, it is very (VERY!) hard for your team to follow up on changes. Using GIT in combination with LaTeX allows you to commit any changes just if it were code. And GIT markup fantastically highlights all changes that were made. So next time you can just give your team a link to the latest commit to they will see only the new and recent parts.

Problem No. 2

Have you ever tried to create links within a document, say in MS Word? Yeah, you kinda able to do that, but if you add, say, a new point to your numerical list, all your links will get messed up. Regardless to say what happens if you add a whole new chapter at the beginning. LaTeX allows you to define variables, just like any programming language. Just use a simple


where section:intro is just a clear variable meaning that your content is in the section called „intro“.

Problem No. 3

As soon as you try to maintain your MS Word spec you realize how this program is clearly not created to write large documents. Ever tried to create a numerical list, then add a break and continue the list? Then you’ll know how easy it is to screw things up. By being completely controllable there is always an easy solution for almost everything you want to achieve with a LaTeX document.


I mentioned it already in the previous paragraph, but I can’t stress it out enough – your LaTeX spec will really shine bundled with GIT. Not only you have a neat version control (and don’t need to save „project_x_tech_spec.v.1.0.docx“, „project_x_tech_spec.v.1.8.docx“ and so on), an ability to link only your recent changes by sending a commit link, but you also have one place for your always up-to-date end format, because recently github learned how to display pdf-files.

So basically your pdf url stays always the same, something like this:

My setup

Since TeX is permissive free software (to me it sounds a lot like open source), there is a bunch of good free editors (honestly, even notepad will do it). However I felt in love with Texpad – it’s available only for MacOS (and iOS) and makes full usage of your retina display. It costs 25 $ and is available for download at Texpad homepage.

Starting writing documents with TeX may be a bit hard the very first time (on the other hand – what isn’t hard the very first time?), but there are plenty amount of templates out there on the interwebs helping your out to fire your document up. My personal favorite (there are few Russian language related things which you might omit) :

\documentclass[DIV=calc, paper=a4, fontsize=11pt]{scrartcl} % Документ принадлежит классу article, а также будет печататься в 12 пунктов.
\usepackage[utf8x]{inputenc} % Включаем поддержку UTF8
\usepackage[russian]{babel} % Пакет поддержки русского языка
\usepackage{titling} % Allows custom title configuration

%for frames

%For image using

%Numbering subsubsubsections etc

%For code highlightning

%Further enumeration - you might omit that! It can lead to strange numeration!

%For referencing within enumeration lists

%Packages for word-like comment style
%This is really awesome! You can add marks that are highlighted.
%My personal favorite usage is like this: \todo[inline]{some comment goes in there}

%Package for images

%For a nicer reference



%For some math formulas if needed

% Some nice visualization
%\usepackage[svgnames]{xcolor} % Enabling colors by their 'svgnames'
%\renewcommand{\headrulewidth}{0.0pt} % No header rule
%\renewcommand{\footrulewidth}{0.4pt} % Thin footer rule
% End visualization

%smart enumeration

\title{Some title goes in there}



... Here goes your content with \section{} and \subsection{} and everything else...


Happy writing!

The Software Development Edge – Book Review – Part I

Hear me, I beg. And say thankya, big-big. This one is going to be a hell of long post, but do not worry, you can browse through the cites really fast and get all the essential data you need. My very short summary – go and buy this book, remember (almost) every page, it will do you some good. The software development edge by Joe Marasco should be your holy book, your guidance in the dark realm of leading teams and developing software.

I counted exactly 170 good ideas, worth remembering. Regarding a total count of 370 pages we have a score 170/370 ~ 0.46, which is amazing! It means almost every second page you’ll encounter contains something useful.

As you might guess in my book summary I’ll have to cover over 185 pages of ideas. Since it would take too long to release a complete overview at once I decided to split it up in four parts, each covering around 100 pages of text. The first one ends exactly at page number 100.

For now, here we go – book’s best points, no cites but rephrases:


Spend a lot of time talking to your developers, get familiar with details and problems.

Worst combination possible – keenness absence and sloppy management. Mostly, it will lead to programs that don’t work and if they do, not very well.

If you happen to be the team leader, do not easily yield to your superior (of course you should listen and give in in most of the times, but not easily, because your superiors may suggest (due to their unknowingness) unreasonable demands.

Your iterative approach to solving problems: observe, listen, empathize, synthesize, testing, write down.
Observe – look around you. What’s happening? Where could be the source of a problem or maybe it’s symptoms?
Listen – after you’ve located the problem, talk to people and listen to their opinion. Talk less, write more.
Empathize – the clear difference is here to „listen“ – while empathizing you not only collect objective data, but also give subjective feedback.
Synthesize – now put all parts together: your objective data while observing and listening, emotional aspects while empathizing, your box of tools for solving problems (should be mostly your experience). The result – a possible approach for the given problem – should be put out to test.
Write down – now you should write down everything that occurs while your approach is doing it’s job. If you don’t do it it will become much harder to convince others to accept your approach. Besides, what’s not written down is soon forgotten.

Doubt everything. Check every partial solution.

In every big project someone, who is on his/her own is a potential danger. However you shouldn’t throw all people in one big basket. Create as little teams as possible with as little members as possible. Four groups three or four members each may be way more productive than an horde of 50 employees.

Sooner or later every leader will have to make choices. If your team members were chosen correctly they will accept your decision because having one is better, than none decision at all. However it doesn’t mean that you are free to come up with any crap idea – you still need to analyze give situation. The only thing to avoid is to be paralyzed.


The mountain top – the end of your project – should always be the main goal. Everything that hinders you and your team on the way up must be cut off.

On the other hand climbing up in real life is just the half of it, you also need to come down. This can be compared with supporting your existing project – a successful one can be completed and then supported over a long period of time.

Why projects fail

Nonrealistic time schedule

Too many team members, team contains a lot of mediocre developers compared to the best ones.

Neverending stories projects lasting so long, that all requirements change multiple times.

Ignore first iterations‘ results. No analyze and change after seeing them.

Lack of clear goal, understandable by everyone

What can lead to success

Small, but smart plan with few details is more effective than plan overloaded with details

Clear your work before requirements change

Correct your movement’s vector (use small iterations) on the fly

Durability – extraordinary peak strength means nothing on the long term

Concentration – your team don’t lose sight of the goal


Don’t hire high skilled people to involve them in trivialities.

Main point of every task should be a client’s problem. Even more important is for your product to generate additional value for your customer (by solving his problems).

Best leaders can project their sense of goal to others – by giving them a good example. Managers make sure that this goal is achieved. Best people out there unit qualities of leaders and managers.

Take care of every small problem in time. Even smallest problems tend to grow massively. This leads to two kinds of bad managers – the „ostrich“ ones, who won’t see the problem and the „lazy“ guys, who will postpone everything until it’s too late. Don’t be one of them, problems don’t disappear magically.

Do not let you lead easily. Always remember – your goal is to solve a problem, achieve some result, not to make you most popular and well-liked guy in the department.

Don’t panic. Seriously. Be solid as rock. Every crisis will be over, your duty is to participate in solving this crisis, not in overreacting. Be an example for everyone else (rock-solid).

Laugh. Even when facing dumbest customer’s demand, better laugh about it, do it, forget it than making drama.

Teams forgive their managers a lot of things, but laziness, incompetence, lack of reward for efforts and lack of humor are not among them.

Trust your instincts – if you are really feeling uncomfortable with something, trust your inner self, most likely you’ll turn our being right (this also means do not hire people who will make you uncomfortable – in exceptional cases it might be worth the risk).

Developing software

Goals are most likely not where they meant to be. Often because at the beginning the technical requirements are not quite clear und well understood.

During the process people will make mistakes.

Your goal is a moving one.

A good manager will always make a lot of little steps rather than few big ones. This allows to shorten the overall distance because after one misstep you haven’t travelled a big distance and after a dozen steps your next one will most likely be close to optimal.

Do not start with easiest problems. By doing so you’re digging your own grave. Your team won’t bother with upcoming possible risks. Even the easiest task will grow big (there is always room for improvement). This leads to scarcity of time for the real challenge and to one further problem – explaining that you need more time doing the most difficult part, covering the biggest risks is much easier to your superiors than begging for more time because your team was wasting it.

Iterative approach forces you to apply all lessons learned from this project (all previous iterations) to all upcoming iterations of the same project.


Happy new energy! This is how you make bitrix work with git.

I wish everyone a pleasant new 2015!

May your business flourish, your apps find new users and your customer forget the number of your technical hotline.

Besides, if you should ever happen to work with 1C-Bitrix framework here are some hints how to befriend it with git. If you just try to plain start developing a Bitrix app under git you may encounter few uncomfortable things – since Bitrix is huge (more than 18000 files) ever commit will take long. In most cases I received plain errors instead of pleasant working.

So here what you should do:

First, add this to your local git config

git config --local pack.windowmemory=100m
git config --local pack.sizelimit=100m
git config --local pack.threads=1

You may want to play around with the numbers, just keep in mind following:

Larger window sizes may allow your system to process a smaller number of large pack files more quickly. Smaller window sizes will negatively affect performance due to increased calls to the operating system’s memory manager, but may improve performance when accessing a large number of large pack files.

As seen here

So now which files to exclude from bitrix using rather .gitignore or /.git/info/exclude? Of course I can’t tell you where to put your development files, but it is a good practice not to touch those:


Meaning ignoring them is generally a good idea. This will save you a lot of time! Happy coding. (For the record – we’re using GitLab instead of GitHub for reasons of security, however commands are just the same for both of them)

Next book sneak peak

The next one, „The Software Development Edge“ by Joe Marasco is finally done. Since I’m continuing my more „scientific“ approach on book summarizations this time it turned out to be really extensive. I guess it will take a while to write everything important down.

A little sneak peak on my work regarding this awesome book by Joe Marasco.
A little sneak peak on my work regarding this awesome book by Joe Marasco.

[readolog_blockquote ]One of the main reasons for Joe being able to deliver software in time was his effort to understand every detail of development, every problem occuring, thus, leading to knowledge where you can make right decisions for the whole project movement. This effort is not based upon some kind of magic, but simply upon investing a lot of time in talking with developers.[/readolog_blockquote]

Nobody knows what it’s like… to be the PM.

Thankeee’sai for waiting. This post took a bit longer than it should have. But since I’m reading a real heavy one – Coders at Work, next book review will follow not so fast. However I want to share another few thoughts with you.

PM Tips – Part 1 – sales, talking, clients

I was wondering – are there any concepts that make a difference between a good it project manager and a mediocre one? Was I able to make this transfer or am I still somewhere deep below the ocean?

Let’s try to take a look from a bird’s view – if it’s possible.

[readolog_blockquote ]You will have clients[/readolog_blockquote]

That’s the sad truth. You will have to deal with clients. This means – oh gosh! – talking to them, persuading them, selling services to them, explaining stuff to them. By no means you should feel like a sales manager, but you will always have verbal relationships, like it or not. You may not like it, you may even hate it and be worst misanthrope ever walked on earth, but you’ll have to deal with it. Even if you work as technical manager, or CTO or just for a company where clients, paying your company, are cleared by other people, regard your superior as your client.

Do the experiment, you will discover they act just the same… they wont understand most things you say, so you’ll have to explain, you’ll need to persuade and sell them everything (you need new chairs for your team? It’s kind of a sales process too!). This part of PM tips doesn’t suggest that you should be or have experience as active sales manager, however you should get used to similar sales processes.

[readolog_blockquote ]Clients don’t know what they want[/readolog_blockquote]

Most of the time this statement is true, unfortunately. On the other hand… this is 70-80% what you’re paid for. See why you should get familiar with your clients? Because it’s not completely true, that they don’t know what they want, in most cases they simply don’t know how they want it (meaning the software you’re creating) done. Some research should be done to extract exact numbers, but I would guess the ratio 40%-60%.

[readolog_blockquote]Experience matters[/readolog_blockquote]

If you’ve done a few online shops you’ll probably know what to suggest to your customer next time. You won’t know every detail, your client either, but in this case your both percentage knowledge doesn’t work multiplicative, but convergent, thus, creating desired result.

How to get your team organized with 5$ per month

Some time ago I had a pleasure (no irony intended!) to start working in a company with no established developing process at all. There was no issue tracking, no communication tools, no code hosting…nothing (nothing but a Russian Bitrix system, but it doesn’t count, since it’s awful and nobody was using it). Now I want to share with you one of myriads of possible approaches. As it happens we pay only 5$ per month to make it work.

How to start?

First of all you’ll need a webserver. We decided to pick up the cheapest DigitalOcean droplet which is available for exactly 5$ per month. You can pick Linode or any other server, where you’ll be granted full root access. DigitalOcean comes with a fancy possibility to create a Redmine-Droplet in just 55 seconds, this is just what we did.

Where to host code?

Trust me, even if you have just one developer you better start using version control. Github is the most common service just to do so, however if you can’t afford sharing your code with the community you got to pay for private repositories. A wide known alternative would be Gitlab, which not only allows you to host the service on your own machine, but also doesn’t charge you for creating private repositories if you continue using on-demand version. I didn’t manage it to install Gitlab on our 5$ droplet (maybe I’m just not gifted… maybe it has something to do with recommended RAM size of 2 Gbyte and two unicorn worker units to be able to handle http requests – 5$ droplet got only 512 MB RAM), so we’re using private on-demand repos. However if you manage to install gitlab on your machine the following routine will be much easier, since pulling from Gitlab won’t requre any hooks as it will be on the same machine as Redmine itself.

How to connect them?

You’ll probably don’t want maintaining two systems at a time. This is where so called hooks come in play. You can try and install but for me, although I set up (at least I suppose so) everything correctly, it didn’t work.  What I did instead was following:

  • create an ssh-key on your server, where redmine is hosted (since chances are you won’t be able to copy the key to your clipboard you’ll need to send the file to your local machine first via scp
pbcopy < .ssh/
scp /some/local/directory
(I never know how to connect to my local PC, so instead I connect to remote machine and download the file)
For example - scp root@ /directory_created_for_the_key
  • now comes a tricky thought – since Redmine hooks only its local repos but your local environment is another one, we need a workaround. As depictured below you need to set up your remote origin as gitlab
git remote add origin
then you push using 
git push -u origin master
Gitlab Redmine connection visualization
Gitlab Redmine connection visualization
  • To keep your Redmine repo up-to-date, you’ll need, first of all, to create one (on the Redmine server) – simply git init /home/redmine_projects/project1
  • Create a cronjob – nano /etc/cron.d/sync_repos
  • Repeat the line for each repository (app should be the owner of the repository. In our case it is „root“)
    */5 * * * * app cd /path/to/project.git && git fetch origin && git reset --soft refs/remotes/origin/master > /dev/null
  • Wooosh! You’re done! Now every push will be visible just 5 minutes thereafter in your Redmine repo-tab.
Now your repo on the server where redmine is installed is always up-to-date (with a 5 minute delay).
Now your repo on the server where redmine is installed is always up-to-date (with a 5 minute delay).

The mythical man-month

Would you call me arrogant for retitling this book as „Mythical technology no one cares for now“? You have the right to do so. However I want to provide some argumentation for that if it please ya.

To tell long story short – the main thesis of the title, that adding people to late projects will delay them even further is mentioned in the second chapter of the book. Until the 17th chapter you’ll deal with ancient stuff about OS/360 (what the heck is that?) and IBM 1771, Machine 881295, coding languages so ancient they make Greek Gods seem modern. I have no issues with people wanting to learn from the very basics. But generally this is not effective. If you want to dig a hole in your garden you go to the supermarket, buy a shovel and do the dirty work. You won’t, however first go and buy seeds, plant a tree, watch it grow, go to the mines, prospect the ore, process it, create the shovel blade, cut your tree (same procedure for the axe by the way?), make the handle, connect the blade with the handle and…finally dig!

Yes, you could do that, but it’s just not effective. You just rely on people who create this stuff for you. It’s important to have a basic knowledge (that a shovel blade made from paper might seem as a bad idea) but still you need other qualifications for digging a good hole.

Is this post just about nagging or will there be something constructive?

It’s the same with this book – not only it gives the reader such outdated information (ok, ok, it was written few years ago, 1974), but it’s also written so damn complicated and jumps from one extreme to the other – it’s either written too general (although I’m not the dumbest person I wasn’t able to understand) or so heavily loaded with detailed information about things one one knows they even existed without even explaining it!

You see, this is the main point – if this book should be an introduction it clearly lacks all introductional features as explaining material. If this book is a summarization of some facts… well I guess it was good back then, but now I don’t see the point of it. The mythical man-month suggests that this book is about people, about working with people but it’s just a practice report from over 40 years now. I might seem to brag here often about the release date, but you know what – other authors show that this is clearly not an issue at all, just take a look at DeMarco & Lister (if you haven’t read my article about their book – just skip the article and go buy their „Peopleware“)


Let’s consider two quotes from the book:

Consider the linkage editor, designed to load separately-com- 
piled programs and resolve their cross-references. Beyond this 
basic function it also handles program overlays. It is one of the 
finest overlay facilities ever built. It allows overlay structuring to 
be done externally, at linkage time, without being designed into 
the source code. It allows the overlay structure to be changed from 
run to run without recompilation. It furnishes a rich variety of 
useful options and facilities. In a sense it is the culmination of 
years of development of static overlay technique.


The unexpectedly hard part of building a programming system is 
system test. 1 have already discussed some of the reasons for both 
the difficulty and its unexpectedness. From all of that, one should 
be convinced of two things: system debugging will take longer 
than one expects, and its difficulty justifies a thoroughly system- 
atic and planned approach.

You take the meaning? First quote – my wtf moments: what is linkage editor? Cross-references? Program overlays? Overlay facilites? Structuring to be done externally? There is a lot of information in this text. But is it useful?

Second quote – a hell lot of text for saying… debugging is hard?

My advise at the end, if you really want to read this book – skip chapters 4-13 and chapter 15 and 16. Just do it, you won’t miss anything you’ll require for a start of your career. Basically in chapters 18 and 19 (of the second revision) the author summarizes his own book, commenting own statements 20 years later (revision was published in 1995).

[schema type=“book“ url=““ name=“Mythical Man-Month“ description=“This is the official description from Amazon, don’t come hereafter and complain – I warned you! Few books on software project management have been as influential and timeless as The Mythical Man-Month. With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.“ author=“Frederick P. Brooks Jr.“ publisher=“Addison-Wesley Professional“ pubdate=“1995-08-12″ edition=“2nd Edition“ isbn=“858-0001065793″ paperback=“yes“ ]