jim

Here's a hypothetical scenario at a company: We have 2 repos that builds and deploys code as tools and libraries for other apps at the company. Let's call this lib1 and lib2.

There's a third repo, let's call it app, that is application code that depends on lib1 and lib2.

The hard part right now is keeping track of which version of lib1 and lib2 are packaged for app at any point in time.

I'd like to know at a glance, say 1 month ago, what versions of app is deployed and what version of lib1 and lib2 they were using. Ideally, I'm looking for a software solution that would be agnostic to any CI/CD build system, and doubly ideally, an open source one. Maybe a simple web service you call with some metadata, and it displays it in a nice UI.

Right now, we accomplish this by looking at logs, git commit history, and stick things together. I know I can build a custom solution pretty easily, but I'm looking for something more out-of-the-box.

Trying to make web applications federated is a popular effort. Examples include things like the “fediverse”, as well as various other efforts, like attempts to make distributed software forges, and so on. However, all of these efforts suffer from a problem which is fundamental in building federated applications built on top of the web platform.

The problem is fundamentally this: when building an application on top of the web platform, an HTTP URL inherently couples an application and a resource.

So it's been about a week since I turned on the discussion bot, /u/mahoro@lemmy.ml (Mahoro-chan). This bot is a (lazy) fork off of AutoShonenpon, in which I hacked in a connection to Lemmy instead of Reddit.

Anyway, I'd like to get some feedback from the community.

• Any bugs? Missing titles? Titles I should remove?
• What do you think about the frequency of posts?
• Feature requests?
• Any other feedback?

(side note: since yesterday, federation has been painfully slow from my instance so it might take me a while to respond to messages)

The sidebar for our instance has a broken link for programming.dev - it links to https://programming.dev/programming.dev

It was a great app! Been a user for as long as I remember using reddit on my phone.

Thanks @talklittle@lemmy.world I appreciate all your hard work over the years.

A series that I recently adore even though it's an overused okaku+gyaru trope.

Thanks to the TL!

I generally don't like "listicles", especially ones that try to make you feel bad by suggesting that you "need" these skills as a senior engineer.

However, I do find this list valuable because it serves as a self-reflection tool.

Here are some areas I am pretty weak in:

• How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
• How to convince management that they need to invest in a non-trivial technical project
• How to repeat yourself enough that people start to listen

Anything here resonate with y'all?