braveo

9 ms·

31.
by braveo 9y ago
The author doesn't understand what boilerplate means.
32.
by braveo 9y ago
> Any time we write similar-looking code over and over, that’s considered boilerplate. That's not what boilerplate code is, and DRY is not the way you get rid of boilerplate (the article claims it is a part of the solution). boilerp
33.
by braveo 9y ago
I don't really have a source, but it's common with protein powders. They'll list 28 grams as a serving size with a scoop that has a line in it about 3/4 of the way up that represents 28 grams. Technically not misleading
34.
by braveo 9y ago
I'm not sure what that buys you that you can't get by just using an identity column.
35.
by braveo 9y ago
It was, I meant I went looking for it in the article and didn't see it :)
36.
by braveo 9y ago
I didn't provide enough context. There's nothing wrong with using UUID's, but I would avoid them for clustered indexes. And I would say typically you wouldn't care about whether or not UUID's were sequential unless
37.
by braveo 9y ago
I'm curious, why this approach instead of something like DOSBOX?
38.
by braveo 9y ago
I can't speak for other databases, but SQL Server's NEWSEQUENTIALID is only guaranteed until the server reboots. At which point the next UUID integer value can be less than the previous, at which point you're back to splitti
39.
by braveo 9y ago
The one point I went looking for and didn't see is that UUID's make for very poor clustered indexes. SQL Server tried to mitigate this with the 'NEWSEQUENTIALID', but it essentially 'resets' when the server is
40.
by braveo 9y ago
especially since companies are notorious for making the scoops bigger than expected so you go through product quicker.
41.
by braveo 9y ago
I would point to both CLang and KDE as projects with very good modularity. I remember reading through the sources oc CLang a few years back and being impressed with it.
42.
by braveo 9y ago
Not only that, but the intern can make decisions that an automated system isn't going to be able to do safely due to ambiguities, etc. This reminds me of an automated licensing call I was putting together once. The company owner wante
43.
by braveo 9y ago
> I would like to believe that if the panel person was a male, it would have elicited the same building irritation from the audience. Although, I'm less sure that someone would have spoken up. This makes me think of a complain I saw
44.
by braveo 9y ago
I don't disagree with the sentiment, but I felt it important to point out that the assumption made in the sentence I quoted was itself a sexist assumption.
45.
by braveo 9y ago
> Saying "that wasn't sexist; so-and-so is actually less assertive" kind of assumes that we're talking about conscious sexism. The idea that less assertive implies female is sexist. The person you're responding t
46.
by braveo 9y ago
> In my opinion, ignoring hurtful behavior because we believe the intent wasn't meant to be hurtful will only encourage these behaviors in the long run. OTOH, maybe you should man the fuck up and move on with your life. I know that
47.
by braveo 9y ago
I think the important point is that everyone has to deal with bullshit, and it's generally better to assume it's not meant to intentionally hurt. I've had many occasions where someone has said something that caught me a littl
48.
by braveo 9y ago
I decided a while back that Uber was a horrible company and they will never have any of my money. And the shit keeps coming. At some point hopefully others will make the same realization.
49.
by braveo 9y ago
yes, that's what I meant, I was in a hurry this morning.
50.
by braveo 9y ago
> Attempts to talk over panelist when panelist starts to speak, but notably the panelist consciously speaks louder and repetitively to cut off the moderator. If that isn't talking over another panelist, I don't know what is...
51.
by braveo 9y ago
I can tell you're young.
52.
by braveo 9y ago
That's not at all what I said. It's a business decision. That's it. I didn't say we should optimize for direct bottom-line business interests. I said IT IS A BUSINESS DECISION. It is not the decision of the developers
53.
by braveo 9y ago
And yet, the decision to target a specific browser is STILL a business decision.
54.
by braveo 9y ago
I'm going to have to agree with 2bitencryption here. Everything is a "moral choice" when the person demanding the choice feels strongly about it, but that typically means you just lack perspective. At the end of the day we&#x
55.
by braveo 9y ago
That isn't what I asked, I asked if this class of problem is truly causing a lot of harm. Software stabilizes over time, you find problems and then you fix them. How often are these class of bugs causing catastrophic issues? That&#x27
56.
by braveo 9y ago
Are these category of bugs a constant problem in FF?
57.
by braveo 9y ago
that's purely a business decision.
58.
by braveo 9y ago
You may have your timelines incorrect then. By the time Mozilla and Firefox came around MS had already won that war and it was businesses who were making the decision to target IE, not developers. When developers were pushing IE was when i
59.
by braveo 9y ago
> Disagree. Developers were the ones that pushed Mozilla and then Firefox (and then Chrome) as soon as they could. No, the DOM put into IE was legitimately better than that in the old NN. MS won that war because their browser was BETTER
60.
by braveo 9y ago
I'm not old, I'm just not young enough to romanticize prison.

More ›