Here some killer buzzwords,
whichess them behind the big abstract magic to a greatnes ultra speed
development.
Here comes the big
drops:
Division of labour i.e. the specialization
Let smart person do the smart thing and boring guys make the boring things, also make artist guy make the art.
80 20 rule is the new 90/90 rule.
Use programming language that works, on the situation that be doing,
don’t use wrong things, have overall mental picture what you are doing, do not blindly
shot in the dark, but know what you doing; like it is some variant of a finite-state machine (FSM)
Redundancy
It is that
have more than needed, the robust when one break there is another. Have lot of workforce.
Like make two separated groups of people make the
same Black box, Have them kinda
fight against each other i.e. competition, I mean have; Say! Two to four --three
people groups to race which of them teams make the Black box faster and better,
the smaller Big O.
The winner team get a big price bonus this
make them super nay ultra motivated. To a participate on the challenging competitions.
Don’t have
these challenges to be about random poop, but hard critical parts of the thing
that is under development.
This all for le smart people; the boring &
Artist type they don’t need it, to the art is may be even harmful because it needed
to be a coherent; and the boring stuff that not need much resources, but monkeying
around.
You know three
people teams the mocking programming, one sit the front of a computer do the
all the coding, and two guys standing behind him mocking and nagging, because
them want win nice prise.
Shuffle mix
these teams every now and then, so they see more people and learn better from each
other.
Black box thinking on the functions
and classes.
There is no means how a code does it, but what it does, like the robust
and how fast it do it. No “Keep it simple stupid”(kiss) here, let it be convoluted
as it can be, and if it grow too unbearable just make them replace that part wholly
to a new part.
the Black box thinking, it mean you dont look it. Just accept, and
remember mutations are better and faster than the “return”.
Big turnover rate
Be nice give people a
change by hiring them on much, don’t let stupid gatekeeper block business
hiring all them relatives and friends, so no hr just hire yourself.
Check all
peoples Resumes and portfolios and check them demons keep mental note about the
best ones and hire them then, and bargain thru all salary issues. If there is thousand
applications then check all them thousand, you have probably do something more
boring and even free.
When you check them applications focus on how
big is candidate’s work memory and have he interests on all kinds of wisdom,
his mental faculties, it is not so much important about his coding knowledge,
but that is good if he just know some language, because he will learn while
doing. Also don’t hire expensive titular coders that has long rock star CV they
might be just part some work cartel and be much useless relative the expensiveness.
Hire rather more those that CV and wallet is empty they got hunger and
potential.
Big turnover, you now free Internship trainee
etc. It is win-win they got mark at the CV and you a cheap labour.
Don’ t much unit test
That is thing of the
past, there on modern IDE like Visual Studio, has a built-in testing thingies
like, if you forgot “;” it got red underline, and same if you forgot initialize
some variable.
No unit test! just some checks that functions
and code lines, and whatnow do what you expected them to do, make them print on
console or try them separated other code that you then see that them works.
Trust legacy code and
the makers of code languages and IDE’s and formulas.
Then there is also the market disruption, minimum viable
product(mvp).
Remember the thing you
do the product if it is cheap enough that is no burden to customer, and if it
even barely can hold it’s function customer will use it.
No comments:
Post a Comment