Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
MoreQARespect
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
by
MoreQARespect
1y ago
I've recently been following red-green-refactor but instead of with a failing test, I tighten the screws on the type system to make a production-reported bug cause the type checker to fail before making it green by fixing the bug. I
92.
▲
by
MoreQARespect
1y ago
Orgmode has standardized primitives for the things which exist in some markdown note taking implementations but differ from implementation to implementation. Markdown doesn't have a built in concept of todo or tag or scheduled event, f
93.
▲
by
MoreQARespect
1y ago
The same thing happened with the first internet bubble. It didnt prevent the rise of the internet it just meant some players who, for instance, overinvested in infrastructure ended up taking an L while other players bought up their overbuil
94.
▲
by
MoreQARespect
1y ago
>What I meant by "not possible" is writing both sides of the API at the same time. For example, you write a library for overlaying maps on video feeds If I were doing this I would probably start by writing a test that takes an
95.
▲
by
MoreQARespect
1y ago
This is entirely backward. They all started switching when python was already immensely popular after the popularity boosts given by sysadmin, django and numerical/datascience users.
96.
▲
by
MoreQARespect
1y ago
The way to prevent giant classes and methods is with linting rules, not by crippling your text editor. type inference makes code waaaaaay less verbose which aids readability.
97.
▲
by
MoreQARespect
1y ago
It's fine that they dont want to do it or dont want to do it yet. Still, I wasn't especially impressed with "code folding is hard, we might do it one day but don't hold your breath" from an editor that purports to b
98.
▲
by
MoreQARespect
1y ago
>It makes sense at a high level though This is the way I've always done TDD. I don't think it makes sense to do it any other way. If a test case doesn't map on to a real scenario you're trying to implement the code fo
99.
▲
by
MoreQARespect
1y ago
Does it do code folding yet?
100.
▲
by
MoreQARespect
1y ago
I find people overfocus on fast running tests, often to the exclusion of tests which test realistically and loosely couple to the code. This is a pretty easy and natural thing to do because it's quite easy to go "I shaved 2.5 minu
101.
▲
by
MoreQARespect
1y ago
It sounds like they were cargo culting ThoughtWorks. ThoughtWorks and companies like them do work but theyre heavily reliant upon heavy duty sales. Delivery at high quality is necessary but not sufficient.
102.
▲
by
MoreQARespect
1y ago
>We try to replace them every time we come across one that needed adjusting actually. Quick is bad here. And yes they're flaky as hell if you use them for everything. Even a tiny change to just introduce a new element that's su
103.
▲
by
MoreQARespect
1y ago
>No regular developer will carefully review 50 changed snapshots. If you follow a habit of making small, incremental changes in your pull requests (which you should anyway), those 50 snapshots will generally all change in the same way. A
104.
▲
by
MoreQARespect
1y ago
>Maybe I didn't explain properly. Say I create a component, and use snapshot testing to verify that "This is how it should look". Now next person changes something that makes that snapshot "old", and the person n
105.
▲
by
MoreQARespect
1y ago
>You generally don't want to have to change all the tests for every change You generally don't want every change to result in a lot of work . If changing a lot of tests means looking at a table of 30 images and diffs, scanning
106.
▲
by
MoreQARespect
1y ago
>I haven't found any team that used snapshot testing and didn't also need to change the snapshots for every little change, which obviously defeats the purpose I dont see how this even defeats the point, let alone obviously. If
107.
▲
by
MoreQARespect
1y ago
It's often shorthand for "this cant be unit tested" or "this isnt dependency injected" even though integration tests are perfectly capable of testing non-DI code. The author's claims that we should isolate code
108.
▲
by
MoreQARespect
1y ago
The question about whether it takes jobs away is more whether one programmer with taste can multiply their productivity between ~3-15x and take the same salary while demand for coding remains constant. It's less about whether the tool
109.
▲
by
MoreQARespect
1y ago
>Given that most humans and engineers in particular perform best when in position of having high autonomy High autonomy militaries outperform low autonomy militaries too.
110.
▲
by
MoreQARespect
1y ago
It's silly and extreme and dogmatic because that's what he's like as a person. This is as much reflected in his political views - not just coding. It might not be such a problem in other professions but good software developm
111.
▲
by
MoreQARespect
1y ago
hitchstory
112.
▲
by
MoreQARespect
1y ago
Snapshot test driven development is: 1. Write test. 2. Write code that gets the test to pass, generating a snapshot. 3. Iterate on the code until the snapshot looks right (maybe bringing stakeholders in the loop to ask "does this dashb
113.
▲
by
MoreQARespect
1y ago
It's intractable unless the problem space demands 100% correctness at all times. When Im using observability apps I dont demand correctness, I'm very happy if the LLM came up with 3 hypotheses about what happened and I could disca
114.
▲
by
MoreQARespect
1y ago
Scrum is training wheels for agile. If your team were truly terrible and previously had 6 monthly iterations or something you'll be seeing some "agile" benefits which may seem amazing compared to the bullshit you put up with
115.
▲
by
MoreQARespect
1y ago
>I imagine this wouldn't work so well for hard algorithmic stuff where there are mathematical properties you need to be aware of and maintain Mathematical properties are often even more ideal candidates for being encoded into either
116.
▲
by
MoreQARespect
1y ago
Often this is true but I find that for complex or semi-complex applications with confusing (and often shitty) user interfaces LLMs are pretty much a net positive. For all of their faults, one thing LLMs are good at is providing a more user
117.
▲
by
MoreQARespect
1y ago
They're really good at sales and marketing, especially aimed at beginners. I'm still puzzled why people use it given that it's a database and there's nothing technical it ever did better than any of its competitors. The
118.
▲
by
MoreQARespect
1y ago
Yeah, Ubuntu used to be the distro that "just worked" while nowadays that crown has passed to Fedora.
119.
▲
by
MoreQARespect
1y ago
If they measured that too it would make it harder to justify a MSFT P/E ratio of 29.6.
120.
▲
by
MoreQARespect
1y ago
Like tests, types can be more hassle than theyre worth if you dont use them correctly. Before mypy came along I was pretty disciplined at A) testing and B) ruthlessly clamping down on primitive obsession. I use types a lot now but I didnt s
More ›