3,075 karma · joined September 20, 2013
I've taken mental health leave (not due to a PIP) and my productivity before and after was significantly different. It was great for my employer that I took it. I'm quite sure I would've eventually ended up with a PIP if I hadn't taken it sooner myself, and the best remedy on a PIP would have been to take mental health leave. Not as a strategy as such, but literally because it would have been the best solution (and I think the only one).
Someone voiced that they liked a certain tool for a certain feature and suddenly we are judging them for it? I like that people share their thoughts and opinions.
You don't have to stop loving a project just because you're not ready to put in the work that the maintainers expect you to put in.
When I open a PR without discussing it at all beforehand with anyone, I expect the default to be that it gets rejected. It's fine by me, because it's simply easier for me to open a PR and have it be rejected than to find the people I need to talk to and then get them all onboard. I accounted for that risk when I chose the path I took.
1. only using AI for small things, very impressed by it
2. giving AI bigger tasks and figuring out how to use it well for those bigger tasks
3. full-agentic mode where AI just does its thing and I review the code at the end
4. realising that I still need to think through all the code and that AI is not the shortcut I was hoping it to be (e.g. where I can give it a high-level plan and be reasonably satisfied with the final code)
5. going back to giving AI small tasks
I've found AI is very useful for research, proof-of-concepts and throwaway code of "this works, but is completely unacceptable in production". It's work I tend to do anyway before I start tackling the final solution.Big-picture coding is in my hands, but AI is good at filling in the logic for functions and helping out with other small things.
Today I'd honestly suggest to skip learning about git altogether (besides the basics, like branching, staging etc) and just start using lazygit immediately.
I've seen people claim that having a clean git commit history is not worth the time, it takes too long to have it nice etc, opting to just stuff their refactor, renaming and new feature changes into one commit. With lazygit I spend a few extra minutes a day to make it nice and I've gotten compliments for it from others when they review my PRs, because it makes the review much easier.
The big issue is that I'm not very good at moderating my intake. I'm a crack addict for information and one small dose will turn into a bender.
I think when she wasn't in the forest, she was just waiting to go there again. Instead of ball, it was forest.
If I feel like the author might just not be aware of some "better" (subjectively) way of doing things, then I'll leave a "FYI: could also do this in X way" type of comment.
I recently had to install Windows on a machine and the installation process drove me insane. There's tens of things you need to disable to avoid being tracked on a machine _you own_.
Linux is the only OS that leaves the user in the position of power. Treasure your i3 setup. I really hope it lasts for more decades to come.
Add the following to containers.conf if you don't want to deal with it:
[containers]
label=false
If you don't like podman's default security level, there is usually a way to turn things off.It's a pretty rare character indeed.
In the HN bubble, yes. From the perspective of the average business, definitely not. Or at least, doesn't have to be.
We had somebody in a different timezone join the team and there was a long discussion about when we should do stand ups. I almost suggested just dropping it, but that would have been heresy.
Notably, it's still slightly better than the first code example in the original article, as it takes the rounding bug into account.
Software engineering described by a software engineer, love it!