bdavis__

thanks for posting this, but I don't think it meets the definition of "Pretty simple".

go to work for Boeing or Lockheed. you might be surprised by the sophistication of missile seekers. and countermeasures.

note that what you see on TV in the current conflict may be several generations old.

Beliefs can change based upon experiences and time. It's called wisdom.

one just has to identify how society determines the "rich", and how much to require. both of these are very difficult questions.

i want to tax the rich! yes, i do. lets take a reasonable share and deal with societies ill's.

let's not take all their money; just the excess that there is no reasonable chance that an individual could use it.

for example, you could raise my takes $100 a month and it would not be missed, or noticed. in Elon's case, $10M a month would be nothing.

in general, a software dev anywhere might not realize the flaw. but an systems engineer or other aircraft and flight controls engineer would notice it. and they should have, when the requirements were written. and again when each requirement was verified prior to flight.

there are not person-specific clearances, but there are person-specific non-clearances; e.g. there are lists of people and companies that you cannot do business with because of them being non-compliant with ITAR.

You sub contract out hardware assemblies (and software) when you start feeling market pressure and your cost has grown to be competitive. Then you find, as a prime contractor, that you are still responsible for the product. You still have to maintain expertise. And, to keep the vendors in line you have to be able to at least threaten to bring the work back in house. All of this greatly reduces the cost advantage. Now days, the concept is "only sub out work that is done better than you can do; where better includes technical performance".

RedHat has a realtime kernel.

it is available from the mirrors. Currently also available from CentOS.

last time i checked, it would not load the NVIDIA driver. YMMV.

if you are in the < 120hz range, then it will probably work fine for most non safety critical times.

no one confuses gear from MFJ with "high quality". cheap stuff, that whets your appetite for the good stuff.

and yes, i have an MFJ tuner and the 20 meter QRP rig they sell. it is a ford or a chevy, not a lexus or a mercedes. (both items were received with parts loose and had to have some re-assembly).

you write an ECN (Engineering Change Notice). these stack up against a given part number (controlled by a drawing). then the drawing gets updated. this is where any conflicting ECN's get discovered.

Note: ECN's were how things worked when you had a draftsman. Most engineers do the CAD themselves nowdays.

HP 8640B puts out a clean and precise waveform. wonderful piece of test equipment from the world of RF.

put a short wire on the output, and tune it to 146.34 (for a second). bang, the local repeater will kerchunk.

yeah, absolutes never apply to every situation.

it is possible to go down in expertise, but not up. sometimes "fortran in any language" can be a viable approach depending...

note i didn't say a the best approach.

from a different angle: "non original team" might have higher defects, but i propose that "non original team" without process or time to understand the code base would be more accurate.

changing people requires a time investment. and the learning curve is steep at the beginning

it is probably because the new devs know so much more and are able to identify and communicate problems in code that others have written.

write code for the center of the bell curve (at your organization). the bottom will never understand anything, the top understands it all. You need to make the majority in the middle be comfortable.

that means slowly bringing in new language features, as they become widely known and practiced.

up next, chapter 2, about the docker infrastructure.

some problems cannot be fixed. they either need to be cancelled, or they will run to completion using 2 or 3 or 4 or X times the budget and schedule.

the real value is identifying these projects early. but identification is not near as difficult as getting the message understood by the stakeholders.

the telephone. with a wire. the one that has been around for a century.

call some one, talk about a specific topic. maybe e-mail a document before or after. on the phone you are not distracted by the notifications and the emoji's, you focus on the topic at hand.

get off my lawn!

how many existing scripts have you broken?

spend a few minutes doing the assigned reading before the lecture

preemptable, priority based scheduling is your solution.

if you are in a latency sensitive environment, the "fairness" or "throughput" of the scheduler are not things you care about.

next most important is 'pinning" threads to cpu cores, such that cache misses (or faraway memory) are minimized.

agreed. on all points.

when i was first exposed to ada, early 1990's, the language was unusable. compile times where excessive (like hours). machines of that era were slow and had small memories (4MB was a common size, and more than 1 CPU was a luxury).

i must also admit, ada was hard. you had to do some mojo just to print out a value ("package int_io is new integer_io blah, blah). it had a standard of a couple of hundred pages that you kept on your desk. and you looked at it on a regular basis. and the compiler was picky (strongly typed).

companies dropped ada because they couldn't hire. C++ people were more available.

my opinion today is ada is relatively small, makes very fast code, and supports all the programming paradigms of C++ in a very sane way.

if the first ada compiler was "ada95" instead of "ada83", it would be very popular. it came out a decade before the world was ready.

i would say it is interesting they did not use ada. best language every designed for this problem domain.

Note this applies to the manufacturing,not the design.

It is actually a wonderful analogy with software:

* to a first order, cost of the materials in an airplane are proportional to the weight * at design time, the weight of the aircraft is minimized. thus, political and management forces cannot change it.

just like software, each subsection that is bolted on has different weights; but if you average it out it is a good measure of progress. and cost.

when that call is over, the 60's, 70's, and 80's are on hold.

reliability is giving the right answer. availability is being ready to give the right answer.

cloud services have poor reliability and good availability.

all ham transmissions need to be identified on a regular interval with a callsign, assigned by the FCC. it is trivial to look up a callsign, and see if it exists.

"guardians" are the term used for members of the space force.

why oh why? how much complexity can we place between application code and the cpu? both linux and windows are too much..

roll with it.

the best ideas come from improvements. both the idea and the improvement have to be there.

it is a complement for others to parrot your ideas.

also remember, technical skills are only part of the picture; others may be demonstrating to you the political part of working in an organization.