I actually like it better this way, as I wouldn’t have to reach in as far to turn it on. I think having controls there and the spigot on the corner on the left would be best, though.
(they/he/she)
I actually like it better this way, as I wouldn’t have to reach in as far to turn it on. I think having controls there and the spigot on the corner on the left would be best, though.
One serving of peanut butter
Every day in standup
If you want to improve your problem solving skills, I’d suggest solving actual problems. Data structures and algorithms can be very satisfying in their own right, but the real value is in taking a real-world problem and translating it into code.
It also depends what you want to do with your knowledge. There are domains that are deeply technical and require a lot of the things you’ve mentioned, but they also tend to be pretty hard to break into. A lot of software is not so deep. Any software project will have need for good domain modeling, architecture, and maintainability. Again, these are things best learned through practice.
Armed Bear in the same vein
C shell
Hmm… I admit I didn’t follow the video and who was speaking very well and didn’t notice hostility that others seem to pick up on. I’ve worked with plenty of people who turn childish when a technical discussion doesn’t go their way, and I’ve had the luxury of mostly ignoring them, I guess.
It sounded like he was asking for deeper specification than others were willing or able to provide. That’s a constant stalemate in software development. He’s right to push for better specs, but if there aren’t any then they have to work with what they’ve got.
My first response here was responding to the direct comparison of languages, which is kind of apples and oranges in this context, and I guess the languages involved aren’t even really the issue.
I think most people would agree with you, but that isn’t really the issue. Rather the question is where the threshold for rewriting in Rust vs maintaining in C lies. Rewriting in any language is costly and error-prone, so at what point do the benefits outweigh that cost and risk? For a legacy, battle-tested codebase (possibly one of the most widely tested codebases out there), the benefit is probably on the lower side.
Having tasted a few dog foods and treats, I agree.
I’m guessing the pumpkin spice isn’t too strong either, but dried pumpkin is the first “flavorful” ingredient, at least.
But these do have pumpkin in them.
My dog goes nuts for pumpkin puree, but hates greenies, so I dunno
I got super sick from this. It probably didn’t help that I was trying soothe my upset stomach with more peanut butter.
im multisexual which means i like multiple sex
It always grates on my nerves to read laypeople’s opinions of how software development should happen. So much unfettered stupidity.
I can finally finish my Gyro Zeppeli cosplay
This is my perspective on a lot of art and music. If something is universally hated, I want to know why it is and if I can find any redeeming qualities. A lot of my favorite things have that characteristic of doing something very specific extremely well but being generally unlikeable.
Switching to Linux or… maybe?
Either #2 or #3. /usr/bin and /usr/local/bin exist for that purpose, but some people prefer to keep personal scripts and such in home, maybe as part of a dotfiles repo or something, and so just add ~/.dotfiles/scripts or something to PATH.
Javascript and not Coq?