Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
alangpierce
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
alangpierce
8y ago
Idiomatic TypeScript and idiomatic JavaScript are nearly the same; it's not like the C vs. C++ situation. A design goal of TypeScript is to make it possible to define types for idiomatic JavaScript programs, and I think they meet that
62.
▲
by
alangpierce
8y ago
I think it's pretty reasonable to ban jokes about killing people. Maybe it was an overreaction here, but I certainly try to avoid even jokingly saying things that could be interpreted as a death threat if taken seriously, especially on
63.
▲
by
alangpierce
8y ago
One tool, not mentioned so far, is tota11y: http://khan.github.io/tota11y/ It gives a bunch of inline annotations for accessibility problems and points of concern. Not sure how it compares with the others suggested, bu
64.
▲
by
alangpierce
8y ago
> His time was 2 hours 46.03 minutes which by modern marathon times does not look so great but was good at that time. This made me laugh a little. I guess at the Olympic level it "does not look so great", but that's a fa
65.
▲
by
alangpierce
8y ago
Might be good to clarify use cases in the README. It sounds like this is useful for reading and writing binary file formats. My initial thought was that this was intended for careful memory management for performance reasons, like a packed
66.
▲
by
alangpierce
8y ago
It does depend on the job, and I don't doubt that there exist jobs where DP in the interview process is reasonable, especially if it's a "CS job". I'm particularly talking about software engineering interviews, to b
67.
▲
by
alangpierce
8y ago
I guess I'm more worried about false negatives (i.e. people doing poorly who would do well on the job) than false positives. I have worked with excellent coworkers who I think would likely do really poorly on DP questions because they
68.
▲
by
alangpierce
8y ago
> is that "dynamic"? Nope, DP is a bit more than "build a table" or "cache results". It's specifically about framing a problem recursively, and it needs to be the sort of recursion that has overlapping
69.
▲
by
alangpierce
8y ago
TBH it's been a while since I've done these contests seriously, but I remember the "order of computation" problem to be hard to think about for less trivial cases (like with a 3-dimensional table). But maybe I worried ab
70.
▲
by
alangpierce
8y ago
Yep, it's still certainly DP, in the same sense that 1 + 1 is addition, but understanding 1 + 1 doesn't necessarily mean that you've mastered addition.
71.
▲
by
alangpierce
8y ago
> problems on DP are pretty standard in most product-company-based hiring challenges This is sad and a little surprising to me. I've always thought of DP problems as being obviously terrible interview questions, even among the diffe
72.
▲
by
alangpierce
8y ago
> So "DP" is just recursion with memoization? Sort of. "I know DP" doesn't just mean "I know what memoized recursion is". It means "I know how to take a problem, recognize that DP might help, frame
73.
▲
by
alangpierce
8y ago
I've done a lot of programming contest stuff, and at least when speaking casually, I've always heard DP as referring to either the top-down approach or the bottom-up approach. They have their tradeoffs (though usually top-down is
74.
▲
by
alangpierce
8y ago
> It's not representative of the work that the candidate would be doing I have absolutely used whiteboards on the job at every software job I've had. Collaboratively brainstorming a system design, working through examples, and
75.
▲
by
alangpierce
8y ago
To be clear, this is saying that seed-phase companies have a 74% chance of eventually failing, and a company that makes it to series C is nearly as likely to eventually fail, at 71%? My impression was that joining a later-stage company is g
76.
▲
by
alangpierce
8y ago
They acknowledge that the term "whiteboard interview"/"whiteboarding" is a simplification and a proxy for a style of interviewing they don't like, but I really wish they didn't pick "whiteboard"
77.
▲
by
alangpierce
8y ago
For an open source project, I'd recommend using an autoformatter, documenting it in the contributing guide, and enforcing it in CI so that anyone submitting a PR can clearly see if they submit something that breaks the formatting rules
78.
▲
by
alangpierce
8y ago
Part of the point of solutions #1 and #3 is that they pass in exactly the same function on each render, so it's possible to avoid unnecessary rendering further down by knowing that the props are the same as before. The hooks solution w
79.
▲
TSLint in 2019: TSLint Will Be Officially Deprecated in Favor of ESLint
(medium.com)
12 points
by
alangpierce
8y ago
|
1 comments
80.
▲
by
alangpierce
8y ago
I agree that create-react-app is bloated and overkill, but that's also a lot of the value in it, or at least it has been for me. When I used CRA for a project about a year ago, it spit out a gigantic README with everything anyone ever
81.
▲
by
alangpierce
8y ago
You don't need to use different languages to decouple things. A common pattern in React is to decouple logic and style using presentational components and container components (there are lots of articles on it if you Google those two t
82.
▲
by
alangpierce
8y ago
The "predictable performance" point applies not just to performance across browsers but also that you don't need to pay JIT warm-up costs. A while back, I ran some benchmarks on the same codebase in TypeScript and AssemblyScr
83.
▲
by
alangpierce
8y ago
> The docs actually state quite clearly that developers are discouraged from replacing class components with function components. Could you link to where it says this? My understanding is that hooks are intended to be the new best practi
84.
▲
by
alangpierce
8y ago
This certainly agrees with my experience. I've had a number of cases in the past where I'm feeling low/depressed at work and tend to get more frustrated, e.g. annoyed with some policy or some design decision or some detail ab
85.
▲
by
alangpierce
8y ago
It's tricky. On one hand, it seems odd to say "you must care about the work you do". On the other hand, I think there's a noticeable difference in quality between software that just meets the minimum requirements vs soft
86.
▲
by
alangpierce
8y ago
That doesn't really resonate with me, might just be a cultural disconnect. I've worked at 5 Bay Area tech jobs, and in all of them, it has been fairly common that some people choose to stay for dinner. Sometimes it's people w
87.
▲
by
alangpierce
8y ago
I guess it's a complex decision, but I feel like if I was running a worldwide business and a single country decided to impose a $100 billion fine (the scenario I was describing), I'd want nothing to do with that country. That'
88.
▲
by
alangpierce
8y ago
My office has been using them for years for dinner orders, sad to see them go. We used to use Sprig and Munchery (anyone staying for dinner gets to pick), but then Sprig shut down, so we moved to a choice between Munchery and a group Caviar
89.
▲
by
alangpierce
8y ago
I guess depends on exactly how you use JSDoc, but it sounds like you're talking about relatively informal documentation with some best-effort machine validation. My experience is that you don't get anywhere close to the confidence
90.
▲
by
alangpierce
8y ago
Note that it's possible to use both TSLint and ESLint in the same project, and that's what I've been doing for nontrivial projects. ESLint has a big community and a lot of nice rules, but there are a few things that ESLint ca
More ›