9659

a little bigger, more complete, example would help. this is something i have never seen in C++.

(note C++ is a big language that changes a lot)

Related but not the same model of computer.

If the computer has visibility of the program counter using LED's (right next to the switches) visually the operator can see what the program is doing.

Well, at least they have an idea. "It's flushing the line printer. See, how the left most PC leds are off, and the pattern being displayed. it is writing data to the printer".

Or, "something is wrong, the PC is stuck in a loop, see the pattern".

Very different way to get a feel for an operating program.

small, oft ran program, of course.

we agree on all the facts.

i paid my $2,300.00 monthly electrical bill without complaint. (usual about $75)

the upside and downside were understood.

Not a swindle.

One company offered a plan where all of the electricity was purchased on the spot market. All of it.

Spot market purchases of electricity are very cheap. Except when they aren't.

Most months my electricity bill was 1/2 of current.

As a resident of texas, allow me to describe / explain how electricity works.

Consumers can select from maybe 50 "retail providers". They all have some kind of marketing deal, like "all green" or "free weekends" or "0.14 a kwh fixed for 3 years".

You pick your deal and deal with this 'company'. All of the electricity comes from the same place. All of the wiring is maintained by one company.

Your "choice" is deciding who sends your bill and collects the money.

Seems like a monopoly would be a lot cheaper. Less employees, less infrastructure, less advertising.

"Runaway stab trim". It is a memory item, every pilot should be able to perform it from memory.

Turn off the motor, and the trim is manual. There is a crank right there in the cockpit. If it is too hard to turn, change aircraft configuration to reduce the forces required to. Pilot know how to do this. This pilot stuff, they understand the forces on the flight controls and what impacts them.

Boeing made an engineering mistake. The pilots also made an operational mistake. Unfortunately, both mistakes at the same time were fatal.

I pray that pilot training has improved. And that Boeing has made systems level changes to the aircraft that will preclude it happening in the future.

And that is how aviation becomes safer every year; at a significant cost of customers lives.

About 2000, Software QA (and almost all traditional QA activities) were changed. The focus was on process over inspection. "Design in quality, do not inspect it into the product"

Suppliers (to include software) were expected to manage the quality of the product they provided; the purchaser would focus on how they managed the process, not in the compliance of every part.

This had a chance until software process was tossed in the name of "agile".

The missiles are designed, built, and installed by the contractor. They are managed, operated, and controlled by the USER. USAF.

Over a 50 year life. With very strenuous time to launch requirements. By staff that is well trained, but not well experienced.

An ICBM is a lot different that putting a payload in orbit. Needs to sit for 10 years, with 21 year old technicians performing the maintenance. And then launch when desired, on short notice, perhaps with portions of the support systems inoperative.

steal the example programs, and make them your own.

good performance, good reliability.

I wouldn't use the word "regularity", but the pleasure of debugging a long standing issue on a RHEL 5 machine came up in December.

had to compile git and tcpdump from source.

all in all, a pleasant experience. vi is the same.

except when it is.

> better yet create a document you can reference establishing your guidelines. How about working on a document that establishes the companies guidelines?

I can not imagine having to meet everyone's personal quality bar.

270 to 240. 11% of body weight.

The persons knee's will be stressed a little less. Back problems, perhaps a little less probable in the future.

Personal mobility improved by a bit. You will move around more. The stairs will not be as punishing.

Blood glucose magnitude down. Control of glucose up. Diabetes side effects maybe put off for another 5 years.

Just because it does not solve your problem, doesn't mean it doesn't help it.

(M60) here. first year of college, 1982. fortran programming. the basement of the physics building was called the "Student Input / Output Facility". A room full of keypunches, about 1/2 broken. two card readers and two line printers. there was a student employee on duty 24 hours a day with the job of keeping the printers in paper. The students had a line until 2 or 3am, waiting for the card reader.

There was also a room that said "graduate students only". It was full of ADM3 terminals, connected to the same CDC computer as the card readers / printers. Along with documentation. Lots of documentation. I never punched a card, but probably spent more time reading and learning how to use the time sharing system.

Hacker story. So, you want a student account and password? Make up a card deck with JCL that just copies from stdin to the printer. Put one 'blue card', which means "end of record". And no 'red card', which meant end of job. Get in line, run your job. The next student job (unless it started with a red card, which was recommended, but never done) would copy to the printer output of your job. First line was account name. Then a comma, and then the password.

You were in.....

That was the last year of cards. Undergraduates got terminals. And the CS dept got a pdp 11.

The ada concept of "package spec" and "package body" does headers the right way.

Expose the types, and the public procedures. Users only need to see the spec during compilation.

operational use, this was a specific problem, and it was imposing on mission success. those get fixed fast, even on manned aircraft platforms. (time more likely in weeks, rather than days).

space-X hopefully did a risk review. what is the chance this "100 line fix" is going to break something else? what was the in lab coverage? can it be rolled back?

sometimes you say you want agility; but you would really prefer low risk of greater failure.

The government pays for the development costs. They will not pay for a subscription unless the contractor takes the up front risk of developing the software.

Federal contracting rules also limit the profit that can be made selling to the government (you can argue this are not effective).

Some 'agile fans' have been promoted up a few notches at Lockheed, that is all this is.

The USG likes to pay for and own source code and weapon system designs.

The 're-implement in rust' crowd is doing it for the evangelizing of rust. If they cared about free software, they would have improved the existing tools.

I long for the days when the basic unix system is unusable because everything has been "improved" and is "secure and written in rust".

Nope. You can eject from 2 aircraft before the military takes away your keys.

You were right. Give it another 25 years. sincerely, a no code extra.

replacement?

why not make df better...

you identified the exact problem. developing a website with very inexperienced people? requirements very fluid from the customer (they know what they want when they see it)?

agile, as practiced today, is the way to go.

building a defined system with performance requirements? with a budget? using staff that understands the technology?

something else, is the way to go.

in my experience, a short requirements exercise (say 10% of the expected project duration), followed by development iterations, is the way to go. how long are the iterations? between 2 weeks and 3 months.

take time for design. have milestones where the system is functional and stakeholders can interact. but not continuously.

"an increase in velocity should come natural as your codebase expands"

you may not respect academic software engineering, but if this is true you have just created a perpetual motion machine.

changing / adding software to a system becomes more expensive (takes more time) as the size of the system increases. and it is not linear.

Defect in software. Identified and corrected.

Lucky it wasn't important, like "inadvertent display of advertisement to non optimum user".

You know, something important.

1983 called. Ada would like a word.

not sure how you feel about charities, but this one seems to be legit and one that does not waste money on overhead.

i mailed (from the US) a check. you need to put 3 US first class stamps to get the letter to Canada.

used vi(vim) every day for a very long time. thank you, sir.

Most of it is. The job is called "bookkeeper"

Zuck collects private information and uses it to sell advertising. Elon runs a car company.

What do they have to do with CS?

"Peak CS" was last year.

Not every school has peaked, but many have.

It will drop for the next 5 to 10 years.

(FAANG hiring freezes will disincentive students...)

Ham radio is an avenue to get kids interested in electronics.

The spectrum is worth it for that alone.