splittingTimes

Can it run & render openGL contexts as well?

Yes it has adapted to larger temp swings, but these other swings occurred over 10ks or 100ks of years, not 0.15k years. Life cannot adapt over the span of single or low double digit generations.

Germany is following suite with other European countries and stops free testing in October. Why?

Free testing on a massive scale and using masks felt like the fastest road to normality.

1. Protect children

Even though I am vaccinated i can still catch and transmit the Rona. That chance is even higher as i am potentially asymptomatic. Living together and having often contact with children who cannot be vaccinated makes that a huge problem. I do not want to expose the little ones to serious long term health issues.

2. Go to events / economy

In that regard, i felt safe to go to events or indoor activities where I knew everybody was tested negative. Now we can have super spreader events again. So I will avoid indoors.

3. Stop mutations

Until we have an anti viral that is effective once you are sick, the overarching goal should still be to have as few infected as possible. The more people have it, the higher the chance of further mutations. The kicker is that now when a mutation occurs in a vaccinated person it will favor a variation that properly has immune escape rendering the vaccine efforts useless.

If the government thinks it is an effective instrument to convince anti vaxxers to get a shot (which I doubt) make only them pay for tests.

If the arguments would have been that the tests themselves have become less effective to detect the Delta strain or that too many test centers are scammers, i could totally get behind a discussion. But then the solutions would be much different and not "stop free testing".

Our short sighted government has bet everything on the vaccines to be the ultimate answer to the pandemic. Watch them scramble in 7 month when a omega variant occurs that hits like a hammer and circumvents the immune response of the vaccinated.

Then we will again hear the all to familiar phrases of "who could have seen that? No one predicted that!" We get full lockdowns as there have been no further improvements in the public health departments, IT infrastructure or new concepts to make class rooms safe. In the end our children, teens and 20 somethings will suffer under the measures the most by robbing them of another year of what should have been carefree joyful youth.

Anybody interested in open source intelligence, I can wholeheartedly recommend "Open-Source Everything Manifesto" [1]. Do not be mislead by the title. Open-source here is all-encompassing, not only software.

===

[1] https://www.amazon.de/-/en/Robert-David-Steele/dp/1583944435

So that means at 0.95c i would see stuff that is in periphery below or beside me, in the frontal of my vision? Is at 0.995c then every in front of me?

But my friends roughly know my living standard... so coming up with an excuse that is most probably a lie will not be met more favorably I would assume.

When I had more time (before having kids) i would print out a couple of articles every other day to read while commuting with public transport or during the evening. I became a bit obsessed with the optimal usage of paper space per article. So I wrote a HTML-to-LaTex converter as a golang learning project and applied the scientific paper style to the articles. I was quite happy with the results. Some HN classics can be found here:

https://github.com/frankMilde/interesting-reads

Maybe the data retention policy of OP is the real problem. Sound like a data hoarder/virtual messy to me.

When ever I take pictures on a trip or vacation, i go through them at the end of each day, delete most of them and keep maybe 2 or 3 max, beautify them and the rest goes into the bin. No matter how long the trip, i try to only keep at max the 15 best Pictures. All filler no killer. That way I am comfortable to show others pictures of a trip without boring them and I also like to look at them from time to time as I know those are the best moments.

At the end of each year we create a calendar with photo collages of 4 to 6 pictures per month. The calendar goes to relatives and we create a photo book from the print outs. That is what gets archived.

This is the precursor of how to talk to and configure a holodeck program.

"All the CO2 that is produced by burning one liter of oil can be sequestered by less than one liter of olivine." [1].

Given that formulation I assume that the amount of olivine needed is the same order of magnitude as the 1 liter of oil to produce the CO2.

The world is consuming 97 Mio barrels of oil per day [2]. I doubt we can mine that amount of olivine on a daily basis. Is it even available in that quantity?

How is olivine considered an adequate option to reduce the CO2 in the atmosphere?

===

[1] that Wikipedia article above.

[2] https://www.worldometers.info/oil/

Coming from C/C++ and Having worked for 5 years within the java world now, i must admit that the naming "conventions" and variable abbreviation in c code or more specifically Linux kernel code form a high entry barrier for me. Why is it so hard to write things out? We all look up to the various Linux philosophies (keep it simple, do one thing, etc), but to me it feels that this kind of code style is not written with a human reader in mind, but comes from the programmer perspective of "what is the shortest way and type as few characters as possible."

This kind of overhead seems so unnecessary and alienating.

This statement is odd given the fact that the US (and China for that matter) are gobbling up all the European lumber as it is cheaper than in the states, leading to ridiculous price increases over here.

Even earlier discussion, also with Link to posters in discussion

https://news.ycombinator.com/item?id=23448398

As a team lead I would not except this kind of toxic gate keeper mentality. A single person with such a bus factor is a huge problem to a teams/projects (or God forbid departments) success. Discuss and frame it in terms of worries for business continuity with your line manager. If that does not click, consider it a red flag.

I feel you. A blocker I found is that typically everybody is down in the trenches of the actual project work coding, reviewing, analysing bugs, helping support. Therr is already something more urgent to do.

You need buy-in from your team lead/line manager and a critical number of team members that actually want to make a cultural shift, but for some reason cannot. Your regular team retrospectives are the place to address this and come up with an action plan how to bake it into teams processes.

One of the possible solutions is to block time in the teams calendar for dedicated "learning". That could be regular "developer forums" or "reading clubs" or what ever.

If a document is required to be read before a meeting, schedule 10min in the beginning of the meeting where all collectively read the doc.

Not sure which language you use, but At least in java you can embed images into the javadoc comment and they get rendered by the IDE when you hover over a method or class. Comes in handy when you need to describe Boolean mesh operations for example.

Wholeheartedly agree. On our side we are not only multiple dev teams working tightly together on the same product (CAD application in a highly regulated medical field), but we also have a domain experts group, a designer group and the POs that need to prepare the high-level user stories and behavior of the features pre development. Our teams work with 3 week sprints and we found that in order to actually start development of a topic we need ~3SL prep time, meaning POs write high-level user stories, domain experts discuss how the detailed workflow behavior should best be like, then the designers come with mockups. Those are typically not aligned and need several feedback loops until it is settled. Then we devs need to break this down, look into the technical side, groom the tickets, write Dev stories and estimate them. Then the PO prioritizes the tickets and we pick em for the sprint. Then we develop for typically 3 sprints, but sometimes longer. After the pure development come the feedback loops again with the domain experts and the actual stakeholders. This can also take 2-3SL easily. So we have

3SL prep | actual implementation ≥ 3SL | 3SL feedback loops & polish

Post development our deliveries also have to synch with the bi-yearly sales windows of our parent company and need coordination for marketing, regulatory affairs / verification & validation, training & education and the sales team.

The real challenge is to somehow interface our agile development process within a traditional workflow (marketing, T&E, sales needs to know upfront what features will be delivered at a given release some month in advance so they can plan and prepare their activities and materials for a commercially successful software release.

Is there any example in recent history, where a failed state managed to turn around and improve/start functioning properly?

And if yes, how did they do it?

Good point. In that regard, i think the cartels have also latched on to the oil trade.

IIRC, when sheet melts, it will release a huge amount of fresh water into the salty Atlantic gulf stream and shut it down. The convection from top warm water sinking into the depth because of a salt concentration gradient will stop functioning.

Besides it's climate impact and heat transfer mechanism it will likely disturb the other ocean currents that are import for a stable climate as well.

This. I never understood The attractiveness of working for Facebook, Twitter, Netflix, etc. other then money. How is the Dev work there helping society at large?

Once, I got approached for a job at Amazon to help "build the next big e-billing system"... What an uninspiring thing to do.

I thought many people with mild symptoms got long covid, too.

Vaccines help to reduce risk of hospitalisation and death, But are there studies that show that vaccination prevents long covid, too?

Simple Diagrams is great for this. Can vouche for it.

===

https://www.simplediagrams.com/

Mental model often formed much more around what kind of data flows and interactions happen between components.

As a big fan of Domain Driven Design I found "domain storytelling" a useful technique when adapted to software systems.

With these diagrams it was much easier to convey complex systems and their temporal couplings. Especially to higher Management as they can actually "read" how the sequence of events flow.

Try it out and see if it can be another tool on your belt.

===

https://domainstorytelling.org

apropos undocumented:

Can I limit HNs search functionality to only include my favorites?

I often know I favoured something but for the life of me cannot find it via normal search and going through my hundreds of favorites by hand is impractical.

In Germany you have laws to ensure equal treatment in the workplace. So you are allowed to go to your HR and ask what up to i think 6 other people in a similar position & experience level as you are in earn. HR will of course not disclose the names.

Is my understanding correct, that this is not for 3D view of single models (like in CAD applications), but rather geared towards landscape views with high view angles >90° (in games most notably)?

Totally agree on Manager Tools. Great stuff.

The best book on the topic for me was peopleware [1].

Radical candor [2] was something I started but only got to the first 50 pages. Was also good.

===

[1] https://www.amazon.de/Peopleware-Productive-Projects-Teams-3...

[2] https://www.amazon.de/-/en/Kim-Scott/dp/1529038340/ref=mp_s_...

Over the years our team has gotten good at grooming and splitting up tickets, at estimating individual tickets and keeping a steady Sprint velocity.

Each 3 week Sprint we deliver what the team commits itself to.

However on a macro level we fail spectacularly. Initial Roadmap estimation of how long new features take are way off. A new feature should be ready in 3 sprints.. make that 6. This milestone should be reached in 2 sprints.. Make that 4.

It often comes down to hidden requirements that are discovered midway or prototypes that get into feedback loops with stake holders and take much longer then expected. Compared to those problems, we Rather seldomly we hit unexpected technical problems that prolong a project (but of course this happens too)