HN user

shime

172 karma

https://shime.sh

Posts50
Comments75
View on HN
stanko.io 1y ago

Clean Air and AI

shime
1pts0
stanko.io 1y ago

Building Simpl息

shime
3pts0
essays.shime.sh 1y ago

The Kettlebell as Teacher

shime
1pts0
hrvojesimic.substack.com 4y ago

On thinking about the worst that could happen

shime
2pts0
shime.sh 5y ago

Beware of Programming Puzzles

shime
3pts0
shime.sh 6y ago

Lessons from my third failed startup

shime
1pts2
dashdash.io 6y ago

Linux Man Pages – Dash Dash

shime
1pts0
shime.sh 6y ago

I Love Jekyll and GitHub Pages

shime
2pts0
shime.sh 6y ago

Achieving balance between reading and writing

shime
3pts0
shime.sh 8y ago

Git commit message syntax highlighting in Vim

shime
1pts0
shime.sh 8y ago

Freedom

shime
2pts0
github.com 8y ago

Show HN: Bun – Bundler's little helper, CLI tool to install gems to Gemfile

shime
2pts0
github.com 8y ago

Show HN: Super tiny compiler, written in Ruby, using TDD

shime
3pts1
github.com 8y ago

Awesome Open Source Indie – A curated list of small open source products

shime
72pts9
news.ycombinator.com 8y ago

What happened to Assembly – http://assemblymade.com/ – is there an alternative?

shime
1pts0
shime.sh 8y ago

Programming for money until I'm too old to

shime
1pts2
shime.sh 8y ago

Money and time

shime
2pts0
medium.com 8y ago

Building a crude Node.js from scratch

shime
3pts0
blog.twobucks.co 8y ago

Building a crude Node.js from scratch

shime
2pts0
github.com 8y ago

Learnuv – Learn libuv for fun and profit, a self guided workshop

shime
1pts0
github.com 8y ago

Node vs. Ruby I/O benchmarks for image resizing

shime
3pts0
www.codementor.io 8y ago

Use less CPU for development servers

shime
2pts0
news.ycombinator.com 8y ago

Ask HN: Would you pay for a screenshot taking app?

shime
1pts6
www.wired.com 8y ago

Turn Off Your Push Notifications. All of Them

shime
2pts1
zapsnap.io 9y ago

Show HN: Zapsnap – Temporary P2P screenshot sharing from your browser

shime
4pts2
shime.sh 9y ago

Landing that remote job

shime
4pts0
github.com 9y ago

Show HN: “hello world” over Bittorrent

shime
22pts2
tiobe.com 9y ago

Tiobe Index: Go language at all time high and in the top 10

shime
40pts65
shime.sh 9y ago

Thanks via email

shime
2pts0
shime.sh 9y ago

4 tips from 6 years of remote freelancing

shime
7pts2

For what it's worth, Roam team has just recently added end-to-end encryption option for graphs.

I'm a Roam user, although I've tried Obsidian, Bear, Zettlr and vimwiki. I keep coming back to Roam because I find thinking in blocks suits me better than thinking in documents.

I think this is the effect of various companies trying to capture as much of our attention as possible because it makes sense for their bottom line. We are all victims of recency bias, so it makes sense for companies to prioritize more recent content. If it wasn't the case, the various social media apps wouldn't be as addictive as they are.

I am not aware of a social media app feed that puts quality above recency (not counting the plugins that enable that, like Twemex [1]). Instead they keep us in what David Perell calls "Never-Ending Now" [2]. We endlessly consume temporary, short-lived content and we are mostly blind to the past.

Google search is not social media, but I wouldn't be surprised if Google ranked more recent content higher, given how they have changed the Youtube algorithm.

1: https://chrome.google.com/webstore/detail/twemex-sidebar-for...

2: https://perell.com/essay/never-ending-now/

I think the biggest problem with Medium is the fact that nothing was paywalled and then they introduced the paywall, which caused frustration. Substack, on the other hand, is much more pleasurable because there is an expectation from the start that some of the articles are going to be paywalled.

I also hate visiting Medium, but enjoy visiting Substack. They both have paywalls on some of the content, but Substack is much more enjoyable, even when you don't get to see the full article.

I think software quality is always decreasing because of multiple factors.

1) The tension between leadership that usually only prioritizes shipping new features and engineering that wants to write sustainable code. There is usually no incentive for engineering to decrease technical debt or increase sustainability, as these changes are usually not tangible to leadership. The only short-term beneficiaries of one engineer's code quality improvements are other engineers, which often don't care that much, as they are busy shipping new features as quickly as possible.

2) Speaking of short-term, not all leadership thinks long-term. Sustainable code makes sense if you're thinking long-term, but not if leadership is chasing lucrative exits in a couple of months. If a project survives for 20 years, chances are it survived multiple leadership changes, which all thought short-term.

3) In software, the only constant is change. As project gets older, it has to deal with all the changes that aging entails. Aging means increased exposure to reality and all the "surprising amount of detail"[1] it contains. This increases complexity, introduces bugs, adds edge cases to deal with, etc.

[1] http://johnsalvatier.org/blog/2017/reality-has-a-surprising-...

The only metric I currently pay attention to is the readiness score from my Oura ring.

It's interesting to see how much alcohol, eating just before sleeping or stress affects this score. And it's also nice to get the confirmation on how well I'm feeling from a tool that measures it.

Write about whatever interests you. What article would the past you like to read? Some suggestions:

- you could write a low-effort "today I learned" posts, where you would share tips and tricks about something that you've learned during your day job (e.g. https://shime.sh/til/)

- you could write a high-effort "deep dive" posts, where you would explore how a certain library works under the hood (e.g. https://shime.sh/deep-dive/)

Although deep dive posts take more effort, it's worth it, since you'll learn a lot about something just by explaining how it works.

I have a meaningful (which is subjective) part-time job and I've been mostly freelancing for the last 10 years (out of which the last 4 years I've been mostly freelancing part-time).

Although I've started with UpWork, I don't recommend it for job search anymore, because the quality of clients was low from my experience. A lot of job postings ended up being a race to the bottom with rates. I think WeWorkRemotely is a better option for search, while HN hiring threads are even better.

On autoloading 5 years ago

There are not a lot of things from JavaScript that I would love to see ported to Ruby, but ES6 imports is one of them.

People are hearing actual voices inside their heads?

Yes. It's my voice, unless it's something written by a person whose voice I'm familiar with.

Can you all hear things like music and other sounds too?

I can hear music sometimes. Especially just a moment before waking up.

I think pessimism is a professional deformation of programmers. We have to be pessimists in order to build good software. We have to think of the edge cases and everything that might go wrong with the implementation. And this pessimism spills over to personal life.

I'm not sure of the best way to fix this, as I'm working on it myself, but one of the things that helped is realizing that negative thinking comes from a voice in my head that interprets everything in a negative way. Just noticing and registering that negative voice has helped me be more positive.

1. Building a time tracker that encourages deep work [1]. It's an interesting experience and I'm fascinated by the amount of complexity that is hidden behind building a "simple" time tracker. Reminds me of "Reality has a surprising amount of detail"[2].

2. Writing more, but publishing less. In the past I've been publishing one article per week, but I've later realized that this doesn't improve my writing skills, but just builds my writing habit. These articles end up being low-quality pieces that are easily forgettable. So, now I've changed my approach and I'm investing more time into each article.

[1] https://ciklus.app/

[2] http://johnsalvatier.org/blog/2017/reality-has-a-surprising-...

Sönke Ahrens has a good point on forgetting in "How To Take Smart Notes". We view it as a negative thing, but if we remembered everything we would be drowned in details and we wouldn't be able to distinguish signal from the noise. He argues that forgetting makes us able to learn.

I'm confused why they used "unsophisticated" and "sophisticated" instead of simply linear/non-linear. It's also weird that the author suggests that everyone starts sophisticated and should become unsophisticated.

Good article otherwise. Loved the remark that we shouldn't strive for hitting the yearly quota and instead just enjoy reading.