I am a long time lurker on stackoverflow. There was a time I was stuck on an obscure error for so long but finally light shone when I found an answer to that problem on stackoverflow.

Overjoyed, all I wanted is to leave an upvote for the answer; before I realised that you need a +15 reputation before you can do (I know I am late in this game)

So I worked my way to that 15 and it was a tedious one. Stackoverlords deleting my answer, voting no to my edit and reverting another over petty reasons

I fought back by flagging my deleted answer with my reasons and alas the community backed me up by upvoting my answer (which was revived),the original answer poster approved my edit and @me a thank you comment. I was elated

And it is today, I got my +15. That I could finally pay back and upvote the answer from my benefactor

My favourite memory from 2016 :D

RPi 4 is hard to get your hands on it seems.

Really debating buying it though, 4 GB is enticing, but I just don't see a place for it. I have a surplus of machines which are much more powerful and accessible (Display ports - not mini HDMI)

And let's not forget the sub-2GHz clock speed. My desktop goes to 5, and my server isn't far behind. And my laptop isn't far behind that. And my other laptop isn't far behind that. But this new Pi would be far far behind that.

Not to mention the ARM architecture. There have been leaps and bounds made since the Pi first came out in terms of support for ARM (Most certainly fueled by the Android craze) but it still isn't x64, is it?

If I were 13 again and I didn't have all of the toys that I do now, I would be elated at the launch of the Pi 4. But as it stands, I don't see a use for it. Maybe nostalgia.

I'm going home!

For the past six months I've been on a contract that has kept me away from my family. On Saturday I will finally be moving back home. I'm elated to be seeing my family again, but I'm scared because I don't have a new job lined up. Wish me luck.

Started writing a parser for moonscript. Because I want to do my own syntax highlighting and error support.

I'm sorry, but was this supposed to difficult? Every article I read claimed this was gonna be some impossible feat of herculean effort. I half dreaded it, the other half was kinda elated.

Only it didnt live up to the hype. The tokenizer is a glorified character stream. The lexer is little more than a tokenizer, and the "most complicated" bit is nothing but a fancy transformation of the token output into a tree.

I'm completely to new parsers proper and semantic checking and maybe that's why it seemed easy, but I dont see what all the forewarning in tutorials were ever about.

Finding a bug that wont trigger an error but will deliver incorrect results, but only in certain circumstances and has only come apparent after the site has bern live for 6 months.

You turn in to a detective trying to determine what triggered the wrong result, what the client changed/added/edited in the cms and work from there.

After much investigation it dawns on you, you then find the bit responsible in your shit code and fix it.

Then feel extremely elated at how cool you are, but no-one gives a shit.

Back to work.

That’s why I play bass guitar, do some cool licks on stage and its instant gratification, glad I have that... and devRant community.

maybe I should learn how to code properly as well.

Every time there is a new project, we programmers swear to ourselves that we will code it better this time. We get elated that we do not have to deal with the tech debts piled up in the old module.

Missing my train into work this morning, couldn't of been any more satisfying