To make matters worst, what you see with your open eyes, is not one image, is a collection of images with all kind of distortions, blur and other smudges that your brain "photoshop" away to produce an image that conforms to the flawed/bias criteria that your brains considers to be a good image. The same happens with your ears and your taste buds. Reality in our brains is pure poetry.
Asm 56 GB/s (you are reading Sanskrit)
C 41 GB/s (you are reading US Tax Code)
Rust 30 GB/s (you are reading English)
Python (why bother) (you are speed reading )
So many tools, so many languages, life is great.
What brought me into the coding world was its novelty. In those days an electronic games were: Merlin, Simon and Mattel Football. Today, there is nothing novel about coding and its crushing and relentless.
At one point the mobile phone turns into a Skinner Box?
It is my claim that the amount of hours vested on Internet
consumption is directly proportional to the inability
to interpret in person body language, verbal cues and in person room reading...among other things.
Not to be thrown into semantics but...
Scope vs. Goal
The goal defines the scope.
If the goal does not change, neither the scope.
When the goal includes a date...the scope has no way
to adjust because scope refers, simply put, to a to-do list. A poorly conceived date does not change the scope,
it cuts short the to-do list.
How long does it take to a Nascar Team to win the Indy 500? 500 miles as fast as humanly possible.
Containers add a substantial level of indirection for us, developers. Now we have to grow a seventh arm to juggle to manage/fold into our workflow.
For production? Hands down the right solution. For development, I wish, only wish, We could live without.
One well written document can spin out many programs. One well written program cannot spin out a well written document. Is up to savvy developers and ultimately a computer to give thumbs up to a program. A document on the other hand has a subjective bar for approval. When documents and programs clash (the program not doing exactly what the document asks), to people's chagrin, the program wins.
I worked in the DELL Manufacturing plant in north Austin (Metric Blvd) on the 386->486 heydays. The DELL Optiplex 386SX will run around 800 to 1200 DLLS and came pre-installed with MD DOS 6.1 and Windows 3.1. When the 486 machines started churning out of the factory Windows 95 came to be and the PCs came pre loaded preloaded with a short action snippet of TOP-GUN and MS Encarta Encyclopedia so you could test your optional and expensive Sound Blaster 16 card. Our competition were Compaq and Packard Bell.
Ah! Another case of who police the police. The police police the police. Good news that the spare PCU took over and it was good. We all hope that the spare PCU was not part of an unlucky manufacturing batch. Great article.
True that. Also we all plateau at it. That is where time and effort stops yielding satisfaction or usefulness. Unless, unless, you are really in love with yourself and thing that everything you know is amazing...just kidding.
One question from a Junior Dev or any dev for that matter with multiple possible outcomes depending:
Q: Hi <insert dev name here>, say, why are you asking in my review if the class I introduced is really necessary?
Answer from the Paranoia Distroya.
PD: (Without taking their eyes from the screen or their hands off the keyboard). What is exactly the reason for the class?
You: Refactor common functionality.
PD: Well, long pause while typing really fast, that common functionality may change.
You: May?
PD: (long pause) I'll take a another look....
You leave after an awkward silence, next day your check-in is reverted and a new check in from PD has the module updated and the comment in the
code review marked as resolved.
Answer from Mr. Rogers.
MR: See, base classes are like like a regular class but they are also special. They provide an added layer of encapsulation.
You: So....
MR: I tell you what, lets go to your desk and I'll help you work on the base class and update the code with something that is much
better, then we will update your review and having it all tied up before lunch.
You and Mr. Rogers sit with you and tells what to change while he proselytize on the amazing powers of some editor. You try not to sight. He approves
the review with a smiley emoji.
Answer from My Friend From Across the World (over SMS).
MFFAW: What review? Can you give me review no?
You: DFDDS-4322343
MFFAW: Code change, check co: 5234543
You: I see commit, what of it?
MFFAW: Library removed, NA.
You: What library?
MFFAW: brb
You don't hear back from MFFAW, during scrum you ask again what to do about the code review, MFFAW gets the story assigned and
the review is closed. The code is checked in. A week later MFFAW updates the code and the base class you added is gone.
Take away: Ask questions; be ready to roll with the punches.
In elementary school we played soccer during recess. The kid who owned the ball wanted to play striker. We wanted him to play defense because he sucked. He played striker because it was his ball. The government treats Ballmer the same way. We don't want Ballmer to take his ball elsewhere.