ramino | 10 months ago | on: Gentle – The Kind Mental Health AI
ramino's comments
ramino | 2 years ago | on: The biggest losers: Metabolic damage or constrained energy?
Same experience here.
I‘m also vegan, but I would say cutting back on sugar and highly processed wheat products helped me the most to stay at a healthy weight.
ramino | 2 years ago | on: C# is programming language of the year 2023
They are not too three. They are the three languages with the biggest uptick.
ramino | 2 years ago | on: Copy Tweet as Markdown Chrome Extension
For the ones who love Twitter and Markdown as much as I do
ramino | 2 years ago | on: NuShell: A New Type of Shell
Definitely like the others can’t say it enough. It is a great shell. Having proper data structures in your shell is such a big win.
While using it I feel like working with a db like model. Also using bash commands works great and you learn to improve your parsing skills for free!
ramino | 3 years ago | on: A Rust match made in hell
Which controversy?
ramino | 4 years ago | on: Thoughts.page: hosting a small webpage for your thoughts
> i can appreciate the self loathing of someone who says they work on "merkle trees" instead of blockchain tbh
> like, yeah bro we all get what you're saying but i'm glad you at least realize you should be ashamed of it [1]
Thank god thoughts like these can finally be shared in a better way… cute project but by someone who apparently doesn’t appreciate what other people work on.
ramino | 5 years ago | on: Deno v1.8 – support for WebGPU, private modules, Intl, and much more
what do they mean with private modules?
ramino | 5 years ago | on: The Framework Laptop
Finally! I hope this company will be insanely successful. We need more companies like this focusing on repairability.
ramino | 5 years ago | on: On navigating a large codebase
The article describes pretty much what I’m facing at my job. We have a monolithic Ruby on Rails application with lines of code in the millions.
Still we general mantra is that comments are not allowed and I can only agree with the author that this makes non standard parts of the code extremely hard to comprehend. I would definitely love to work once on an application that size with a few comments here and there.
In my day to day work I depend a lot on our test suite. If I can’t even find the tests that cover this part of the code I just break the code on my branch and let the CI tell me which tests fail. There are probably better ways to do this with test coverage tools but this method seems fairly straight forward to me.
Documentation is something we started to do recently. I feel as long as the documentation is not directly connected with the code it is hard to keep it in sync. We even have PR templates that mention to update the documentation but the shape of the documentation is just too different from the code to have a straight forward Intuition at which point it needs to be updated. What happens for us is mostly that the feature owner at some point realizes that the documentation pages are not accurate at all anymore and rewrites them.
Sadly our commit messages are 50% of the time useless so that they serve more to know who to talk to than to understand why the change was done. PRs and commit messages are great documentation I wish we would use them more. In my company the idea is more that the change should be so small that no explanation is needed but I feel this idea misses the point that code can’t explain *why* something was done.
This is definitely an area for further improvements. Are there best practices someone could point me to?
ramino | 5 years ago | on: Your Language Sucks, It Doesn’t Matter
I wonder where Kotlin would fall in this case. It offers a lot of compile targets and it has some authority over Android (but Dart is getting more popular by the minute/ Java is shrinking only slowly). Will it be the Android language or the next cross platform language?
ramino | 5 years ago | on: Ghost.org deleted my website
I can’t understand the CEO’s decision. This is valuable feedback on their practices. Yes the customer is angry but that should be okay! Imagine if professionals in other areas would behave the same (like doctors for example)... Behavior like this will lead to customers being scared to criticize Ghost. This is the opposite of what the team at Ghost should want.
Someone should not be regarded as a bad customer for complaining once. A bad customer should be defined as someone who over a longer time frame costs resources. And also only after talking to them and not being able to find common ground.
page 1
I need to talk things through all the time and get easily confused and this technology is amazing at enabling that.
Looking for early testers to work together with!