Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
protonimitate
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
protonimitate
6y ago
Agreed - this article reads like a "get good" message to "amateurs". Which, sure, you should be striving for constant improvement - but if you work in an environment where sloppy/quick work is incentivized I would a
32.
▲
by
protonimitate
6y ago
> a constant worry that I'll miss a dependency in my useEffect call and end up crashing my browser session. As an fyi for anyone not aware, there are eslint/tslint plugins for this to help avoid it.
33.
▲
by
protonimitate
6y ago
This is a good point. I wish there was more discussion around when to consider making these decisions, how to transition, what types of systems are in the middle ground between bedroom and facebook, etc. It seems all of the articles/
34.
▲
by
protonimitate
6y ago
> If anything, the entire team seemed to do far more due diligence in decision making than pretty much 90% of the move-fast and break things (TM) SV startups. Right, but this still isn't the fault of React. My gripe with this artic
35.
▲
by
protonimitate
6y ago
> The point about React including so little that you become reliant on a ton of external dependencies that see even more churn than the usual JS framework landscape is a very valid pain point, especially when you are building a very larg
36.
▲
by
protonimitate
6y ago
> Nowadays, the public square, the thing that the constitution is supposed to protect, which is the difference between feudalism and democracy, is de-facto (though not de-jure), owned by monopolistic corporations. That's quite the e
37.
▲
by
protonimitate
6y ago
HN users have read 1984 one too many times. It is possible to think that SV has too much power AND that they still have the right to deem what is acceptable on their own services. You can be entitled to free speech without being entitled to
38.
▲
by
protonimitate
6y ago
Makes sense, thanks.
39.
▲
by
protonimitate
6y ago
No one. > (presumably, but could be any other)
40.
▲
by
protonimitate
6y ago
I'm not a lawyer, and at the risk of sounding ignorant, but I don't understand how a Polish law can be enforced on a company/service/piece of hardware under US (presumably, but could be any other) jurisdiction. At the en
41.
▲
by
protonimitate
6y ago
> It's an idiom to succinctly describe a chain of causality. Right, and the fallacy is that it's being pre-attributed to a sequence of events that hasn't happened yet. Again, it's a boring argument and adds nothing to
42.
▲
by
protonimitate
6y ago
I swear this same exact post gets re-dressed and upvoted weekly. Is there anything worth discussing here? The entire thesis of the post is "my blog is maintenance free". Ok, and? Is blog maintenance really a noteworthy topic? How
43.
▲
by
protonimitate
6y ago
The "slippery slope" / "free speech" arguments are boring, and come into play almost anytime Facebook gets mentioned on HN. "Slippery slope" is also most commonly a fallacy , which a lot of people seem to
44.
▲
by
protonimitate
6y ago
Svelte is be recommended left and right as the "solution to React" but I think it's still way too young of a project to be the cure-all that people think it is. It's promising, especially for smaller projects/MVPs,
45.
▲
by
protonimitate
6y ago
> Are people good judges of how much value they bring a company? IME skils/merit/value contributions have very little to do with salary. It's mostly negotiation tactics. Having public data on salaries would help potential
46.
▲
by
protonimitate
6y ago
> In 99.9% of the cases people work on perhaps technically exciting but impactwise boring industry projects, whose main mission is to make money. Passion, imo, is an attitude - and is reflected in quality of work and teamwork. I do think
47.
▲
by
protonimitate
6y ago
I really like the idea of "chopping the onion". I've personally had a handful of devs who passed our interview process with flying colors, but couldn't actually deliver anything once they got in the door. They could reci
48.
▲
by
protonimitate
6y ago
I'm curious - what's the conversion ratio for this? I like the idea of this but can't help but think it's ripe for being taken advantage of (on both sides). Have you had trouble with converting to full time offers? Have
49.
▲
by
protonimitate
6y ago
Selfishly, no, you should offer to pay what you think is fair for the exchange of service you receive. If you get the same quality work from a person who lives in NYC as a person who lives in Ohio, the pay should be equal. But, as a busines
50.
▲
by
protonimitate
6y ago
"Temp code" is the biggest lie anyone will ever tell you as a programmer. Everyone will have perfectly good intentions, from PMs to directors to ICs, but "this is only temporary" almost never is.
51.
▲
by
protonimitate
6y ago
> You see it all and you'll get it all, so why the fuss? Because people are afraid that they won't be able to command 350K a year salaries anymore. The fear is that the "good old days" of SV salaries are over is being
52.
▲
by
protonimitate
6y ago
> I'm pro basic income, but definitely don't support paying more to be unproductive than productive. And if COVID has proven anything, its that the most productive workers are the ones who didn't even get a chance to earn
53.
▲
by
protonimitate
6y ago
I think the point of the $600 was to keep the economy from seizing up, and keeping people at home was a side effect.
54.
▲
by
protonimitate
6y ago
The Touch Bar is honestly by least favorite aspect of anything Apple has done in recent memory. My touch bar had dead pixels (twice), effectively wiping out half the function keys. And when it did work, it was hard to use. I've been us
55.
▲
by
protonimitate
6y ago
Agreed, I'm pretty bored by the influx of "No-Javascript" articles being pushed to the top of HN weekly. There is almost never any new insight, and you could copy+paste comments from one to the next and not know the differenc
56.
▲
by
protonimitate
6y ago
Ah yes, the outsourcing FUD train is ramping up. Remote work has been a possibility for employers for a few decades now. Nothing has drastically changed since the new wave of WFH to change that, other than its more widely discussed. > 5
57.
▲
by
protonimitate
6y ago
Yup, we recently implemented auto linting/formatting using pre-commit hooks and it's made a huge difference in maintainability and readability. I don't care about the specific formatting/linting rules as much as I care a
58.
▲
by
protonimitate
6y ago
Yeah, I'm becoming increasingly frustrated by the flood of "anti-hype-driven-development" blog posts being praised. The entire article could be summed up with: > Is it solving your problem, and what is the cost? And it cut
59.
▲
by
protonimitate
6y ago
> Just accept the fact that you've switched positions and that your relationship will change. The key here, I think, is the relationship aspect. I've seen and had so many terrible managers that had no idea how to create and mai
60.
▲
by
protonimitate
6y ago
Yup - from a implementation perspective, bug vs feature is a artificial designation. Where I think it _does_ matter, is when a business wants to track metrics like "# of bugs over time" or "# of bugs per feature". My tea
More ›