Not sure the thrust of your comment, but what is really going on is just novelty seeking to get a bit of a dopamine rush, which slides into creativity.
It all comes down to dopamine at the end of the day.
I’ve been formalizing behaviors to requirements and building more end to end tests to verify them. In reality, every requirement needs a verification element. Secondly, building traceability in your unit/integration tests helps “keep it honest” about how much it has built and verified.
Mostly I’m borrowing heavily from model based systems engineering and adapting it to some form of constitutional spec driven development.
My impression is that many of the indian engineering schools are some form of trade school and it shows. A lot of people are very good at churning out things, but they vastly prefer to use well defined tools for their trade and do a lot of work impassionately. Taking the creative path or even reflecting on failures isn’t natural.
On the other side of things, you have PhDs coming out of the US with too many ideas and the inability to deal with basics such as sprint planning and CI/CD.
Not sure if this will help, but I would love it for the Colleges of Sciences peoples instead of a postdoc.
Yeah you could go with just Number though, and then keep almost everything a BigInteger/BigDecimal under the covers (or dynamically choose
the correct class)
You could, but it would be significantly worse. Number and JsonNumber are nearly equivalent in this context, except that JsonNumber has the major advantage of being in the same sealed hierarchy as the other JSON types, allowing for nice pattern-matching (and BigDecimal suffers from the same downside). So you gain nothing - you have to convert to the desired type anyway - and lose quite a bit.
Completely serious. Sea water cooling for data centers is already in use here in Helsinki. And water temperature in the Gulf of America doesn't seem to go above 30 C even in the summer.
Sea water would have to be piped to places like Dallas, whereas much of Finland's people/data centers are closer to the shoreline. A solution that works in certain places does not generally work everywhere.
There's no need to build them in Dallas. Just keep them near the shoreline. The only reason you have so many data centers in North Jersey is so high frequency traders can make their calls 0.02ms before their competitors on the NYSE. For an average user, the 1ms ping between Dallas and Corpus Christi is not a problem.
We have a home in Houston. Over by the big gates down Sunset.
I have no particular objection to building datacenters there.
All that said, I think you're being real hand-wave-y here. The climate in Houston is materially different than it is in Dallas. So there's likely a reason these companies have been locating their enormously expensive assets where they have been locating them.
Houston floods. Often.
Houston gets hit by Hurricanes.
Houston is hot and humid with relatively high ground water tables.
Don't even get me started on the power and the durability issues arising from the use of sea water.
There's a lot to work out there. You put what you can afford to lose in Houston, but you don't bet the farm on coastal Texas. You just can't do that if you want resilient infrastructure.
I built a 40 (later 80) node cluster with clusterknoppix ~2006 to run a bunch of physics simulations off of old library computers after I replaced a bunch of PSU fans. Kept my cubicle toasty until we moved them into a random subterranean room I think was used for some early nuclear research at university.
It all comes down to dopamine at the end of the day.
reply