![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/f3a4dd5f-1257-47c8-825a-03a4ebceace3.webp)
2·
11 months agoEverything you code is disposable. Get at peace with that fact and you will be happy. It was crappy code anyway.
Everything you code is disposable. Get at peace with that fact and you will be happy. It was crappy code anyway.
Yes the problem is that they are management. You can say they are shitty managers all you want, but the only result you’ll get is that they will fire you.
The thing I dislike about Atlassian is everything from Atlassian
It would be even nicer if we could click on a pixel and see the computations screenshot, so we can find the error.
Goodbye Bram, teach angels how to quit vim.
I disagree.
I worked with a software for quantum physics and electronic transport from microscale to mesoscale. It had a “python based” DSL that had support for units through that module. Seems the perfect scenario for such entity, so we wrote it integrating another similar package (it’s not the units package, I can’t find it anymore. In any case, it let you say things like speed = 3 * meters / second)
The results were… interesting.
There are many major problems:
So, it looks cool, but in practice it’s pointless. The only practice to follow is:
In other words:
user gives stuff in micrometers -> store it in length_um -> convert it in nanometers -> store it in length -> use length from now on (implicitly in nanometers)
The reverse for output