I agree. I think it gives a quicker view of what is happening and for some subset of diagrams I have wanted to use tools that do more of this to help people build a mental model.
503 karma · joined December 9, 2023
"Tesla Cold Fusion (TM) will be powering all of our vehicles by 2031."
It would be nice to get to the feature level, meaning across files/classes/functions etc.
I was thinking any breakthrough in hardware (e.g. spintronics etc.), even if just partially effective, means all of this hardware would need to be replaced.
I bought my first new car in 1989, a Camaro with T-Tops and it cost me, $12,250.
> Cause and Effect: If Neuron A fires just a few milliseconds before Neuron B, the brain assumes A caused B. The synapse between them gets stronger.
A recent study from Stanford found that it's more complex than this rule, some synapses followed it, some did the opposite, etc.
He told me years ago that the majority in Iran were not aligned with the new regime, it was a minority of the population that were.
I always use the calculator.
But, because the numbers that get returned aren't always the right numbers, I try to approximate the answer in my head or with paper and pencil to kind of make sure it's in the ball park.
Also, sometimes it returns digits that don't actually exist, and it's pretty insistent that the digit is correct. If I catch it early I just re-run the equation but there is a special button where I can tell it that it used a digit that does not actually exist.
Sometimes, for complex ones, it tells me it's trying to calculate and provides some details about how it's going about it and keeps going and going and going, for those ones I just reboot the calculator.
It was a pretty healthy business, not just for the copy protection breaking but also the general tools software.
Funny story:
I was at their offices working on a project when they were getting ready to ship out the new version. Their warehouse was connected to the office building and they were producing all of the final copies and loading them on trucks to get sent to the distributors.
In the morning they gave the all clear for the first wave of trucks to leave, then about 4 hours later someone found a bug and they had to call all of the trucks back to the warehouse, unload, re-create new clean product etc.
They did this about 3 times before that version finally made it to the distributors.
It was actually a well designed and functional system, just too many bugs.
The article seems about 5 to 10 years late.
Is that true?
I know that cells in the brain have significant variability in DNA, but not really aware of what non-neuronal and non-brain cells in general typically have.
https://dl.acm.org/doi/epdf/10.1145/800195.805951
Quote:
"Unit test:
testing, outside of thesystem, of a part of the system thatmay have less than a complete function.
Component test:
testing, inside of the system, of parts that have been successfully unit tested.
Integration test: testing of new components to ensure that the system is growing functionally; in addition, retesting of successive system builds to ensure that they do not cause re-gression in the capabilities of the system.
Regression test: testing of the system for unpredictable system failure.
Scaffolding:
coding that replaces not - yet - completed functions..."
I was taught in the 80's about this by a woman that had worked at some company that was more formal about software dev than we were at the small company I worked for.
The term "unit test" has been used since the 1960's (if not earlier).
It's not binary, it's a continuum.
With experience, it's possible to identify whether the new project or set of tasks is very similar to work done previously (possibly many times) or if it has substantial new territory with many unknowns.
The more similarity to past work, the higher the chance that reasonably accurate estimates can be created. More tasks in new territory increases unknowns and decreases estimate accuracy. Some people work in areas where new projects frequently are similar to previous projects, some people work in areas where that is not the case. I've worked in both.
Paying close attention to the patterns over the years and decades helps to improve the mapping of situation to estimate.
Requires some dynamic SQL to construct, but the beauty is that you can use the SQL engine for this solution:
select top 1 *
from (select
t1.id,t2.id,...,tn.id
,sum(t1.cost+t2.cost...+tn.cost) as total_cost
from join_options t1
cross join join_options t2
...
cross join join_options tn
group by t1.id,t2.id,...,tn.id) t0
order by
t0.total_cost
Kelly Ortberg, CEO of Boeing, is an engineer. He has a mechanical engineering degree and started his career as an engineer at Texas Instruments.
The agile manifesto has 12 principles (per the orig: "Twelve Principles of Agile Software")
Are you thinking of a different list when you say 4, or are you maybe combining some together?
My opinion is further than that. I tell my people, if you can't get a piece of software working correctly then you have not completed your job.
It is definitely an art and skill that takes guidance and practice to develop, just like designing and writing the code, but IMO it's also the minimum bar to being a complete dev.
Having said that, we do use qa and we do find stuff in qa, but they are typically the types of things that are exposed when linking systems and processes together.
I personally prefer the 5 minute gap, it's a simple and clean solution.
Agree, but that doesn't solve the problem of back to back mtgs. In some cases people have to physically move from one mtg room to another, or they need to use the restroom, etc.
Having the 5 min gap really is needed for those types of things.
Kind of. Mutation rate of our dna is "managed" by the dna/chromosomes/genes to reduce the rate in critical areas.
I used to be that person, but then someone pointed me to the Stanford Encyclopedia of Philosophy which was a real eye-opener.
Every set of arguments I read I thought "ya, exactly, that makes sense" and then I read the counters in the next few paragraphs "oh man, I hadn't thought of that, that's true also". Good stuff.
The system looks well organized and clearly built by people with knowledge of the domain(s), but traditional ERP has significantly more depth in functionality, I don't think that comparison makes sense at this point in time.
For a big project, typically it involves deploying to a fully functioning QA environment so all functionality can be tested end to end, including interactions with all other systems internal to the enterprise and external. Eventually user acceptance testing and finally user training before going live.