500 karma · joined June 11, 2012
https://www.gdcvault.com/play/1022094/JPS-Over-100x-Faster-t...
Then the usage of auto was expanded to help when writing generic code.
I think both of these cases are valid uses of auto, but people seem to have run away with it and will literally use it for statements like auto i = 0;
As a professional C++ coder, I personally don't have a problem with auto (or var in C# for that matter) but I'd prefer people use it where it's useful rather than for every little thing.
Note: I actually had to type the space after 'C' in the first search string, otherwise the results seemed to be things that contain the letter 'c'.
Is there any way to get hold of what you've done?
You can rename a file when it's open. And once it's renamed, you can delete it.
You can't simply brush aside the parent's comments because you don't agree with them. A potential rape situation, or a lost and frightened child are very valid, and very real examples of how having a phone could help.
> Cellphones have made people into helpless, scared sheep.
You realise that people can be scared and helpless without being sheep, right? You also realise that simply being able to contact someone can remove the fear and helpnessness?
I've noticed that some developers rely way too much on tools to do their job and they just don't spend a lot of time thinking. Think about the big picture as well as the details. Think about how your code interacts with its surroundings. Think about what you know to be true at any given line (and write an assertion), and whether or not that thing may ever change. Think about what every line means in isolation, and what it means to the surrounding code. Think about the names you give things.
Maybe it's because of my age, but when I started there were barely any tools to help. Even syntax highlighting wasn't readily available. Debuggers were pretty crap, or didn't exist at all. The best thing we could do to prevent bugs was to really question every bit of code. "What does this line do if x is not what we think it is?", "Can x ever not be what we think it is?", etc
I feel like a lot of developers today don't think enough about what they're doing, and care too much about their stack and their tools. Instead of moving fast and breaking things, perhaps instead try moving carefully, and try not to break things.
"The most effective debugging tool is still careful thought, coupled with judiciously placed print statements" - Brian Kernighan (replace print with assert for my interpretation!)
"All of this is pure garbage. Is Intel really planning on making this shit architectural? Has anybody talked to them and told them they are f*cking insane? Please, any Intel engineers here - talk to your managers."
David Woodhouse replied with:
If the alternative was a two-decade product recall and giving everyone free CPUs, I'm not sure it was entirely insane."
The rest is written by Linus, with all further quoted segments being something David Woodhouse wrote.
> "the user interface is horrendous"
The user interface is perfectly clear if you know how to read it.
I wasn't as unhappy as you sound, I just didn't see the purpose of it (working) anymore.
And so I decided not to do it anymore. Instead, I've decided to buy a small amount of land, live sustainibly, start a market garden, and spend much more time with my family and integrate with nature more.
Life isn't bad, but it sounds like you're stuck in a rut. Perhaps you just need to find your passion, and make a plan to transition from where you are now, to where you want to be?
Kids will break it no matter what it's made from. That's why I think cardboard is a great choice because it can be fixed easily, or even just replaced for free in most cases (old delivery boxes, or the selection of free boxes you get in supermarkets, etc).
Not to mention kids can easily draw on cardboard, or paint it, etc.
My first job was writing COBOL on an IBM 390. I hated it at the time, but I realise now how many important lessons I learned from it. It wasn't trendy, but it was worth doing and I'm glad I had the opportunity.
HKEY_CURRENT_USER\Control Panel\Desktop\MenuShowDelay
And as for game consoles, both Xbox One and PS4 uses an AMD. Only the Switch uses NVidia.
Even official open-source releases like the Quake series still require you to buy the original game in order to run them.
I'd agree that it's sloppy coding, but I can also see it from the original developers point-of-view. Why check something you know isn't going to change?
I don't see the problem in an alternative notation if it's easier to read (I don't know if it is, I've never used the app).
If software developers don't value software, there is something very wrong with our industry.
I'm currently looking to get out of programming after 17 years because I'm tired of politics and bureaucracy. But anyway, on to your question...
I can't tell if these were signs of an on-coming burnout, or if I was already gone by then and just didn't realise what it was. But for me, I started to get angry and frustrated, quicker and easier. Sprint meetings annoyed me, daily stand-ups seemed pointless, interruptions always came at the wrong moment. I started to believe my own hype and went days without doing any work what-so-ever because I knew I could still do more work than my colleagues if I wanted to. I used to moan about my employer all the time and would often find myself saying things like "this fucking company...".
All of those symptoms probably have nothing to do with burnout per-se, and were almost certainly a result of a complicated relationship with a co-worker and a lack of credit and respect by my employer. Nevertheless, I believe that period changed something fundamental in regards to my thinking about programming, the industry, and perhaps life in general, which has led me to want to get out (of the industry, not life) as soon as I can.
I think what I'm trying to say - and having some trouble conveying - is burnout can come as a result of some other thing that starts you on the road of questioning if this industry is really what it's cracked up to be. So perhaps instead of looking out for potential signs of burnout, look instead for changes in your attitude. If your attitude is becoming more negative, you need to change something quickly or you’ll probably end up “burned out”.
Or maybe I’m just rambling about something that most people wouldn’t describe as burnout…