Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shados
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
62 ms
·
571.
▲
by
shados
8y ago
Yeah, a lot of articles and studies quote single family detached homes, while referring to high density, high demand areas where those things basically don't exist. The cost of a 2 bedroom single family in Manhattan is not a very inter
572.
▲
by
shados
8y ago
TypeScript is basically only good now because of the competition. Earlier versions were pretty darn awful. These days, yeah, you're probably right that having only one might be better. Hopefully WebAssembly and languages running on top
573.
▲
by
shados
8y ago
A second bad thing that's equally bad to a first still ends up with double the bad things, which is worse than the single original bad thing.
574.
▲
by
shados
8y ago
Third parties won't get you in trouble as long as you have a DPA, but you need to get it. Customer IDs are fine as long as they can't be associated with other information anywhere else, but if they can, it's an issue. Sanitat
575.
▲
by
shados
8y ago
an exception stack trace containing the data of a customer object could put in a name by accident, for example. And then you're in trouble. The third parties you use could be storing data, even if they tell you they don't. If they
576.
▲
by
shados
8y ago
The answers to all those questions are "it depends". There's a few thousand libraries, those obviously refer to each other.. Some have readme files and that's enough, some have full documentation "books", some
577.
▲
by
shados
8y ago
> We're pretty small scale (< 20 services, < 10 devs) This is really important and the whole point, indeed. Eg: We consider our org to be "many repos" (we have several thousands). However, hundreds of them contain 5,
578.
▲
by
shados
8y ago
The benefits and drawbacks of both approaches is mostly: -what do existing tools do for you by default -what does creating artificial boundaries around projects does to your org (this is purely social/psychological). In both cases ther
579.
▲
by
shados
8y ago
The joke would be that even the simplest nodejs app these days pull in hundreds of libraries because of left-pad style libs... The more serious answer is that when you have hundreds/thousands of applications with as many use cases, cou
580.
▲
by
shados
8y ago
My wording must have been awful...because that's exactly what I was trying to say. The big companies that predate git and such used monorepos because that was the norm at the time, and it was easier to do with the tools at the time, an
581.
▲
by
shados
8y ago
Definitely not 100%. It also has a lot less to do with company size, and more about when the company was created. Before the git and similar tools of the world came to be, managing a single repo was a pain, nevermind hundreds or thousands o
582.
▲
by
shados
8y ago
> Why are you dependent on 3rd party code that isn't in your repo Not the parent, but for us, the 3rd party code is in a private package manager (artifactory, private npm, whatever). Having thousands of libraries we didn't writ
583.
▲
by
shados
8y ago
> Fighting back against monorepo design is dangerous What's dangerous about it? Monorepos have a lot of benefits, and should absolutely be considered. Maybe even by most. But right now in the community it's almost pushed as the
584.
▲
by
shados
8y ago
That's easy. Depending on the interest rate, condo fees, taxes, etc, a 1 million home is about $4500 (less when the interest rates were lower, I think). If you have a couple of DINKs, it's 2250 per person per month, or about $2700
585.
▲
by
shados
8y ago
Define "far from the city". A 3br for 500k is available (if on the low-ish end) for Whaltam, which Boston folks consider to be in the middle of nowhere, but if it wasn't for traffic/transportation problems, wouldn't
586.
▲
by
shados
8y ago
I'm talking out of my behind here, but I was always under the impression some stuff we use casually is built with the assumption it's not under heavy attack, too. Eg: I thought consumer grade videocards were pretty darn insecure.
587.
▲
by
shados
8y ago
Fair, though usually "drinking zero water" as an extreme does not cause death by water intoxication, and avoiding all alcohol does not usually cause liver issues. So im curious how this particular extreme affects the galbladder.
588.
▲
by
shados
8y ago
> Without enough fat, many will see issues with their gal bladder over time Wait what? I was under the impression that most gal bladder issues came from fat, not from not enough fat. Or is it one of those "both extremes are bad"
589.
▲
by
shados
8y ago
Less so because its many up if many complex factors. But if there are conditions that negatively affect memory, attention/focus, writing and reading skills, pattern recognition and more to various degree, it's quite likely the opp
590.
▲
by
shados
8y ago
> I haven’t seen any evidence that experienced professionals can build a website that will last for 5 years either You need a team of experienced professionals, which virtually no longer exists. You could work at 10 different companies b
591.
▲
by
shados
8y ago
> if you want an app that will still be maintainable in 5 years That's part of the issue. People have been making teams who CANT build apps still maintainable in 5 years. Everyone has and only a select few remember/know that it
592.
▲
by
shados
8y ago
Very true. The most important thing you mentioned is this one IMO: > even if they pay for them without realizing that In health care, you have doctors, physician assistants, nurses, administrators, etc. They have very different backgroun
593.
▲
by
shados
8y ago
Can't talk for the person you're replying to, but in my case at least I worked for a LOT of companies (did consulting for a while, and switched jobs probably more than I should have had), AND so did my SO, so while it's anecd
594.
▲
by
shados
8y ago
A lot of companies in tech hotbeds have a hire rate of 25 to 50% of the people who make it in person. It's not "hiring every warm body", but it's pretty damn close in my book, if you consider that resume screening and ph
595.
▲
by
shados
8y ago
Absolutely, there's no full correlation between how hard you work and how successful you are, there are situations where the contrast is totally out of wack. We're (unfortunately) used to execs taking home insane pays for dubious
596.
▲
by
shados
8y ago
> That being said, I’m not following how attitudes in software engineering are related to the topic of this post. Sorry, I probably made my point poorly. It wasn't about attitude in software engineering. It was how insanely overvalu
597.
▲
by
shados
8y ago
Articles like these, while only loosely related, always make me think that the software engineering bubble has to pop. You have people with ton of education busting their behind dealing with little brats all day to try to make sure they hav
598.
▲
by
shados
8y ago
Haha, sorry if it was unclear, my tone was in jest. Yeah, basically what Im trying to say is that this is awesome. It was several years ago so I don't have my old code anymore (different job), but it was in the printing industry, where
599.
▲
by
shados
8y ago
The sample app (the color contrast stuff) hurt my feelings a bit. I used to work on an app that needed to do something similar and I ended up fighting with the YIQ formula (it really doesn't work for a lot of cases). Playing with the s
600.
▲
by
shados
8y ago
Amount of bugs that end up in production. A reasonably important and easy to measure metric.
More ›