Hacker News: mstachowiak

New comment by mstachowiak in "Is this the end of the once-mighty GoPro?"

mstachowiak — Sat, 18 Jul 2026 19:32:32 +0000

Sadly, consumer goods are the new arms (drones, batteries, etc)

New comment by mstachowiak in "EPA Moves to Cancel $7B in Grants for Solar Energy"

mstachowiak — Tue, 05 Aug 2025 16:13:54 +0000

You can finance the purchase to avoid upfront payments. And in many cases, the energy savings exceed the finance payments, resulting in a net monthly gain from a cash flow basis with no upfront payment.

New comment by mstachowiak in "AI Sucks at Code Reviews"

mstachowiak — Fri, 15 Nov 2024 19:02:34 +0000

I'm the author of the article. Yes, I agree. I think AI reviewers, in their current state, are essentially glorified linters. Much of what they excel at can already be achieved with linting. However, I believe their edge lies in spotting semantic mistakes, whereas linters are ideally suited for syntactic or stylistic issues.

New comment by mstachowiak in "Some of us like "interdiff" code review"

mstachowiak — Wed, 11 Sep 2024 03:34:40 +0000

It's always exciting to see new approaches to code reviews - GitHub has its strengths, but it’s far from perfect.

For the scenario you’ve outlined, have you thought about splitting the 3 patches into separate, dependent pull requests? While GitHub doesn’t natively support this, the right code review tool (shameless plug - I’m part of a team building one called GitContext) should allow you to keep pull requests small while maintaining dependencies between them. For example, patch 3 can depend on patch 2, which in turn depends on patch 1. The dependency tracking between them - provided by the code review tool - can ensure everything is released in unison if that's required.

Each patch can then be reviewed on its own, making feedback more targeted and easier to respond to. You can even squash commits within a pull request, ensuring a clean commit history with messages that accurately reflect the individual changes. Better still, with the right tool, you can use AI to summarize your pull request and review, streamlining the creation of accurate commit messages without all the manual effort.

A good code review tool also won’t get bogged down by git operations like rebases, merges, or force pushes. Reviewers should always see only the changes since their last review, no matter how many crazy git operations happen behind the scenes. That way, you avoid having to re-review large diffs and can focus on what’s new. The review history stays clean, separate from the commit history.

I'd be curious if this approach to splitting up pull requests and tracking their inter-dependencies would address your needs?

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Tue, 05 Dec 2023 03:32:33 +0000

Agreed, that's a tough pill to swallow. We envisioned trial period to let people make up there mind, but free for the first few users is another route. We'll noodle it when we loop back to pricing. Appreciate the feedback, it's helpful.

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Tue, 05 Dec 2023 01:14:43 +0000

We agree! Thanks for adding yourself to the waitlist, I'll make sure you're granted access

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Tue, 05 Dec 2023 01:13:30 +0000

Fair question. We're aiming to provide enough value for the price we'll ultimate target. We aren't charging yet, but wanted to provide people with some of our rough thoughts on pricing since it's a common question. For now, it's free for folks who want to kick the tires.

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Tue, 05 Dec 2023 01:07:34 +0000

Thanks for highlighting, we're investigating and should have a fix shortly.

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Tue, 05 Dec 2023 00:28:30 +0000

Sorry for the confusion. It's currently only offered as a web application and only works with GitHub. We are working to expand beyond these limitations based on customer needs / interest. I assume your interest is in a desktop application?

New comment by mstachowiak in "A study of Google's code review tooling (Critique)"

mstachowiak — Mon, 04 Dec 2023 21:02:22 +0000

Shameless plug - I'm one of the creators of GitContext (https://gitcontext.com), a code review tool which has drawn much inspiration from Critique and others, and would love feedback from anyone who's interested in kicking the tires. We just launched in private alpha.

We're putting a maniacal focus into the user experience of code reviews, which we feel is overlooked by most tools. Many of the features of Critique that developers enjoy have been included in our first release... - A focus on only the latest changes - A familiar, side-by-side diffing interface - show 'diff from the last review' by default - Tight integration with other tooling - 'Action set' tracking - we allow you to pinpoint and assign line-level issues to relevant team members and track who's turn it is to act - Satisfying gamification - plenty of buttons that go green and even some fun visual rewards for merging

Additionally, we've layered in... - A beautiful, modern UX that provides light or dark mode - Comments that never become outdated and reposition/evolve with the review - Smart version tracking that handles rebases, merges, and force-pushes gracefully - Progress tracking that allows you to see what each participant has left to complete down to the file revision level. - A real focus on trying to get turn tracking right

We're just getting started and have a ton of ideas we can't wait to layer on. If anyone is up for giving it a try, we're actively seeking feedback. If you mention 'Hacker News' in the waitlist form we'll let you in right away.

New comment by mstachowiak in "Google I/O: Big changes coming for SEOs with ubiquitous AI"

mstachowiak — Wed, 10 May 2023 22:57:31 +0000

I tend to agree, because if Google doesn't, OpenAI et al will. The real question is how does Google balance this against the loss in advertising revenue?

New comment by mstachowiak in "Yellen says government will help SVB depositors but rules out bailout"

mstachowiak — Sun, 12 Mar 2023 16:34:02 +0000

Reminds me of Charlie Munger's belief that the world is driven by envy, not greed. https://www.cnbc.com/2022/12/10/billionaire-charlie-munger-w...

New comment by mstachowiak in "Stripe refunds: fees from the original charge are not returned"

mstachowiak — Thu, 20 Feb 2020 04:15:47 +0000

Thanks for replying on this thread, PC. I'm curious to get your take on how this plays out for customers with large average transaction values ($500+)?

Stripe's cost to process and refund a payment, while not zero, is generally flat (card networks refund interchange fees, Stripe only has to cover the minimal cost of running the software to process the transaction, which is the same for all transaction sizes). Shouldn't the retained fees be flat and not a percentage?

New comment by mstachowiak in "OpenSSL wins the Levchin prize"

mstachowiak — Thu, 11 Jan 2018 01:22:51 +0000

Can't help but find it ironic the winner of the 2018 Levchin Prize for Advancements in Real-World Cryptography has an invalid SSL certificate on his research website.

New comment by mstachowiak in "F.C.C. Repeals Net Neutrality Rules"

mstachowiak — Fri, 15 Dec 2017 14:59:28 +0000

For reference, the previous commenter was talking about AL's 7 congressional districts. US congressional districts are defined based on population (they're suppose to be equally sized intra-state).

New comment by mstachowiak in "Ask HN: Who is hiring? (March 2017)"

mstachowiak — Wed, 01 Mar 2017 18:39:19 +0000

MyVR | Software Developer | SF | https://myvr.com

We're building the open platform powering the vacation rental industry. Join our experienced team disrupting a massive and rapidly growing industry.

https://myvr.com/careers/

New comment by mstachowiak in "Tesla Says Model 3 on Track as Quarterly Loss Beats Estimates"

mstachowiak — Thu, 23 Feb 2017 01:48:33 +0000

I would propose viewing Tesla as an energy storage company, not a car company (JB and Elon both think of Tesla this way). The car is a battery on wheels, and the battery is the product. They're not trying to be the next BMW, and attempts to value them through this lense will miss the mark.

New comment by mstachowiak in "Tesla Says Model 3 on Track as Quarterly Loss Beats Estimates"

mstachowiak — Thu, 23 Feb 2017 01:01:38 +0000

In Tesla case, it's because the non-GAAP numbers represent how they view and make decisions about their business internally. It makes them look better in some dimensions and worse in others. They report on it because it gives insights into how they think about things.

New comment by mstachowiak in "Co-founder Conflict"

mstachowiak — Sat, 18 Feb 2017 23:38:50 +0000

Interesting hypothesis. A quick look at YC's top companies by market cap seems to back it up:

Airbnb: 3 design centric cofounders DropBox: 2 tech cofounders Stripe: 2 tech cofounders

New comment by mstachowiak in "George Orwell’s 1984 is currently the top selling book on Amazon"

mstachowiak — Wed, 25 Jan 2017 06:41:45 +0000

The emoluments clause of the constitution applies to all members of government.