I had the pleasure of sitting in on the first public Productivity in Tech round table discussion. It was a fantastic experience, huge thanks to host Jay and to the rest of the crew!
Oh hey, I made a little game with Unity 2017. Check it out!
I’d make it open source, but I used some paid assets.
I’ve been doing a lot of research on LINQ for episode 6 of the Coding Blocks podcast and I was a bit surprised by what I came up with.
I had originally thought of LINQ as a feature. I had heard the parable of the guy at the white board, writing what they thought code should look like and then worked backwards on how to get there. This makes sense, but what surprised me was just how much of the building blocks were already there.
I wrote a blog post about it over at codingblocks.net, so go check it out: What’s So Special About LINQ?.
I put together a collection of audiobooks that get mentioned whenever the discussion turns to “reading”.
Unfortunately there aren’t many books about code, but there are some for the infosec crowd and even more for those with an entrepreneurial bent.
Many applications require customers (don’t call them users!) to sign up with a username or email address to use the service.
If a user mistypes their credentials, security best practices dictate that an error message be displayed which informs the customer that there was a problem WITHOUT revealing whether or not the username was found.
I’m still putting together my 2013 goals, but I do know that one of them is to launch more sites.
I’ve been doing this whole internet thing for a long time now, I really aught to have more to show for it.
These types of posts have been done ad nauseam, but I’m putting together my own short list for a presentation so I thought I’d share.
They’re not such a big deal in the grand scope of life, the universe and everything, in fact, these are far from the worst missteps you can take in programming.
However, seeing these same problems year after year drives me crazy. It’s like fingernails on a chalkboard.
It makes my soul hurt.
I had an easy time with this one, which makes me feel a lot better about all the ones I had problems with!
No fancy-pants recursion or math short-cuts here, just a straight forward logic problem. The only “trick” here is to realize that since a <e; b < c, we only need to check values of a and b up to 499.
I’m sure you could whittle that number down by crunching the numbers, but it’s good enough for me!