![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/913b482d-9012-449f-bc87-b1f4463e7154.jpeg)
Buy a 3d printer. You’re getting cancer regardless
Buy a 3d printer. You’re getting cancer regardless
I have 1010 fingers
In my opinion, the settings file isn’t where this information should be presented. I would put these notes in the release log and readme and example settings file. I have also written this information to logging during startup so a user knows what to do, or I write a migration that does the change automatically if that’s possible.
This is only my opinion and you can use the comment method described like “//“: “Deprecated”
if desired.
For settings files I always have an example file with sensible values filled in and along with descriptive keys that serves as reasonable documentation. If something is truly unknowable, I’ve probably done something wrong.
Agreed. Except that it’s not easier to write imo
Every time I have reached for TOML I have ended up using JSON. The first reason is that Python standard library can read but not write TOML, which is generally useless for me. The second reason is TOML does not add any benefit over JSON. It’s not that much easier to read and IMO JSON is easier to write by hand because the syntax rules are completely obvious.
I’ve always pronounced it Linux. Who pronounces it another way?
OP didn’t say listening to music is pointless. Try rereading the post.
Since my phone is water resistant, I put a magnetic mount in the shower to listen to music, podcasts, and the occasional Teams meeting if I’m running late.
You’re not qualified to have an opinion on TDD — ThePrimeagen
It would be better if they share the site/ai model they’re using so people can do this for themselves. Thingiverse doesn’t need an influx of likely unprintable random models
That’s just like your opinion man
I enjoyed 3D movies and wish it became a thing. I still break out the 3D glasses for my TV every once in a while
To answer the first question, do whatever works for you, but I’d look at alternatives like Notable. It offers cross platform apps with sync using any desktop file sync service like OneDrive or iCloud.
I personally don’t see a point to using a Jupyter notebook for taking notes. You can create markdown files in Jupyter labs if I’m not mistaken, which is what I’d probably do, but I wouldn’t because I use Notable for that.
Only if the code base is well tested.
Edit: always add tests when you change code that doesn’t have tests.
I agree with your first point, but pretty strongly disagree with the other two. Code review is critical. Devs should be discussing changes and design choices. One Dev can not be all things all the time and other people have experience you do not or can remind you of things you forgot. Programming language absolutely matters when you’re not the only dev on the team.
I used to think something like this when I was younger. I spent an inordinate amount of time looking for good gui versions of cli tools. I have come to understand that this is not usually the case and cli tools are more convenient much of the time. I would not classify this as superiority complex, unless I’m being a jerk about it. I don’t care what you use, I just use whatever has the lowest barrier to entry with the most standardization, which is usually the original cli tool.
That said, jetbrains git integration is awesome.
A good thing to note is that both of those bars you mentioned have different names. That makes it easier to know which to go to, once I figure out which is which.
This brings back trauma