novocantico

9 ms·

61.
by novocantico 5y ago
> Unit tests are never a tool to prove stuff to managers/customers/stakeholders. They are in certain agile circles. Ones I used to work in.
62.
by novocantico 5y ago
I find that having one commit per logically-grouped set of changes really helps me to focus on those changes and not get distracted. Before I got into that habit, for years I would try to cram so many features in at once, and would have a
63.
by novocantico 5y ago
The main feedback I have is that I wanted to read this near the end of my lunch break, because I've been interested for years in the idea that a reasonably-restricted subset of TypeScript (who needs all that dynamism) can almost defini
64.
by novocantico 5y ago
> the agreement they signed didn't say remote Just read stuff you sign, don't sign unless you agree, and ask to modify if needed. Incredibly easy way to avoid problems like this.
65.
by novocantico 5y ago
One argument against 100% test coverage that I've never heard articulated in my decade career as a professional software engineer is that we need to learn to just trust trustworthy software engineers . Yes, there will sometimes be m
66.
by novocantico 5y ago
https://www.novocantico.org/ The only thing interesting about it is its implementation (it's self-hosting). I've tried writing blog posts explaining it but it's difficult to explain.
67.
by novocantico 5y ago
One pretty decent Magit alternative I found was lazygit. For a long time after quitting Magit/Emacs I just used git's CLI, but lazygit is pretty great.
68.
by novocantico 5y ago
What you're describing is a lack of engineering in modern software. That's not inherently a bad thing. Arguably a good thing, because we have more problems solved enough to be boxed/canned. But I'm not satisfied with
69.
by novocantico 5y ago
I mean I wholeheartedly agree but that nick
70.
by novocantico 5y ago
Sure you can. Open up your VS Code extension in a VS Code window and live-debug it. I'd bet the process is probably very similar when editing VS Code yourself, but the point of the extension system is that you usually shouldn't ha
71.
by novocantico 5y ago
I used Emacs almost exclusively for half a decade and got pretty good at it. But I feel like VS Code is the natural evolution of all the great ideas of Emacs. So I use VS Code almost exclusively now.
72.
by novocantico 5y ago
Who knows, maybe someone who works on Chrome or Edge or Safari is reading this thread and will talk to their higher-ups about using it somehow. (Wishful thinking?)
73.
by novocantico 5y ago
Relating to it being the "oldest problem ever", there are some interesting philosophical properties of certain numbers. Augustine wrote about certain numbers quite a bit in his voluminous City of God (and probably elsewhere). If y
74.
by novocantico 5y ago
I try to lead as ordinary a life as possible, within reason, and use general problem-solving techniques for any issue I need to solve. 99% of the time, this doesn't happen by writing software. Which, it turns out, is actually a pretty
75.
by novocantico 5y ago
First and foremost, have a purpose or goal that's worthwhile. Everything we do starts with where we're coming from and where we're going. What you're describing is essentially low-level burnout. The cause of burnout is t
76.
by novocantico 5y ago
Most likely because those who can, don't unless they're paid for it. Which FOSS discourages by its nature.
77.
by novocantico 5y ago
I don't really understand this, but I understand even less why 22 people are sponsoring it on Patreon. Can someone let me in on the secret?
78.
by novocantico 5y ago
Related to this, something I did 10 years ago and started seeing more often (especially in git-bash!) is to have * a newline before your current prompt * a newline after all your context and right before your "$ " This helped me t
79.
by novocantico 5y ago
It's also extremely easy to abuse, which IMO kind of negates the benefit you pointed out.
80.
by novocantico 5y ago
That's not really about right vs wrong. That's about having a goal and trying to meet that goal. The goal here was to learn Rust, so using Rust to write [whatever] in makes perfect sense for that goal. When I learned to look this