serif makes my eyes twitch.

i agree that i use documentation over function names but sometimes i need a reminder to check. writing a string and returning count of bytes written is not really useful with unicode. describing inputs and output types are right there in the function definition but describing how the types are used in the function name can provide useful reminders.

ascii_write() and utf8_write() will cause me to pause and actually read the documentation if I have edge cases I need to be concerned about when handling both encodings. if write returns size with either ascii or unicode I can easily mistake size for length.

Static binary analysis is interesting, I wish they had provided some specifics though.

I settled on an editor for the past couple of years but I recommend that you look for functionality first. That is, figure out what you want your tools to do for you then find the tool that does it. If you want to create the functionality or tailor it to your workflow you should find an editor that can be extended in the way you are most comfortable.

If you have the tests before you have the code you can make incremental changes and catch the errors without deploying the whole fucking system. If you never have the tests and you only have code then you always have to deploy the whole system to test. While every developer should know the build chain and the operational scenario not everyone should be setting up and deploying complex system tests. If your continuous integration/deployment does this then you are a rare gem.

I've yet to find one that had a privacy policy that suited me--no guarantees my code wasn't being ripped off.

What do you mean by "online"?

After I started interviewing candidates with 3x my experience I began to feel comfortable with the progress I was making in my career. Most of my challenges are language agnostic and generally focus on problem solving. Sometimes they are based on concepts like asymmetric encryption but never at the implementation level. There are no right answers just less wrong ones. Most candidates don't even bother taking a shot at a solution despite my urgent pleading to do so. I have never turned down a candidate that has tried to answer all of the questions so far, even if they are just borrowing with popular solutions.

Haha, yah windows users are in desperate need of decent command line tools.

Get-Random -Count 32 -InputObject (65..90) | % -begin {$aa=$null} -process {$aa += [char]$_} -end {$aa}

So only use it to give you 32 random characters? Pretty much any 32 characters will be a better password than you have now.

openssl rand -base64 32

ipython? honestly, parsing ascii pipes for data types gets annoying after the first hop

Whatever I can automate with clang-format or autopep8. Style is mostly a distraction when it's inconsistent. With modern editors and autoformatters that can do a better job than I can, I can focus on meaningful edits.

I had a coworker once show me a Emacs feature where it would go to the source code in once buffer at the symbol break in the gdb view. Sounds pretty awesome, would love to see that in Sublime.