- IT is an adaptive world that aims to fit business needs and create new opportunities. - Programming requires making things work first before optimizing for speed. - Software development is an iterative process where the initial solution is rarely the final solution.

1. IT’s world,
with a marked tone
on software
2022.01.21 /om@

2. First, solve the problem.
Then, write the code.
(John Johnson)

4. In a room full of top software
designers,
if two agree on the same
thing,
that's a majority.
(Robert Glass)

5. • The first time God created the world, it became a total mess.
So God scraped the whole thing and started again,
and the big thing we learn is that after six days, God shipped.
(Dan Bricklin)
• God could create the world in six days because he didn't have to make it compatible
with the previous version. On the 7th day ... God began debugging.
• We have a deal with God – he doesn’t produce software and we do not produce
miracles.
(a software engineer...)
• ERROR 406: file corrupt: config.earth -- reboot universe? (Y/N)

6. UNKNOWN ERROR n° 5
Sometimes it pays to stay in bed in Monday,
rather than spending the rest of the week debugging Monday's code.
(Dan Salomon)

7. RUNTIME ERROR 6D at 417A: 32CF: Incompetent user

8. Walking on water and developing
software from a specification
are easy if both are frozen.
(Edward V. Berard)
Software and cathedrals are much the
same :
first we build them,
then we pray.
(Unknown)
You never finish a program, you
just stop working on it.
(Unknown)
The software isn't finished until
the last user is dead.
(Unknown)
And the users exclaimed with a laugh and a taunt :
"It's just what we asked for but not what we want."

9. Your code is both good and original.
Unfortunately the parts that are good are not
original,
and the parts that are original are not good.
(Unknown)
Beware of bugs in the above code;
I have only proved it correct, not tried it.
(Donald Knuth)
There are two ways to write error-free
programs; only the third works.
(Alan J. Perlis)

10. Always code as if a single
bug will bring the building
down.
(Unknown)
Code never lies,
comments sometimes do
(Ron Jeffries)
Talk is cheap,
show me the code !
(Linus Torvalds)

11. Programming is like sex:
one mistake and you're providing
support for a lifetime.
(Michael Sinz)
If debugging is the process of removing
software bugs,
then programming must be the process
of putting them in.-
(Edsger Dijkstra)
If we can't fix it, then it ain't broke.
(Debuggers motto, noted by John Bently)

12. 3 biggest lies on IT
• It works
• It's compatible
• You'll have it tomorrow
(Jean-Louis Gassée)
3 biggest Software lies:
• The program's fully tested and
bugfree.
• We're working on the
documentation.
• Of course we can modify it.

13. Hardware: the parts of a
computer that can be kicked.
(Jeff Pesis)
Software is getting slower more
rapidly than hardware becomes
faster.
(Wirth's Law)

14. Software is a gas;
it expands to fill its
container.
(Nathan Myhrvold)
Software is like entropy:
It is difficult to grasp,
weighs nothing, a
nd obeys the Second Law of
Thermodynamics;
i.e., it always increases.
(Norman Augustine

15. Beta: Software undergoes beta testing
shortly before it's released.
Beta is Latin for "still doesn't work."
(Unknown)
If at first you don't succeed :
• call it version 1.0
• try management
Old hardware becomes obsolete;
old software goes into production every
night.
(Robert Glass)

16. • Heisenbug : It is an error, which
disappears or alters when it is attempted
to be identified by analogy to Heisenberg
uncertainty principle in quantum physics
• DEBUGGING : Removing the needles
from the haystack.
• It's not a bug - it's an undocumented
feature.
• NBWAD : Not a Bug – Work As Designed
!!
• If at first you don't succeed, try/catch,
try/catch again
• If you don't have a good system,
make sure you get good users.

17. Laws of Computer Programming
1.Any given program, when running, is obsolete.
2.Any given program costs more and takes longer.
3.If a program is useful, it will have to be changed.
4.If a program is useless, it will have to be documented.
5.Any program will expand to fill available memory.
6.The value of a program is proportional to the weight of
its output.
7.Program complexity grows until it exceeds the
capabilities of the programmer who must maintain it.
8.Any non-trivial program contains at least one bug.
9.Undetectable errors are infinite in variety, in contrast to
detectable errors, which by definition are limited.
10.Adding manpower to a late software project makes it
later.

18. The most important single aspect of
software development is to be clear about
what you are trying to build.
(Bjarne Stroustrup)
Before software can be reusable it first
has to be usable.
(M.A. Jackson)
Any fool can write code that a computer
can understand.
Good programmers write code that
humans can understand.
(Martin Fowler)

19. A man is smoking a cigarette and blowing
smoke rings into the air.
His girlfriend becomes irritated with the
smoke and says,
"Can't you see the warning on the cigarette
pack? Smoking is hazardous to your health!"
To which the man replies, "I am a programmer.
We don't worry about warnings; we only
worry about errors."

21. There are only 10 types of people in the world:
those who understand binary, and those who don't.

22. I need the business to tell me it’s no longer being
held hostage by you IT guys. This has been the
running complaint the entire time I’ve been CEO . IT is
in the way of every major initiative. Meanwhile, our
competitors pull away from us, leaving us in the dust.
Dammit, we can’t even take a crap without IT being in
the way.
It’s not the upfront capital that kills you, it’s the
operations and maintenance on the back end.
Well, we need to start. We can’t make new
commitments to other people when we don’t even
know what our commitments are now!
With DevOps, there is a hypothesis-driven
culture, requiring everyone to be a scientist, taking
no assumptions for granted and doing nothing
without measuring.

23. You are a computer.
If you become front-end you'll count the likes on social media.
If you become back-end you'll be breathing deep on a mountain.
Listen! one life man. Become a Full-stack.
(Chetan M. Kumbhar)

24. 99% of the problems with a
computer, program, or code
are located between keyboard
and chair.
The 50-50-90 rule:
Anytime you have a 50-50 chance
of getting something right,
there's a 90% probability you'll
get it wrong.

25. The first 90% of the code accounts
for the first 90% of the development time.
The remaining 10% of the code accounts
for the other 90% of the development time.
(Tom Cargill)
Good programming is 99% sweat and 1%
coffee.
Programming is 10% science,
25% ingenuity and 65% getting the
ingenuity to work with the science.

26. Conway's Law
Any piece of software reflects the organizational structure that produced it
... If you have four groups working on a compiler, you'll get a 4-pass
compiler.

27. Some of the replies you'll hear from programmers
when something goes wrong.

28. Premature optimization is the
root of all evil.
(Donald. Knuth)
Get it right. Then get it fast.
(Steve McConnell)

29. Thomas’ First Law
Nothing is more
permanent than a
temporary solution.

31. Three years in IT
is like an entire geological
epoch.
(Paul Hardy)

33. Perfection is achieved not when there is nothing more to
add, but rather when there is nothing more to take away.
(Antoine de Saint-Exupery)

34. Make it work, make it right, make it fast. (Kent Beck)

35. Sometimes it's better to leave something alone,
to pause,
and that's very true of programming.
(Joyce Wheeler)

36. IT is a changing
and adaptive
world to fit to
business needs
or to create new
paths.