Kache

@Kache@lemmy.zip

• ⁨Comment⁩ on ⁨The Fate of Data Model Dependency⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Yeah, this should be common software engineering problem for a senior engineer

  In the beginning, there is only one data model used both externally and internally, to keep things simple. Now that they’re diverging, it’s time to draw an abstraction boundary that translates between internal and external models.

  I’m not super strong with Java, but subclassing to handle v1/v2/vX doesn’t sound like the right thing to do. I’d detach the old model from the API while otherwise keeping it unchanged, implement a new pathway to connect with the new API, then translate in/out of the old model before it passes into the existing system. This way, the surface area of change and of integration is isolated and decoupled from everything else.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Efficiency of living is not static, I wouldn’t be surprised if it were possible to sustainably support 10B people with a relatively high standard of living.

  I heard the following metric recently:

  But in China, in 2013, China had terrible particulate air pollution. It was known around the world as the airpocalypse (ph) on a - a 700 on a scale of air pollution from zero to 500, the U.S. embassy reported. And, you know, over the decade after 2013, the size of the Chinese population grew by 50 million people. And so if more people were always worse for the environment, you might think that particle air pollution in China would have gotten worse. But, in fact, particle air pollution in China fell by half, even while the population grew.