I had a coworker who would sometimes not create a method as being static to the class and would therefore need to create a default instance to call said method. “It’s domain-driven design.”
I had a coworker who would sometimes not create a method as being static to the class and would therefore need to create a default instance to call said method. “It’s domain-driven design.”
The price and quality are so hard to beat.
For me it all depends on how often a project changes. If it’s constantly in flux, I don’t bother remembering any of it because I might not be the last one who touched it. The more you try to remember everything, the more wrong you become due to the successive work of your coworkers.
I’ve had mine on vibrate for years. Texting doesn’t trigger it, only calls. It’s been great. I look at my phone only when I’m ready to look at it.
When your management judges teams by lines-of-code written.
I’m just going to start pronouncing it “The Gulf of MEH-he-co”, really laying on a heavy Spanish accent for clarity.
Is that a water dispenser? I need something like that.
That’s something I haven’t heard before about the memory safety. In what ways is it not memory-safe?
I remember Click (2006) being very sad, but I haven’t watched it in a long time.
The episode “The Sign” of Bluey, the end.
The runoff voting downside is incorrect, the “drag the voters up to yellow and watch how it makes red win” example. This is not “see how making yellow more popular makes yellow lose”. It’s actually “see how making red more popular than yellow makes red win”. The movement of the voters is not for yellow, but for red and yellow in a way that gives more voters to red.
There is no way for yellow to be the only candidate to get a boost of voters in the demo. If there were, it would only demonstrate further that yellow would still continue to win.
Runoff voting is the way.
Everyone wore black.
I don’t know how to get everyone I know to really understand this. Every time I bring it up in conversation, the other person just puts their hands up and explains that they’re powerless to address it, so it’s not even worth talking about. I don’t know how to respond to the apathy.
Yeah, if it’s purely a Sqlite implementation detail to create temp files, that’s on them to own and fix. I thoroughly dislike that the files are obscured from users.
Oh, I thought that the temp files were named by the user. If that’s not the case, that these are not databases created specifically by McAfee in the temp directory, then I’m not sure what the appropriate solution should be. Obscuring the file type and how the file is used from users is still a bad practice.
I love how the solution didn’t involve changing the prefix to “mcaffee_”. Now users don’t know who to blame. Great. That’s so nice of them.
It’s time that we admit to deaf people that music isn’t real. The joke has gone too far.
Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn’t be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.
I’ve found that one of the best things to do when making a library for something that is going to have a web interface is to first have it work in the terminal. You can much more quickly play around with the design and fix issues there instead of having to work with a more complex web interface.
You just create a simple menu system, like
input("1: Feature A\n2: Feature B\n>")
and just start trying out all of the different scenarios and workflows.