Also, doesn’t the jetbrains license let you continue to use the version that was the latest as of when your license ended. It’s a small difference, but also kinda huge.
Also, doesn’t the jetbrains license let you continue to use the version that was the latest as of when your license ended. It’s a small difference, but also kinda huge.
I think it needs to be 5 or 8 so it’s a number from the Fibonacci scale.
It is also important that there is no possible way that a story point can meaningfuly represent time.
I know you asked about memory, but the computer I just assembled had a 750watt power supply. As an American I think we should refer to it as a “one horsepower power supply” instead.
I feel like most of my googling of simple code is because I know what I’m trying to do, but I don’t remember the correct function name and or language structure for the language I’m currently using.
Clearly this is what we call “self documenting code”.
On my current team, when we were trying to choose a style, my only input was “any style that can be checked/applied with a git commit hook.”
I get some people prefer reading code in a particular format. Let them configure their editor to apply it, but let’s keep the version history in one unavoidably consistent style. Pretty please.
Correct me if I’m wrong, but I’m pretty sure some compiler settings can change this. I have a fuzzy memory of a bug that went away when compiled with debug flags enabled and the difference was that unassigned variables were being zeroed vs not zeroed.
Since my last comment, I learned that my local library has a few machines and a serger that you can reserve time on. I think that is going to be how I avoid buying my own for a while, and possibly a social setting I may learn from others.
Curiously, what sort of fights do you have with your sewing machine? I just started getting into sewing a couple months ago. I’m currently using a borrowed machine and haven’t had any major issues yet. I was hoping to buy my own soon and wanted to know if there were specific features that commonly cause problems.
I like puting my prototype code in namespaces like “garbage” “trash” “throwaway” etc to emphasize how unfit for production. I’ve no concrete evidence of it’s success, but I like to think it dissuades other team members from using it where they shouldn’t.
I like pronouncing numpy so that it rhymes with lumpy just to make people uncomfortable.
I suspect a press is your best option, which is really a slightly more controlled variation of your hammering it with a screwdriver effort.
s/ice/hot/g
Glad to see Fairytale of New York here. I was going to make the comment if I didn’t find it.
With lyrics like this, what’s not to like:
You scumbag, you maggot, you cheap, lousy removed. Happy Christmas, your arse, I pray God it’s our last.
Might also add: greedy
One side: 80 grit The other side: high gloss
I’ve given up on food delivery. With the all the fees and tips and shit to wait who the hell knows how long for food to show up colder than a penguin fart.
It’s just not worth it to me anymore. Why would I want to pay for that experience? I can make less disappointing food quicker for less money.
As a started reading I thought “Hmm, some of these remind me of [coworker x]”. As I continued I realized all of these remind me of [coworker x].
I might have to turn some of these into bingo cards.
Yeah, I wish I knew this about a year ago. Thanks.