jdmichal

I've used many different version control systems. Git is, by far, the best at merging and avoiding conflicts to start with. I believe it's because it can often work from the basis of a common ancestor commit, so it's able to perform three-way merges instead of two-way merges.

I feel like you're not allowed to make up phrases like "E-Mail-Caste", not explain what it means, then get mad when others don't perfectly understand it...

Up until a couple years ago, I used to do my taxes myself. I would just open Excel and start doing one line at a time. The value that goes on the form was the left-most column, and cells to the right of that would be for additional values and calculations. Worksheets and schedules became additional sheets within the workbook. Any change to a value would automatically propagate through the entire thing.

TFA gives this number as ~1.5GW per year -- I believe calculated by the JPL proposal.

The MY2022 Maverick is what the new Ranger should have been. And the Hyundai Santa Cruz also was introduced in MY2022. Finally some steps in the right direction, at least.

"Take a break while you get ready for the next exercise:"

The best response I've heard to this is: Tell me which part of the US you would willingly give up to Russia if it threatened to attack. If your response would be for them to pound sand, why should we expect or want any different for the Ukraine?

I for one definitely go grab the shotgun everytime I hear that "the situation is rapidly evolving" on the news. Someone has to be ready to defend against all those mutants. /s

Last I heard, there's an idea that it might help recolonize the gut with good flora after infections and such.

This is why I call ChatGPT a mirror. And it's a really damn good mirror. But even the best mirror can only reflect that which already exists.

> I can see us relying far more on centralized institutions (again).

Yes. In an age of abundant junk, curation of the gems can be a successful strategy.

> AI will dig a huge gap which does not yet exist between the best and the worst products (articles, code, whatever your product is).

Google results and app stores are already filled with low-effort trash. If this gets worse, then the importance of "influencers"[1] as curators of the trash pile rise even more.

[1] Or YouTubers or whatever else you want to call them.

Ah I get it now. Sorry for the density.

People only have one appendix to start with. Did you mean appendage?

> It's research (as in new knowledge) and development (as in new products based on existing research and knowledge).

This is... Exactly what I said?

> And yes, a carpenter developing new cabinet designs absolutely would qualify for the R&D credit (and their salary could fall under the scope of this rule change).

I feel I pretty clearly alluded to the physical process of turning wood into a cabinet, not developing novel new techniques for doing such.

R+D is "research and development", not "research" and "development". It's specifically development of research into new products. Otherwise a carpenter could be seen as "developing" wood into cabinets. If there's no research or experimental process involved in the work, then it's not R+D.

Isn't welding just "developing" metal products?

That's why you have to take into account that it's "research and development", and not "research" and "development". As in research and the development of that research, not separately research and development.

The flipside is that that 5-year amortization continues even if you did fire everyone, right? Because the costs already happened. So if we consider forward from year 5 of your example, with everyone being fired at year 5:

Old:

Year 6: 1000K profit

Year 7: 1000K profit

Year 8: 1000K profit

Year 9: 1000K profit

Year 10: 1000K profit

New:

Year 6: 200K profit (End of year 1 amortization)

Year 7: 400K profit (End of year 2 amortization)

Year 8: 600K profit (End of year 3 amortization)

Year 9: 800K profit (End of year 4 amortization)

Year 10: 1000K profit (End of year 5 amortization)

Of course this "wind-down" period is unhelpful if you're actually shuttering the business...

To be fair to you, I certainly read that but didn't associate that letter to the comment until mikeyouse pointed it out. A lot happened between reading the article and reading that comment.

In "research and development", that typically means "research of new ideas and methods, and developing them into commercially viable products". So are there things that software engineers do that fall under R+D? Absolutely! Is adding a sorting feature to a grid in your app one of those things? Probably not!

In addition to other replies, in hot and humid climates, you still want the A/C running for de-humidification purposes. So you set it high instead of turning it off completely.

I always wondered why "electric with an onboard generator" didn't take off as a subset of available vehicles. AFAIK, hybrids all work with complex gear boxes to allow the engine to directly power the wheels, while also charging the batteries.

I suspect the answer is because it's more efficient from a MPG perspective to allow the engine to directly power the wheels, at the cost of the extra complexity of gearing. Converting motion to electricity back to motion is lossy, and even more so if you insert battery storage as an additional step.

The Bitwarden client does this. The issue is that nothing prevents the attacker from taking the encrypted database and working with it directly, thereby bypassing that client protection.

I agree with runako. I suspect that you are going to have a hard time targeting areas where heat pumps are already common for cooling.

I'm in Florida. We got our A/C replaced a few years ago. Got quotes from three companies with varying ranges and the one we chose knocked it out in a (long) day. Including various "side-jobs" such as running a new electric line with a larger gauge, installing a hurricane pad, removing the loopback with the water heater, and lifting the air handler into the attic.

Total cost was under $8k. None of the quotes, including for name-brand units, were above $12k. $18k for an unknown name seems just right out to me.

The New Mexico Rail Runner is 96.5 miles, 74.2 of which was preexisting BNSF track which is still shared with freight and also I believe the Amtrak Southwest Chief. There are some other segments that are also preexisting track, but they are much smaller and some was improved as part of the project so I won't even try to figure out what proportion was what there.

So strictly less than 22.3 miles of new track. For $385 million.

> It's unquestionable that iPod unleashed the explosive miniaturization of technology, and paved the road for everything that we saw in the following decade with smartphones.

PDAs were being developed at the same time as the iPod and probably have a much better parental claim than the iPod. The first smartphones -- the ones before the iPhone -- were basically PDAs with cellular modems, and utilized the similar OSes as their non-modem-bearing predecessors.

https://en.wikipedia.org/wiki/Personal_digital_assistant

I had an HTC Wizard, specifically the Cingular 8100, which came out two years before the first iPhone.

https://en.wikipedia.org/wiki/HTC_Wizard

The iTunes being discussed here was not a streaming platform. It was a library management platform (2001) that also offered purchase and download of FairPlay DRM-laden music files (2003). Later it would offer DRM-free MP3 download for select music (2007) and eventually its entire catalog (2009).

Are there MOND theories that attempt to account for dark energy too? Or only dark matter?

If sparring incites images of violence for you, I suspect you don't really understand what sparring is. It's specifically practice without the violence -- extra rules are put into place to ideally eliminate injury, though of course accidents do happen.

If you use domain-driven design, then microservices boundaries can be naturally drawn at domain boundaries and that will tend to work out pretty well. They should be as big as they need to be to support the domain.

I've definitely seen systems where the general gist was a microservice per data type, without any consideration of how those data types and the overarching domain were organized. And it turned out pretty terrible -- UI calls that were very coherent from a domain perspective blowing up into a chain of 3 or 4 calls to other services to get all the required data.

In reality, there was a primary data type with a few different types of supporting data. So a single microservice serving that primary data type along with the supporting data would have been quite appropriate.