Archive for the ‘SEMINARS’ Category

Life of A Programmer — Session 5.1 — You are a Quality Assurance Manager

January 14, 2020

You are a software engineer. You work for a great software
development company.

Would you believe it if I told you that you are a Quality
Assurance Manager.

You don’t believe it! I don’t blame you.

Q.A. is a management activity. It is taught in Business
Administration.

You have a college degree in Software Engineering, not
Business Administration.

MORE IN THE NEXT MESSAGE

 

Life of A Programmer — Session 4.5 — How can you become more skilled than your fellow employees.

January 6, 2020

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

In 1961, Lockheed had a standard document called an ANVO. This meant
“ACCEPT NO VERBAL ORDERS”.

This is a very important and valuable concept. Spoken commands are
more likely to be misinterpreted.

Your boss might only make verbal commands. In this case, give him
your interpretation in writing.

When an ANVO has been issued, make sure that its required effort
is properly documented in your log.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.4 — How can you become more skilled than your fellow employees.

December 30, 2019

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than
three or four pages.

Each source code file should have lots of descriptive
comments.

Each source code file should reference a section of
your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able
to instantly relate to its design and use when you open
its file.

You might have to answer a question over the phone a year
after you complete the project.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.3– How Can You Become More Skilled Than Your Fellow employees.

December 23, 2019

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

Keep an accurate written log of your activities.

This log should contain the beginning and end time
for each activity.

This log should briefly define the activity and its
results.

Where appropriate, the log should reference particular
sections of your plan.

The “Weight of The Evidence” is always valuable in any
progress report.

You will always be able to show management your current
status at any time.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.2 — How can you become more skilled than your fellow employees.

December 16, 2019

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

In many companies, when a new major task is assigned, the
responsible software engineer will be asked to make a plan.

This plan will be presented to management and the senior
programmers for their comments and criticism.

In most cases, this plan will become obsolete and forgotten
with the first software development keystroke.

To become more valuable in the eyes of management, you must
strictly execute the plan that you have prepared.

It can be done and you will learn how to plan your tasks much
better than anyone else

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4.1 — How can you become more skilled than your fellow employees.

December 9, 2019

You were recently employed as a software developer in a major software engineering company.

You have a family that needs the financial resources that your job provides.

You need to reduce the risk of layoff and increase the probability of a raise.

Your needs are more likely to be met if you adopt the following four principles.

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

MORE IN THE NEXT MESSAGE

 

Life of A Programmer — Session 3.3 — But You Have a Challenging Software Engineering Job.

November 25, 2019

Around 1975, the employee / employer relations began to change.

Employer / Employee loyalty diminished with each passing year.

Job Seekers with many employers on their resumes were favorably considered.

Everyone effectively became a “temporary employee”.

Currently, you are upper-middle class. However, your future is not certain.

MORE IN THE NEXT MESSAGE

 

Life of A Programmer — Session 3.2 — But You Have a Challenging Software Engineering Job.

November 19, 2019

Let me present to you the long term history on employee / employer relations.

I joined the Lockheed California Company in 1961.

At this time, there was a strong loyalty between employers and employees.

Employees were expected to stay with their employer for their entire career.

Employers were expected to keep their employees for their entire careers.

Job Seekers with more than several employers on their resume were not favorably considered.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 3 — But You Have a Challenging Software Engineering Job.

November 12, 2019

You have a challenging job with a great software engineering company.

You have a software engineering degree from an excellent university.

Financially, you are upper-middle class.

You have a nice house in a upper-class neighborhood.

Your feel that your future is certain.

I beg to disagree. If you can accurately predict the future, you are in the wrong business.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 2.2 — But You Have a BS Degree in Software Engineering

November 4, 2019

A College Education does not qualify you to be truly a “software engineer”?!

Your degree was granted to you when you successfully completed a set of classes.

Each class is basically a reward / punishment training process.

You satisfy the instructor, you get a good grade.

For all intents in purposes, you cannot become more skilled than the instructor.

To do so usually means that you are not using the techniques that he is teaching.

Disagreeing with the instructor usually does not result in good grades.

MORE IN THE NEXT MESSAGE