HN user

rjprins

511 karma
Posts5
Comments195
View on HN

This exactly my process as well. Although interestingly I swap Codex and Claude; having found Claude way more pedantic in its reviews and codex more pragmatic in its implementation. Maybe it differs per programming language.

Evolution is a continuous random branching and selective pruning process. And there is not a lot of pruning going on in the current human explosion. So unless ADHD is an old branch and we see other mammals survive because of their distractability, I remain skeptical.

A little late to the discussion, but what I missed in the comments was to properly try to reestablish the relation with your co-founder at least once more.

It sounds like it will take a lot more than a meeting. The two of you should go on a three day retreat to discuss the company situation and strategy deeply and to repair the connection between you two.

If you have completely different views, in a way that is really interesting and you should both strive to fully understand and learn from each other.

Who knows what lies underneath the difference in views?

Once you know that you can make a much more informed decision and if you still leave it will likely be on much better terms.

I agree that recovering from VCS is something that never actually happens. Mostly because the code is forgotten.

Still, commented-out code is generally worthless and should be deleted. Unless it is actively being worked on and only commented out to achieve some short-term goal. In which case it should also not be commented out but instead live on a branch.

Occasionally you might have two flows and you're not sure which is best. But in that case keep them in separate functions and one of those will not be used but can still be covered with tests. And all static analysis tools will work on it. Just needs a comment about why this unused code is there.

Stress is all about perception. With mindfulness you can practice changing the way you look at things. If you practice zooming out of things that induce fear and see a bigger picture this will generally reduce stress.

The mind has a natural tendency to zoom in on scary things. I guess that is our prey-animal heritage.

Certainly, for rightfully stressful situations immediate action is needed and mindfulness is not a solution, but in modern life almost all stress comes from the imagination. If you are not conscious of your own thinking fearful thoughts may suck you in indefinitely.

Mindfulness (and psychedelics) can greatly help with becoming (more) conscious of fearful thoughts and that enables you to deal with them constructively.

Clearly it depends on the type mindfulness. From the paper:

mindfulness is typically defined as “the awareness that emerges through paying attention on purpose, in the present moment, and nonjudgmentally to the unfolding of experience moment by moment”. Core MBP elements are mindfulness meditation training, doing things mindfully such as eating or brushing one’s teeth, and collective and individual inquiry with a qualified teacher, using participatory learning processes.

Probably heightening consciousness while brushing your teeth is not the most direct way to mitigating stress.

One of the biggest impacts on my life recently was adding an automation for my smart lights (Philips Hue) in the living room.

The lights start dimming over a span of 2 hours until they are their minimum at 22:00.

The result is that it just feels like it is time to go to bed. I have always struggled with getting plenty of sleep and not staying up too late and this has had a tremendous effect the past two months.

If the ranking algorithm tries to maximize "value for the searcher", then SEO could actually mean "produce value for the searcher". Although that might often not actually be the case, it is probably still better than paying Google directly. That would translate ranking to "maximize the value for Google".

Depends on the invader? What if it's the USA "liberating" Belgium from it's evil government? Who says the current government is better than the one taking over?

What are countries anyway, most of them don't align with cultural or language barriers.

Fuck patriotism, fuck flags, fuck any tribalism that powerful people are using to get others to do what they want.

Indeed very often the problems people encounter are described well in the error message and/or stacktrace that is printed. But many, many people find it very hard to correctly read and understand those and it's because that is also a hard skill to learn.

Agreeableness and values similarity are great. You have to consider the opposite as well, if they are low you get lots of conflict and possible hostility. Innovative thinking is especially at risk in hostile environments.

Agreeableness may be confused with "yes nodding", i.e. agreeing superficially while withholding commentary. This can happen especially in hostile environments.

I'm the other way around. I enjoy public transport and feel that cars are isolating and anti-social. I like seeing all kinds of people and having little connections with them. Cars encourage egoism. They battle for space on the freeway. In buses people share the space; they make space for each other or stand up to give a seat to elderly. Cars are often used for status. Public transport is humble.

I don't own a car and never use Uber, but I live in a bike and public transport-friendly city in The Netherlands.

- Ansible lacks proper error handling

- YAML is not a proper programming language

- It's not easy to create reusable "functions". You can include tasks but it can be painful to manage variables, you can depend on roles but everything ends up in separate folders and files.

In retrospect I would prefer to just use Fabric, or use Ansible modules through Python.

Imho, (good) Python code is so easy to read and inspect, that it can be better than documentation. Documentation is less exact. I often find myself reading the libraries that I use, to see what it really does. Once you get into the habit of that, documentation is only useful as a starting point and you can discover a lot more useful functionality. (And also get a good feel of the quality of the library, and learn a lot in terms of patterns)

Of course, this habit comes with the risk that you might have to do more maintenance on your code on library updates.

As documentation takes effort to write and constitutes a sort of contract with your users, it makes sense for library writers to only document the truly essential.

Actually older cities are harder to make compatible for bikes. New cities, with a better urban planning are the ones that win in terms of cycling comfort.

Most parts of most cities are flat. A couple of hills doesn't mean you can't cycle in the rest of the city.

Certifications are nice, but that does not necessarily make people a good IT security specialist.

There is no clear path, but there are many facets to learn about:

* Web application security and popular attacks (such as https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Proje...) * System and network security (learn to use BackTrack http://www.backtrack-linux.org/) * Understand and learn how to use crypto: e.g. known crypto algorithms and what they are good for, learn how to apply disk crypto, learn how SSL works, know how you should do password hashing. * Learn about phishing and social engineering * Learn about malware, botnets, and zero-day exploits.

Learn about all of them but try to become an expert on just one of these subjects by playing with tools. For example, set up a honey pot system to capture malware. Then try to find the malware on it, and then try to reverse engineer it.