splittingTimes

That approach assumes to know the relation of X and Y in advance, meaning you have a curated, up-to-date list of your tech debt or even better: a map of techdebt-to-feature.

However, working with legacy, you often find techdebt or inadequate architecture/infrastructure mid project...

IIRC, Dengue has 4 different strains. When you get reinfected with the same strain, then you are good. Getting one of the other strains is the problematic case.

I think you need a more encompassing approach. Permaculture might be something for you. They have developed specialized techniques for all climate zones.

For example check out the "Greening the desert" project.

https://youtu.be/2xcZS7arcgk

This is a classical quantum mechanics text book write up. Nicely done with a pleasant layout. However, I never really saw the benefit of the Bloch sphere. It never provided a deeper physical insight for me that was not seen from the equations.

I too got exposed to him via the Venus project and Robert Steele's "open source everything manifesto"[1]. Having read Jacque Fresco [2] and found it clear and easy to follow, I tried to read Bucky's book "ideas and integrities" [3], but his almost stream-of-conciousness kind of writing style is so opaque and non approachable (to me at least) that I had to give up.

Can you recommend anything from him that is more readable?

===

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

[2] https://www.amazon.de/Best-That-Money-Cant-Buy-ebook/dp/B077...

[3] https://www.amazon.de/dp/B004WH04LM/

In your experience, What's the best tool to check 3-way merge diffs under windows?

Do you guys have some more enlightening resources? Thanks.

You can download the posters here: https://www.roche.com/sustainability/philanthropy/science_ed...

> diatoms produce quarter to half of the oxygen on earth

Hmmm so plankton is 50-85% and diatoms are 25-50%? So how much are plants adding?

Never anything official. It was just how it was done in the group and wider scientific community. Some googling pulled that up if it helps

https://books.google.de/books?id=uzJbyD6_3DAC&pg=PA4

And yes you have to be consistent and stay in that unit system. The other remaining two we used plain Kelvin for temperature and for the charge Coulomb was measures in electron charge. That's it.

That's why when I did numerical simulation of electron Dynamics in semiconductors during my phD we never used straight SI units (m, s, kg, etc), but instead expressed all physical natural constants in nm, fs, eV, etc. That way all relevant constants had numerical values between 1 and 10 which stabilized the simulations a lot.

For the interested, here is an overview into neural forecasting from the folks at Amazon research:

Neural forecasting: Introduction and literature overview

https://arxiv.org/pdf/2004.10240.pdf

Could i use commercial UV-lights (like for tanning or medicinal appliance) and illuminate the items to kill off the virus?

That means any items you buy in a supermarket (greens wrapped in plastic, toilet paper, packaged meet, tin cans) should be set aside at home for 3 days? And you need to disinfect yourself after each round to the store...

We use three fields to triage a bug. When the bug is create the PO/support team/Dev tries to the best of his knowledge to assess:

1. Severity - roughly defined as in the article

2. Occurrence - How probable will this bug happen in the field? How many users would be impacted? How much support will be needed for this issue? Low - Only some very special workflows or mainly dev work impacted. Medium - Some regular users. High - Many regular users.

3. Reproducibility - How often will the bug occur when we follow the steps. Low - Single occurrence or difficult to reproduce Medium - Erratic behavior, thread problems High - It will almost always happen.

Then a PO can set a prio and give the ticket the status "will not fix" or "to be analyzed". The dev team then takes the bug and does a time boxed (1 day max) first analysis and comes back with an effort estimate of how big the issue it's too fix. Then a PO can reprioritize and set the status to "to be fixed" or not.

Since there are some papers posted in the replies here, do you guys have any recommendantions on what are some journals that should be read by people working in the field of 3D graphics and CAD/CAM software development to stay ahead of the curve?

How did it work out practice? After each Sprint the numbers got revealed?

Did that not lead to a super competitive workplace? I cannot imagine that this was very motivating to the remaining 990 devs... Or was it?

How is this worse than your normal influenza cycle with 3-5Mio infections and 290k-650k death to warrant such an emergency?

So TomTom lost Apple as a customer?

In addition to those described in the article, i have following question on my list:

# Risk

* What are the platform constraints?

* What are the performance constraints?

* Get clarity to what is an acceptable upper bound.

* Would it be acceptable if it took a week to calculate or 20 minutes to open the application?

* Does it need to happen in 30 seconds or 5 milliseconds or 100 microseconds?

* Can you demonstrate a failure?

* What happens when you go off script?

* Most of the complexity is in handling those off-script behaviors. If that’s not being handled well, the project is definitely not “nearly done”.

# Definition of done

* How does the “Definition of Done” look like? Ideally from whole project down to single stories.

* How would you verify that this is working correctly?

* What is the success criteria of this product?

* What does “good” look like?

* What will make it a worthwhile endeavor?

* What are other pain points and blockers?

# Costs

## Opportunity costs

* Is this the most valuable thing we can be doing?

* Is an 80% solution good enough for your needs?

* Is this work really where your team can add unique value?

Other question one might ask to get a feel for the lost opportunities:

* Which parts of the current system are hard to use?

* Which manual process stops the customer to do more creative, value-adding work?

* What changes would improve operational inefficiencies and save money from the bottom line?

* What evidence can you show that this will solve the problem?

* Provide a simulation or prototype or fake (but statistically relevant) data which can demonstrate the solution is at least plausible.

## What connects to this?

* Things with a more complex network of dependencies will be more costly to develop and maintain.

* What systems will depend on this?

* What systems will this depend on? Enumerate all the dependencies. Other systems, libraries, users, protocols, everything

## What’s Plan B if this doesn’t work?

* What are you going to do when we’re up against a deadline, this solution isn’t working as expected, everything is broken, and we still have to ship?

* Get an answer to that, then do that first. Then you can talk about how you can make it better.

* What would be the earliest point you can know whether the system has any value to you? What is the smallest step that would give us the most benefit? How will we do this?

* If we could keep only half the features what would they be?

* What if we take one dev away from this project?

* The 80/50 Rule:

If you’re not 80% done by the time you’ve used 50% of your resources, you are behind. When something doesn’t pass this test, it’s time to evaluate what needs to change:

* Does this project need to stop?

* Do other projects need to move? “I can make up the time” is not a realistic response.

# Maintenance cost

* How long will the system survive?

* When will this system be scheduled for replacement?

* During what period will you be making no changes to the system except for critical bug fixes?

* What are the prerequisites for using the solution?

* What must continue to be true?

* What do users need to know?

* What does the data need to look like?

Just in case you want a nice pdf printout read.

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

Looks like a Miro (former realtime board) clone to me. What is the differentiator?

I am wondering if these effects are really important and warrant the use of "AI". If so, then what is the size of the target? If it is only some cm^2, then they still have a long way to go till it can handle industrial sized problems. Once you are at industrial scale, do you still need that kind of accuracy??

"Heliogen uses computer vision software, automatic edge detection and other sophisticated technology to train a field of mirrors to reflect solar beams to one single spot."

In principle I think you are right, but that would mean for each plant you build you need the exact position of each mirror, the oven chamber and the motion of the sun through the day and year. I think the "AI" approach scales better, as it is rather simple "AI" application.

Will we ever get to see golang-style multiple return values/results?

"Manager tools" and "career tools" podcasts have been eye-openers for me about corporate relationships and management politics.

+100 for peopleware.

From another thread I saw the recommendation for "Getting to Yes, and... The art of business improv"[1]. It just arrived yesterday. This blog post looks eerily similar.

===

[1] https://www.amazon.com/-/de/dp/0804795800/ref=mp_s_a_1_8?key...

I only know some of Blows talks. Is there any written advise from him?