Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Hamatti
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
Hamatti
1y ago
One time, when I had just started on a legacy project and was struggling to understand how things worked and where the bug was, I printed out many many pages of the code, booked a meeting room for the day, taped the code printouts to the wa
2.
▲
by
Hamatti
1y ago
OP here! That's a wonderful question, sorry it took me over a week to notice it and reply. A lot of the practical debugging happens with debugging tools on the computer but every now and then I run into issues where it's not obvio
3.
▲
by
Hamatti
1y ago
> using a notebook is antiquated and we have better tools. So far, I haven't found tools that beat pen and paper as tools for thinking _for me_. I still do write a lot of digital notes too but I find that the flexibility of pen and
4.
▲
by
Hamatti
1y ago
OP here. Exactly! So happy to read you managed to pick up the core gist of the story. It's important to find the tools that work best for YOU. I partially wanted to write this because I've often felt as an outsider in tech teams w
5.
▲
by
Hamatti
1y ago
OP here. I don't often do very complex software plans like that. My working notes are often on a smaller scale like individual features or so. If we need to document the full architecture for the project, I'm happy to do that with
6.
▲
by
Hamatti
1y ago
I do almost no organising of my paper notes. The only thing I do is that I add a date to the corner of the first page of when I start making a specific note and I keep index pages where I list page/note titles (or topics, themes, not e
7.
▲
by
Hamatti
1y ago
OP here. > It's slow to write Only to an extent. I write fast enough with pen and paper that my thinking is the bottleneck — which isn't really that fast. I don't need to write down everything I think so it also acts as a
8.
▲
by
Hamatti
1y ago
OP here. Last time my blog caught attention in HN, I was told I'm "living in a fantasy" and this time it's "pure romanticism". The tools you shared are of course important and I enjoy having them a lot. Wouldn&
9.
▲
by
Hamatti
2y ago
That's where the heavy pruning comes in. If there's too much coming in, it's important to get rid of the ones that are less important or most often skipped. For me, the serendipity comes through discoveries inside the blog po
10.
▲
by
Hamatti
2y ago
For me, RSS is the solution to FOMO because I don't need to worry about missing new posts because some algorithm decided not to show them to me or because I didn't happen to see them during the short window they were visible in ot
11.
▲
by
Hamatti
2y ago
My comment above about living in a fantasy was a reply to the root comment's notion that reading through RSS feed in the morning is a romantized, unachievable fantasy similar to a dad starting a day reading the newspaper (which is also
12.
▲
by
Hamatti
2y ago
I wrote about many of those reasons in the blog post. Cutting off the middle-man, slowing down the hectic life and staying in touch with my internet friends are a few of those reasons.
13.
▲
by
Hamatti
2y ago
> it unavoidably leads to content that is created purposely to game that algorithm, which ultimately corrupts the user experience. This is the functionality that really drove me away from social platforms, other than Mastodon. I prefer h
14.
▲
by
Hamatti
2y ago
> Being in charge of your own feed does not mean it will remain lean and sweet. You're right. It does not automatically mean it. You have to maintain it just like anything else in life. > is mostly just a fantasy. It's a fan
15.
▲
by
Hamatti
3y ago
I really like that approach: provide an opt-in for people who need or want the extra features that require login (for example, cloud sync or saving history in cloud or whatever).
16.
▲
by
Hamatti
3y ago
I'm always interested in checking out new tools. That's how I noticed Warp in the first place if it wasn't for the account requirement, I would have given it a go to see if it would have improved my workflow compared to what
17.
▲
by
Hamatti
4y ago
In my experience, print statements should be the starting point because they offer a fast and easy solution and can help you first of all confirm that you're looking at the right part of the code. One point when I switch from print to
18.
▲
by
Hamatti
4y ago
I haven't used LaTeX enough to really have an answer, sorry. Hopefully someone else who's a power user can comment!
19.
▲
Print is your best debugging tool
(hamatti.org)
3 points
by
Hamatti
4y ago
|
4 comments
20.
▲
Humane Guide to Debugging Web Apps
(hamatti.org)
1 points
by
Hamatti
7y ago
|
0 comments
21.
▲
by
Hamatti
7y ago
I love this idea. As someone currently living in Helsinki but having been an expat before, having support in finding the way at the beginning is so valuable. I hope this will evolve into a one-stop shop at finding information about paperwor
22.
▲
Dev Breakfast Newsletter
(hello.futurice.com)
2 points
by
Hamatti
7y ago
|
0 comments
23.
▲
BrowserStack can speed design reviews for teams using Jira
(futurice.com)
1 points
by
Hamatti
7y ago
|
0 comments
24.
▲
Show HN: Simple back end system for front end workshops in JavaScript
(dev.to)
2 points
by
Hamatti
7y ago
|
0 comments
25.
▲
by
Hamatti
7y ago
This is such a great initiative. I work as a dev at Futurice and I've been enjoying the opportunity to the fullest. I would be tinkering with stuff and releasing my projects as open source regardless so it's such a great perk to g
26.
▲
Detecting Cute Animals with Machine Learning
(towardsdatascience.com)
1 points
by
Hamatti
7y ago
|
0 comments
27.
▲
by
Hamatti
8y ago
> However, writing good documentation can be really hard. As the developer, you are, at the same time, the best and worst placed person to document. Best because you know exactly how the software is supposed to work, and worst, because y
28.
▲
by
Hamatti
8y ago
I totally agree with you. It requires good understanding of the project but also it's beneficial to know the pitfalls and decisions made or left unmade that ended up shaping the project. That's why I encourage developers to make d
29.
▲
by
Hamatti
8y ago
Have you talked with people using your tools and asked them? Unfortunately people will rarely send unsolicited good feedback to tools they enjoy so it's important to chat with your users.
30.
▲
by
Hamatti
8y ago
Hey! Original author here, excited to see open source documentation brought up in Hacker News. I feel like documentation in general is a topic we developers don't talk about enough and it's often cast aside as a "we'll d
More ›