thegigaraptor

It’s not an FPS, but Tokyo Jungle is worth checking out if your looking for something like this.

> Git forces you to write your commit message at the end of your coding session

You could create a commit and —amend work into it if that is the route you’d like to take.

Peer Reviews (PR’s) are not a personal attack on your competency, but constructive criticism and if they are genuinely toxic reviews, speak up and point it out to another senior or manager.

I use an external keyboard, but I can empathize with people using it as you normally would. I've experienced the dead spacebar and rarely use the built in keyboard.

I've been on both sides of this, having completed and reviewed interview tasks, and I have to say it's absolutely crucial.

As an interviewee, it gives you a glimpse of what work will be like once you come on board. Are the requirements solid or loose? Is testing required or even mentioned. These and other things can give you insight into how the business interacts with engineering.

As an interviewer it's hard to take resumes and unfortunately even GitHub profiles at face value. I've personally had code taken from work put up on a colleagues personal GitHub. The coding task is also not a sure-fire way, as I've seen those taken from online tutorials. The real magic is in the tasks code review.

I'm not saying this is how it works everywhere, but given the task matches the deliverables asked and we make it to the code review stage, it becomes less of a tech interview and more of a glimpse into the social skills of the developer. PR criticism is a daily occurrence and getting an opportunity to test these waters prior to fully committing to onboarding a developer.

I would like to see this applied to a dating app. Some people turn into complete monsters when faced with rejection.

I almost signed up for that site, only so I could respond to that article. Why kill the platform that can be accessed from devices available to everyone, everywhere. Cross platform support on applications is taxing, even with an engine like unity that offers multiplatform builds, if you want to get a product in the hands of the world, you build it on the web.

I used to scan potential candidates Github repos but a recent job changed all that for me. A coworker was struggling at standup to handle a "deep get" in a JS object. I wrote a small function in five minutes and sent it over chat, thinking it'd unblock him and he could continue his tasks. He preceded to create a repo and added tests to the code and claimed it.

I imagine that in time, someone will look at that code and use it as a consideration for his employment and be just as disappointed in his output as I was. You may hate it but I love white-boarding with candidates. It's not a binary pass/fail exercise but a look into how a person approaches solving a problem and handling on-the-spot pressure. Sometimes things break in prod and the pressure is on, I want to work people that do well under that pressure.

I hope nobody uses this article as ammo against TDD. The benefits are not felt immediately but when time comes for maintenance/updates, I'm working on my second port with a company. The first app had fantastic testing and I was confident in the work I delivered. This second app however was led by a developer who "needed to get things done" and I now have to wrap the v1 app in functional tests to validate that I'm delivering a solid port. If the company had enforced better practices sooner, they would have saved the time I'm spending on retesting the original app. This second iteration is test driven, hopefully the next dev has a better experience.

Also testing helps alleviate QA's workload by ensuring developers have not broken any tests and regressed functionality before we hand off to QA.

If you're hacking on an idea or learning, I can understand not testing, but if someone is paying to deliver code, deliver it with tests, period.

People need to take the time to learn JS instead of forcing their understanding of programming upon it.

Testing code. I was completely against the idea of writing more code for my code that "worked". But as releases came out validating everything was in order became a pain.

I wish people would take time to actually learn javascript. I used to see it as a shitty toy language up until 2012. It opened me up to a completely different style of programming.

I came here to post this, you're a great person.

This post fills me with dread, it's come to the point during code review that I have to be sure the shitty devs aren't coping the bad answers from stackoverflow... I hope they don't find this.

I thought the exact same thing.