If you live in the U.S. I recommend you read No Sweat of the Brow Copyright: https://www.gutenberg.org/help/no_sweat_copyright.html

This is explained by the ElementaryOS H.I.G.:

> Apps should save their current state when closed so they can be reopened right to where the user left off. Typically, closing and reopening an app should be indistinguishable from the legacy concept of minimizing and unminimizing an app; that is, all elements should be saved including open documents, scroll position, undo history, etc.

> Because of the strong convention of saved state, elementary OS does not expose or optimize for legacy minimize behavior; e.g. there is no minimize button, and the Multitasking View does not distinguish minimized windows.

More: https://docs.elementary.io/hig/user-workflow/closing

These are not sapient beings that are capable of looking out for their own well-being. We've bred that out of them over hundreds of human generations.

But there's so much to the linguistics of animal husbandry and dairy that many folks don't know. It goes way deeper than just the milk-oriented terms in the article: Heifer versus cow, freshening and calving, steer versus ox versus bull, AI (not the LLM kind) versus natural service, the barn, parlor, and pasture, and more. Plus plenty of technical knowledge. If you're not hand milking, how many mmHg of negative pressure should you use? Do you use a surcingle, or a claw, or a robot?

Even in the milk-oriented terms, there are others not covered by the article. HTST and UHT aren't the only options, there's also LTLT. Pasteurization can be done in a pipeline, or in a vat. Smaller vats for home and small farm usage can be multi-purpose: I pasteurized milk and cultured yogurt in mine. Some folks even care about the specific proteins (A1 beta-casein versus A2), which is genetically determined by the cow (and can be bred for).

I got a cow in 2020 and there was a lot to learn.

Comments URL: https://news.ycombinator.com/item?id=47675792

Points: 1

# Comments: 0

(Source: https://www.bls.gov/ooh/computer-and-information-technology/...)

Computer Programmers median pay according to BLS: $98,670 per year

(Source: https://www.bls.gov/ooh/computer-and-information-technology/...)

Software developers typically do the following:

- Analyze users’ needs and then design and develop software to meet those needs Recommend software upgrades for customers’ existing programs and systems Design each piece of an application or system and plan how the pieces will work together

- Create a variety of models and diagrams showing programmers the software code needed for an application

- Ensure that a program continues to function normally through software maintenance and testing

- Document every aspect of an application or system as a reference for future maintenance and upgrades

(Source: https://www.bls.gov/ooh/computer-and-information-technology/...)

Computer programmers typically do the following:

- Write programs in a variety of computer languages, such as C++ and Java

- Update and expand existing programs

- Test programs for errors and fix the faulty lines of computer code

- Create, modify, and test code or scripts in software that simplifies development

(Source: https://www.bls.gov/ooh/computer-and-information-technology/...)

Perhaps this will finally force the pendulum to swing back towards continuous integration (the practice now aliased trunk-based development to disambiguate it from the build server). If we're really lucky, it may even swing the pendulum back to favoring working software over comprehensive documentation, but maybe that's hoping too much. :-)

Comments URL: https://news.ycombinator.com/item?id=47167357

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47095459

Points: 5

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47077299

Points: 3

# Comments: 0

My favorite was Thinking, as it tried to be helpful with a response a bit like the X/Y Problem. Pro was my second favorite: terse, while still explaining why. Fast sounded like it was about to fail, and then did a change-up explaining a legitimate reason I may walk anyways. Pro + Deep Think was a bit sarcastic, actually.

Stateful MVC uses Publisher/Subscriber (or Observer) to keep Views and Controllers up-to-date with changing Models over time, which is irrelevant for stateless MVC over HTTP. Plus, in stateful MVC the View and Controller are often "pluggable," where a given Controller+Model may use a different View for displaying the same data differently (e.g. table vs. pie chart), or a given View+Model may use a different Controller for handling events differently (e.g. mouse+keyboard vs. game controller). Whereas, in stateless MVC over HTTP, the controller is the "owner" of the process, and won't generally be replaced.

And in the world of front-end web, stateful MVC really is mostly dead. MVVM and Component-based architectures (using the Composite pattern) have replaced it. A runtime is usually responsible for wiring up events, rather than individual controllers. Controllers don't need to be swappable because events can be given semantic meaning in components, and Views don't need to be swappable because you can instead render a sub-composite to change how the data is shown.