btmiller

Interesting. Yours is not the first account of a poor interview process with GitLab that I've heard. Even out of Texas, had a few colleagues that were very qualified and came out of it with a poor experience, to the point of changing their mind about wanting to work at GitLab.

Though I think the communication has been pretty clear that developers should stop using % formatting in favor of .format when moving to Python 3. Not so much a deviation, just a migration. Now that there's another alternative, there definitely needs to be some clear communication about what's going to be idiomatic going forward.

Interesting. What do you like about code review things? I personally found it to be lacking. It's hard to dig up comments on branches that have been merged into a master branch and I'd also like to have notes/comments on the HEAD of a project. Right now, they just get perpetually buried. That's where a lot of project decisions end up getting made in my team.

Perhaps we should be using a wiki or some other system, but I'd really love for some more enhancements to code review.

I still get the occasional app update adding support for Touch ID. So I think with hardware features like these, the full potential won't be completely realized until these devices are a few years old and it's near impossible to come across someone that doesn't have that feature on their model of iPhone.

We truly stand on the shoulders of giants.

> got asked questions by non tech-type person who was looking for keywords to obscure concepts as answers and didn't understand my conceptual but keyword-less responses

Simple fact of the matter is that you're going to run into those type of questions by non-technical people at any big software company with which you interview. It's on you to be able to smell out what they want and answer with something that demonstrates your abilities and gives them what they're looking for.

Not to be antagonistically pedantic or anything, but just FYI, Go was definitely not the first to use an underscore to ignore variables.

Awesome! I really like using Gitlab CE. Are there any plans for more code review type enhancements? We typically do lots of discussion on merge requests and often times, certain code features or plans will get scheduled for a refactor sometime in the future. Though, all those comments kinda get hidden away after the branch is merged. Maybe what I should be doing is using the Wiki, but it would be nice to be able to leave comments on the HEAD (i.e. comments on current state of a project).