cgrealy

48 ms·

451.
by cgrealy 7y ago
The second a company sends me a gif email is the second I take my business elsewhere.
452.
by cgrealy 7y ago
But incorrectly. I really wish MS hadn't called the repo stl, it just adds to the confusion.
453.
by cgrealy 7y ago
>> I am a creative professional - which, historically, was a very important part of Apple’s user base; and the reason I still use their products. The keyword there is historically . It's pretty clear that Apple has shifted its m
454.
by cgrealy 7y ago
I think some people are taking this entirely too seriously. This is clearly aimed at people who already know this. It's a joke.
455.
by cgrealy 7y ago
Yes, if only said car had some other benefit, like being cheaper to run and maintain. Imagine if the same car had more than enough range for 95% of people's travel and could be filled up at home for a fraction of the cost. Finally, ima
456.
by cgrealy 7y ago
I honestly expected this article to be another "damn kids, get off my lawn" post, but reading it, I 100% agree with the author and I'm kinda horrified to see some of those scenes. I'm lucky enough to have been to some of
457.
by cgrealy 7y ago
No idea.
458.
by cgrealy 7y ago
It depends on who you are meeting with. If it's a FOSS collab, this seems like a reasonable stance to take. If it's in a professional capacity, eh, I honestly couldn't be bothered hiring or working with anyone under these kin
459.
by cgrealy 7y ago
As always, the answer is highly dependant on a number of factors: - How complex is X? - What expertise do you have available for X? - How critical is X? But in general, if X is not part of your core business, only as a last resort. 99% of
460.
by cgrealy 7y ago
Damnit, I really should have remembered that :)
461.
by cgrealy 7y ago
I'm interested to hear what your rationale for this is. When you are writing code, you generally know what it is you are trying to achieve. When debugging code, you're frequently trying to find out why a problem is happening in
462.
by cgrealy 7y ago
Debugging code is more difficult than writing it. If you write the cleverest code you can, you are, by definition, not smart enough to debug it. /shamelessly stolen from somewhere I'm too lazy to look up.
463.
by cgrealy 7y ago
Sorry, yes. That's exactly what I meant.
464.
by cgrealy 7y ago
Most people use slack for work. I think it’s a pretty reasonable assumption that not only is everything kept forever, but that it’s not “your data”, it’s your employers.
465.
by cgrealy 7y ago
"We didn’t have a version control system. Surprisingly, we went all the way to Quake 3 without one, then we started using Visual Source Safe." That is both impressive and terrifying. I'm old enough to remember when I first st
466.
by cgrealy 7y ago
> Always use a Version Control System Please tell me no-one is writing anything without a VCS in 2019. > One commit per change Amen, brother. > You're responsible for the use of your code That's a tough one. Code is a too
467.
by cgrealy 7y ago
A lot of people in this thread have argued that named parameters mean you can add bool params to functions. e.g. getUserMessage(userId, fullMessage=true) While that can help, I'd still argue against it unless your language has some mec
468.
by cgrealy 7y ago
I cringe whenever I hear someone talking about "what pattern to use here" (I cry if the answer is "singleton"). Patterns are a way of describing code. They are meant as a common language to use when explaining a codeba
469.
by cgrealy 7y ago
Again, choosing not to switch off a device because you're "addicted" is not the same as "can't turn off". And every device has an off switch. At the very worst, you either unplug it or don't charge it or t
470.
by cgrealy 7y ago
While this is a clever little pattern, I'd argue that if you have a method of class X that can only be called from class Y, that is a code smell.
471.
by cgrealy 7y ago
The same reason it's the current largest economy.... a happy accident of history and geography. Every other major economic power was devastated after WW2. Because the US was geographically isolated from the major theatres of war, it wa
472.
by cgrealy 7y ago
My point is that IT doesn't (and shouldn't) need to know about employee pay. Extending the Employee class to HR, Accounting and IT is a bad design. You're violating ISP here. The Employee class can implement IThingThatGetsPai
473.
by cgrealy 7y ago
I'm not saying that old code cannot be bad, merely that it's not bad because it's old . Your approach seems like the right one.
474.
by cgrealy 7y ago
6 years is still young for code. My current employer has code that's 13 years old. My last had code that was nearing 20. And there's nothing wrong with that . Old code isn't "bad". In fact, it's almost certain
475.
by cgrealy 7y ago
Not everyone works in "The Valley". The vast majority of software is not written with that amount of churn. The end user doesn't care about the quality of the code, but you can be damn sure they care about the quality of your
476.
by cgrealy 7y ago
Some constructive criticism: abstract class Employee { // This needs to be implemented abstract calculatePay (): number; // This needs to be implemented abstract reportHours (): number; /&#
477.
by cgrealy 7y ago
Fair enough, my comment was a bit snarky, but I feel that pointing out the author failed to back up his arguments is a legitimate criticism.
478.
by cgrealy 7y ago
ugh, I feel your pain. Have had to use that in the past, it's basically one step up from SourceSafe. The first thing I did at the last company that used it was migrate to git. The good news is that (from memory) there is a tool that wi
479.
by cgrealy 8y ago
If most of your time programming is spent typing, you're doing it wrong.
480.
by cgrealy 8y ago
This is a problem of incomplete specifications. "Make me a tool that extracts, collates and graphs data from this spreadsheet. We just need it to run once this friday" "Done, super fast, slightly buggy python script it is!&qu

More ›