Highly recommend reading Designing Data-Intensive Apps [1] and Monolith to Microservices [2]. I can't remember which (maybe both?) but I definitely took away the idea that if services share a DB, that DB's schema is now a public interface and becomes much more difficult to evolve with new requirements.

[1] https://www.amazon.com/Designing-Data-Intensive-Applications... [2] https://www.amazon.com/Monolith-Microservices-Evolutionary-P...

The way I think of it is that a DB should only be accessed by a single replicaset in k8s. Only processes of identical code should share the DB. Everything else is through RPC interfaces.

This is how large scale systems are built, but the pattern makes less sense the smaller your footprint is.

The old school solution to this is have different schema in your database, and have views as the cross team public interface.

Yes, OTel has autoinstrumentation libraries for some language that can pick up a fair amount by default. Though it's unlikely that that would ever be sufficient, it's a nice start.

For Java: https://opentelemetry.io/docs/instrumentation/java/automatic...

Seems like the key shared characteristic of these examples are small communities where people care about each other. As you say, it works at smaller scales. But free rider problems are a lot tougher in a community of millions or more.

I live in one of those communities (eco village in Australia) and all it takes is one old haggard lady to reduce the workforce to nothing, as no one wants to put up with her abuse.

I think one thing people keep forgetting is that all these problems have already been solved for hundreds and thousands of years. You will never reduce inequality, abuse, pain, suffering. It's much better to contribute and improve what we already have rather than to rip it out and try "yet another variation of the same utopia that we've all been thinking about".

Build towards it, not "start again "

Another way it's been said: https://en.wikipedia.org/wiki/Turning_the_other_cheek

Bad idea. It's better to turn your ass to your adversary and move away from the conflict.

I was surprised to see no mention of automation tools like IFTTT and Tasker. These sorts of overarching automation oriented tools let people solve a lot of problems by stitching together things that aren't designed to work together.

I would actually put Excel in this original category. Part of Excel's utility is that it is really good at enabling building of dashboards, applications, whatever. While Excel's builders didn't have D&D character sheets in mind, they definitely expect users to do unanticipated things with the software, just as much as IFTTT or Tasker would.

In some ways this is a "platform" type of perspective. "Here's a bunch of building blocks, go do whatever you think you need" is really powerful once the network effect of building blocks gets big enough. Any tool with a built-in DSL or workflow builder type of UI is probably in this category.

It's funny that you mention IFTTT because one of the inspirations for its creation was the book Thoughtless Acts?, which is full of photos like the ones in this post: https://ifttt.com/explore/ifttt-the-beginning

They used to give a copy to new employees, but it seems to be out of print now.

Not all companies (stocks) have the same sensitivity to inflation. Depends on all sorts of things that are business specific. One example is how easily price increases from suppliers can be passed on to customers. A company that sells a commodity into a very liquid market won't suffer as much.

At the other end of the spectrum, inflation decreases the real value of future cash flows, so tech stocks have been hammered. Here's an explanation I like: https://fullstackeconomics.com/rising-interest-rates-are-ham...

My tip on life insurance: don't buy it from your existing auto/home insurance company. In my recent experience it's far cheaper from a dedicated life insurance company. I also got a discount going through Costco.

"Executive officer" - used in the military, from what I am aware.

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

the language is more 1SG, an XO communicates via ppt

Slide 1: Leg: Anatomy and Function of Bones and Muscles, Plus Diagram

Slide 2: Establishment of ownership of leg to a soldier, attached and special conditions of detachment

Slide n: ... blasé blasé blasé

IntelliJ lets you expand links from patterns, so if in our codebase there's a BUGREPORT-12345 link, it's blue and clickable and goes to jira.

I'm happy to see more virtual offices being built!

My company internally built and then open-sourced Qube[1], which has a lot of similarities, but just integrates with Slack and Zoom. A lot less ambitious, I'd say, but we're very happy with it.

[1] https://github.com/seeq12/qube

This is really cool. It reminds me of Sococo but way more integrated with the tools out there. Any chance I could give it a try? What happens when you click the slack button in the team list? You can send a direct message to that teammate?

We used to use Sococo and got frustrated and abandoned it a couple years back, actually.

If you hit the Slack button it opens a link to that Slack chat. If you are in a room with a group it'll open a group DM to the other people present. (I personally rarely use the Slack button because any given DM or channel in Slack is only ever alt+tab and ctrl+k away, but that's just me.)

That makes sense. What was frustrating with Sococo?

They rewrote it from a native app to a web app, and it got a lot slower. Limits on the size / number of videos active. Status was not as flexible as we wanted (i.e. reminders when you forget to update, time zone conversion, etc).