Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
beaker52
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
271.
▲
by
beaker52
7y ago
Oddly (I've never seen this before), a fox was struggling in our garden in a London borough yesterday, today it lies dead outside our neighbors house. It's unlikely, but I do wonder.
272.
▲
by
beaker52
7y ago
Haha me too. I think PHP was a great rite-of-passage as a developer back then: inconsistent standard API, all the session and cookie access built in, with all the security gotchyas, evolution from major versions 4 to 5, obsession with Frame
273.
▲
by
beaker52
7y ago
Not sure why the author points out that Svelte isn't JS/HTML/CSS then goes on to recommend Preact over React. Preact isn't React either. If using Preact were caveat-free, React would be redundant.
274.
▲
Conferences, but in Your Home
(homeferences.netlify.com)
3 points
by
beaker52
7y ago
|
0 comments
275.
▲
by
beaker52
7y ago
Should we keep doctors out of their places of work too? Or is their life worth risking? What about the police? What about people who keep electricity/water/communication services running? What about food and goods manufacturers? W
276.
▲
by
beaker52
7y ago
Border Force staff are being (asked/forced) to work overtime specified in their contracts. Why are we so quick to hate on Amazon, who actually deliver things that we're going to need?
277.
▲
by
beaker52
7y ago
Actually, it's really important that people get the latest advice, and feeling bad is a good thing when action is required to prevent worsening outbreaks. It's not just about YOU catching it and surviving it -- as we've seen,
278.
▲
by
beaker52
7y ago
Careful Google, free Kube is GCP's only big-shiny draw and you've just cut that into quarters.
279.
▲
by
beaker52
7y ago
It doesn't have to be _everyone_ - I've played many an online FPS where I really appreciated that _one_ player for the meta battle going on between us whilst the rest of the game unfolded around us. I really play games for those m
280.
▲
by
beaker52
7y ago
This is the case when you get involved in any mid-refactor system or codebase. It has to evolve to it's destination and it always happens over time bit-by-bit. Quitting in the middle of a murder isn't likely to give you the trunk
281.
▲
by
beaker52
7y ago
I find DRY fascinating. It's the source of a large portion of the accidental complexity I find in code. "If I just create this abstraction, all this duplicated code goes away" - we've all heard it and many of us have tol
282.
▲
by
beaker52
7y ago
Just like Facebook introducing the "big coloured square with text on" statuses - users give their attention to big coloured squares with text on them, and thus the adverts they were previously accustomed to scrolling right past.
283.
▲
by
beaker52
7y ago
That people sometimes do shitty things, make mistakes or let me down, and no matter what, if I squint - I can see myself. That I'm not always right, or always better than Joe. And that: I'm not always wrong, and Bob is not always
284.
▲
by
beaker52
7y ago
I dislike the panning of "clean code" in the article because I really think that duplication can be clean as shown. Clean code has a quality of comprehension, not simply a lack of duplication. The example given is pretty typical a
285.
▲
by
beaker52
7y ago
Probably because it doesn't outwardly appear to affect young women so much? People should be able to make such observations.
286.
▲
by
beaker52
7y ago
This holds true until about a year into the project and everything is complicated beyond the desire of your developers and productivity has tanked.
287.
▲
by
beaker52
7y ago
This is the most basic multi-state machine you could make. You could do this with a typescript enum, giving you compile time type checking "for free". I've tried this "state machine" approach but the problem with de
288.
▲
by
beaker52
7y ago
I always push for feedback. I can be pretty feisty when it comes to asking. I think it's only fair that if I bother to talk them either on the phone or in person that I get some sort of feedback. I've even taken to asking the inte
289.
▲
by
beaker52
7y ago
I've actually read this book no fewer than three times. I disagree that it trades on excessive verbiage. I think people were far more eloquent when the book was written and the excessive verbiage is an artifact of that. The book's
290.
▲
by
beaker52
7y ago
That is one of the thing I like about vue.
291.
▲
by
beaker52
7y ago
What you've said is true of any aggregating intermediate API, graphql or not. If you don't want to make n calls, you make a single API endpoint that makes two calls for your one, just like when you compose functions in code. You d
292.
▲
by
beaker52
7y ago
I love product engineering. It's generalist++, and what I believe _most_ software projects need. However it is seen as a forbidden art in many workplaces with strongly-defined structure. I thought working at a tech "startup"
293.
▲
by
beaker52
7y ago
If anything I'd prefer it if styles, logic and dom lived together in the same file. I hate the sheer number of files people create in projects. The worst one I've seen is a ".types.ts" file. Everywhere.
294.
▲
by
beaker52
7y ago
Totally agree with this. I keep seeing "suspense is coming, it's a game changer" but I am yet to see anything particularly game changing.
295.
▲
by
beaker52
7y ago
> My go-to heuristic is "the wordier the question, the more likely it is to be perceived as well intentioned." Just wanted you to know that I have a conflicting heuristic (which admittedly may or may not be unique to me): "
296.
▲
by
beaker52
7y ago
Did you (try|consider) sshd? "Yes, it wasn't suitable because..." "No?" Ah ok, I think it'd work really well here because... Direct, no assumptions, no trick questions, no toes trodden on.
297.
▲
by
beaker52
7y ago
I want this to be true
298.
▲
by
beaker52
7y ago
The problem appears to me to be around the assumptions that we make when we use the phrase "Why didn't you just use x?" Consider "Did you try x?". It's matter of fact. It offers them the benefit of doubt whil
299.
▲
by
beaker52
7y ago
Drawing attention to language constructs like if and return helps you visually identify patterns. When you need to know details you look into the specific code. Highlighting the noisiest and least uniform parts of code is probably not what
300.
▲
by
beaker52
7y ago
1) You want to be recognised for your achievements - that's human nature - everyone wants that. The problem is, you're not getting the recognition you want. That's a disturbingly common thing in the workplace. And it's u
More ›