jim

joined 1 year ago
[–] jim 9 points 3 weeks ago

This is a classic piece, and I love the contradictions in the text. It encapsulates my feelings on good software and code that it almost becomes an art than a science.

[–] jim 3 points 1 month ago

What a wild ride! Can't believe it's been ten years.

[–] jim 7 points 1 month ago

PSA for Debian Testing users: read the wiki

https://wiki.debian.org/DebianTesting

Control-F security returns 18 results. This is well known and there's even instructions on how to get faster updates in testing if you want.

[–] jim 7 points 1 month ago

My thought was that a lawsuit is more expensive than arbitration, but settling a class action lawsuit is cheaper than thousands of arbitrations.

[–] jim 2 points 2 months ago

Took me a sec.

[–] jim 2 points 2 months ago

Thanks for sharing. We use all pytest-style tests using pytest fixtures. I'll keep my eyes open for memory issues when we test upgrading to python 3.12+.

Very helpful info!

[–] jim 2 points 2 months ago (2 children)

I'm most excited about the new REPL. I'm going to push for 3.13 upgrade as soon as we can (hipefully early next year). I've messed around with rc1 and the REPL is great.

Do you know why pytest was taking up so much RAM? We are also on 3.11 and I'm probably going to wait until 3.13 is useable for us.

[–] jim 2 points 2 months ago (1 children)

EOL for 3.8 is coming up in a few short weeks!

[–] jim 2 points 2 months ago

So cool!! Mercury is definitely the most mysterious inner planet due to its difficulty to get a space probe there even though it's the closest planet.

The spacecraft will arrive next year, and I can't wait for all the Science it will uncover!

[–] jim 6 points 2 months ago

Haha, I've been waiting for the 4K/8K reference in this volume. Poor Anna.

[–] jim 6 points 2 months ago

TIL this exists

[–] jim 18 points 2 months ago

The complainant suggested other manga to replace the series such as Chainsaw Man, To Your Eternity, and The Seven Deadly Sins among others.

lol

 

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.

 
 

One of the coolest projects I've seen: a lisp that is embedded into Python. Hy compiles to Python AST so it's (almost) fully interoperable with Python (some notes about it here).

 

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.

5
submitted 1 year ago* (last edited 1 year ago) by jim to c/meta
 

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 @[email protected] I appreciate all your hard work over the years.

28
submitted 1 year ago by jim to c/python
 

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?

view more: next ›