stephen

16 ms·

121.
by stephen 7y ago
Fair! Thanks for the reminder. You're right; I was very early into this thread, when those comments were still at the top. And also the mobile app I use doesn't have a down vote button, so my "I want to react" urge had t
122.
by stephen 7y ago
The comments on this thread are terrible. I don't know enough about him to pass moral judgement, but it seems like many others think that they do (after a quick scan of Wikipedia, meh, that's good enough). It just seems crass to b
123.
by stephen 7y ago
Supposedly es4x (powered by GraalVM) cracked the top-5 empower benchmarks, while no other Node/JS frameworks are in top-20/top-30 (iirc): https://www.youtube.com/watch?v=JUJ85k3aEg4 The assertion in the ^ video (f
124.
by stephen 7y ago
Great post. I've also been ranty about hooks lately but am admittedly also just learning more ins/outs of things as I go. That disclaimer aside, my biggest gripe is that I think hooks _could_ have been done in a "works from b
125.
by stephen 7y ago
I inherited several Flow codebases, which is from the same guy/group as Reason at FB, and attempted to do the same goal of "bah explicit type annotations, let's infer everything". This nearly ruined the codebases and we
126.
by stephen 7y ago
Fancy new names is basically the antithesis of Fowler's approach (it's driving shared language/canonical definitions). And personally in the mid-2000s I found Fowler's material to, contrary to your assertions/experi
127.
by stephen 7y ago
> older features of typescript [...] protobufjs generated typescript FWIW I have a used-in-production project that generates idiomatic TypeScript types for protobuf: https://github.com/stephenh/ts-proto As a disclai
128.
by stephen 7y ago
Does this use a thread local approach, or a Go-style ctx parameter? Since it's async I expected to see the ctx approach, unless the underlying async executor/framework also supports a thread local-ish capability?
129.
by stephen 7y ago
> Dependency injection leads to elaborate, brittle fixtures I believe that can happen, but personally (N=1) haven't seen it. If anything, (well-done) DI is supposed to prevent that, b/c fixtures are isolated instead of dependin
130.
by stephen 7y ago
Agreed with the articles, mocks are very tied to implementation details. I almost always prefer state-based testing: https://martinfowler.com/articles/mocksArentStubs.html As "observable state goes from a to b&quo
131.
by stephen 7y ago
Isn't DAX only a network-based in-memory cache, and not a in-process in-memory cache? Or is it both? It's definitely at least network-based, b/c you have to spin up instances of it in your VPC. However, they also require cust
132.
by stephen 8y ago
Everyone has an opinion; mine is around lines of code. Do you (as in your entire company/maybe eng department) have less than 100k LOC? If yes, you should stay in a monolith (except for potentially breaking out very specific performanc
133.
by stephen 8y ago
I was just looking at this the other day--at first it looked pretty jank on my desktop chrome, but I switched to an android phone and the animations looked surprisingly slick. (Haven't tried on an iPhone yet.) I know the bar for purist
134.
by stephen 8y ago
Fwiw mirror might be a good fit for that sort of "super real time while editting source files" use case: https://github.com/stephenh/mirror Disclaimer it's my basically-well-functioning hobby project. An
135.
by stephen 8y ago
I'm tempted to apply a Greenspun-ism, that by "not having a package manager", you're going to effectively have a half-implemented, bug-ridden package manager anyway. :-) More seriously, dealing with the version hell that
136.
by stephen 8y ago
Yes.
137.
by stephen 8y ago
> Why should they use the same syntax? ... Go is a different language True; I harp on Go primarily due to their IMO idiosyncratic approach: AFAIU they claim to be a "purposefully boring", "good for in-the-large" langu
138.
by stephen 8y ago
Well, shoot. I don't like/don't want to like Go, but they keep getting better. My general annoyance is that they keep things ~just different enough to be irksome, e.g. in this proposal generics is using parens: type List(type
139.
by stephen 8y ago
> Not much of a suprise really Not to be super contrarian, but AFAIU nutritional treatment of cancer actually is a very big surprise for traditional cancer treatment/oncologists. E.g. a podcast I listened to with Dominic D’Agostino
140.
by stephen 8y ago
> novel dependency resolution algorithm I've heard/read this, but I can't tell what is necessarily novel about it...to me, it reads like old-school/boring Maven transitive dependency resolution. (Not holding out maven
141.
by stephen 8y ago
Wow, vgo seems pretty reasonable. ...I have to take one of my "damn it, go" complaints back. Interesting to see their critique of bundler/et el...AFAICT isn't this vgo min version just old-school Maven resolution + semve
142.
by stephen 8y ago
> Really confused by the downvotes It's not type safe. Any other modern/static language would use generics to ensure inSlice and mapperFn both operate on the same types. People downvoting you probably see this as obvious for pr
143.
by stephen 8y ago
> blindly demands using magical frameworks like Spring and JPA That sounds like ~2005 Java to me, where the ~whole ecosystem was that way, and consequently a lot of Java devs left for Rails. However, I think in Java's today (since ~
144.
by stephen 8y ago
Agreed! And, to me, record/replay is still pretending like it's controllable, b/c even if you decouple for replays, records will always be a PITA. My depressing solution is to just not even try to automate tests against the u
145.
by stephen 8y ago
> It's a tool for your toolbox, reach for it when needed Sure, apologies for being negative about a tool you've worked on and are rightly proud of. I'm sure you already have more users than any open source project I'v
146.
by stephen 8y ago
> isolating changes in protocols That makes sense. Ideally protocols are declarative/documented/typed, e.g. Swagger/GRPC, so you can be more trusting and not need these, but often in REST+JSON that does not happen. > Al
147.
by stephen 8y ago
> Again, nothing manual Yes, sorry for being inexact/overusing the term--I understand the tests drive the recording. What I meant by manual is getting the e2e system into your test's initial state. E.g. tests are invariably &qu
148.
by stephen 8y ago
Looks well done (it uses unicode art, so it must be amazing) but I have a fundamental distrust/dislike of record/replay frameworks...just seems like you're papering over an inherently bad testing approach. E.g. sure, when rep
149.
by stephen 8y ago
In your selenium code, the browser was talking to a database. But sometimes that database is down, or really slow. Polly says "browser, don't talk to the database anymore, instead here's what the database said last time"
150.
by stephen 8y ago
I personally find general-purpose Swift surprising because I'd assumed that they'd have to make various language/runtime compromises, solely for backwards compatibility with Objective C, that it'd always be relegated as

More ›