I assume nothing, but a lot of enterprises have fucked places to work.

Its still better than TCS's waterfall :/

#include <unistd.h>
#include <sys/types.h>
#include "some_library.h"
#include "some_logging.h"
//------------------------------------------------------------------------------
// NAME: some_function
// DESC: I can because I use a batshit crazy formatting style normally only used 
//       in military code and device drivers.
// ARGS: -
// RETN: rc - success / error code
// HIST: authored - dev13
//------------------------------------------------------------------------------
int some_function() {
   int rc  = SOME_SUCCESS;
   int uid = getuid();
   rc = do_something_here(uid);
   //------------------------------------------------------------------------------
   // log any failures of users trying to use this.
   //------------------------------------------------------------------------------
   if (rc != SOME_SUCCESS) {
      some_log(SOME_NOTICE, "User %d attempted to do something", uid);
   }
   return rc;  
}

Why would they edit your code when they can just ban you if you don't follow their SJW suggestions?

Well, you could if you wanted to, but that would be overkill, instead try the reverse; mapping all the modules a single FHS structure inside of a project folder.

Read up on fhs, then go in your own direction

You want exactly lz4 compression.

Depends on what you use really. Github is way overpriced compared to bitbucket, but if you start stacking things like Jira and whatnot the price climbs.

Note that the bitbucket pricing model is a lot better for businesses than github as well. In fact most of the atlassian stack is really good.

Slightly more specific link to above: http://www.pathname.com/fhs/pub/fhs-2.3.html

Indeed, "peer review link or it didn't happen"

Peer review or it didn't happen.

Peaked doesn't mean its outdated. Peaked means its as popular as it is ever going to get.

It doesn't take that long to add another if you're already proficient in one. Having more than one language makes the resume look better, and you can do it in your spare time.

Learning more languages makes you a better programmer. Also, since Java has peaked in its popularity already, in 10 years something else will take its place.

You're working on a lot of misconceptions here. Firstly, HR types don't know shit about coding. If the test is out of a book or online and the HR people are looking up in a book to find out what the answer is, then that is a warning sign right there. If you're doing the test during the interview, then it is part of the technical interview. It likely came from someone on the development team or the person giving the interview. This is a chance for you to show off and not for an HR type to waste time and money being clever. Mind that you can also use this as an opportunity to size up the interviewer's skills, as you will likely be working for or with that person.

You're sounding really really pretentious here, and unfortunately this way of thinking is also real common among people who lack skills, so watch out.

1. Weed out the non-coders from the ones that do

   We assume you can code already otherwise the recruiter/headhunter/HR would not have contacted us.

2. Only get the developers that are interested enough to perform their test in a ordered and timely manner.

   I assure you that most developers I interview have yet to ever raise a concern about being tested, regardless of what point they are in their careers.

3. Gather insight about my proficiency for their position

A lot of times it is more about your problem solving skills and creativity, than whether or not you actually finished the problem.

1. I know how to code, and can show it. They can check my blog, my numerous repositories on GitHub, my public sample projects, my freelancing portfolio, and even my fully-working apps and sites out there.

You seem to think a hiring manager has enough time to review all of your stuff. We don't have that much time for you, we're already over worked as it is. Also, I don't know what stuff in your repository is all yours or collaborative or something else altogether.

1. I've already expressed interest in their position. I have a day job, and several side projects: I won't spend a sizable chunk of my free time so they can tick some boxes about my coding skills.

Unfortunately the reality is that there are a million guys from India who will. Take into account that the big companies will get most of those first. Mid sized companies get a few. Tiny companies usually get none. Hence, smaller companies will be easier to start at.

1. No matter how general or specific their tests is, it will never replace the proper way to see if someone fits your position: work with them on the real job, and see how it feels.

Nothing can really do this reliably except for interning, and that is a ridiculous time investment. I want to see if you can solve problems and use your brain, period.

As for your alternatives.

1. Bring the candidate to the office for a day, and work together. They'll get to know the company and its environment, and the company can see how the candidate fits within their team and culture.

Intern for a day? 1 day is hardly enough to learn a stack if it isn't exactly what you already do. However, as it is it would be more valuable than a non technical interview. Some could say you'd also be lowering the performance of the rest of the team through distraction, but overall I think this is viable.

1. Pair program with people from your team for an hour or two (Screenhero works great), so the candidate can learn from them as they learn from him/her.

Same problem as above, also potential confidentiality problems in some cases.

1. Assign the candidate a real feature/bugfix to implement from home, remunerated accordingly. Make them sign an NDA, and both parties will have come out benefitted from the exchange.

This again can work for small companies/teams, but if you're work is unacceptable then we've wasted that money and that time as well as legal's time, so for large companies this just wouldn't happen.

You know, I've found that the better programmers I've interviewed in almost every case started off with a block structured or functional programming language. That said, you should learn C. It's a lot of work, but your low level understanding of things will be significantly better. Python is a decent language too; there is a lot of serious development in it recently, so I would recommend as a complement, but by no means should they be your only language.

Totally possible. Technical interviewers want to see what you can do as well as what you've already done. What your degree is if you even have one is ironically less valuable because there are so many crap programmers coming out of college; however if you were already technically inclined before entering college you're likely to be much much better than those that weren't.

Java is ranked too high. By volume a lot of java programmers are offshore or brought in from overseas. Around here they usually see salary in the range of 60k give or take.

Reverse words in a string is worse... Its more indicative of the skill and style of the person submitting the code for the example. If you look at C vs Java its even more so, (also some of the C code is buggy)

omg I see this so much I pretty much google with -jquery all the time now to avoid that crap.

You would be surprised just how many people with 8 years experience and a masters are incapable of giving an answer other than "just sort it"

Yeah I dunno. The job has me ( a natural introvert ) being forced to talk to people all the time. I'll probably have to find somewhere else to work out go into business for myself.

Being a "rock star" promoted into the "software architect" role; this has to be the most depressing read I've had in a long time. Still good though.

Well, there are a lot of things you could do, but usually the wrong answer is when people say just sort it and stop. It's really a cue to get the developer to show how clever they are, so If we go for a simple linear answer you could just save the highest number you come across. You could use threading, multiprocessing or even a gpu because the problem is parallelizable. You could also make use of a memory map or directly access the device unmounted

1 'column' doesn't have any commas. also, sorting 5 tb would take a very very long time, if it was sorted then it would be at the end or the beginning, which would indeed be trivial.

Yes yes, I've given these interviews before, but the idea is that you help the person along a little if they don't get the obvious traps. My current really obvious one is to find the largest number in a 5 terabyte file, single column csv.

My earliest machine only had 12k to work with, and a lot of that was wasted by the programming language if it was interpreted, so I have to say that this was not always the case to make a call stack with low memory machines. Also consider that many programs weren't even threaded and people were still using machines that couldn't multiprocess for years

Before the peanut gallery starts to come down on this guy, you have to understand why goto was so problematic to begin with. The kneejerk response is "Spaghetti code!", and I applaud you at being able to parrot, however the actual reason has more meat to it.

Way back before the invention of context based returning, you would have to write a bunch of additional code at the end of a block of code in able to go back where you came from. So if you wanted to reuse a code block, you would have to set a global variable (because originally you couldn't pass one) and once you got there, you would have to use that variable to get back, so the best reusable code would invariably end up looking like spaghetti to the untrained eye. These days with functions, classes, inheritance, switches, exceptions returns and whatnot this is no longer an issue; You can write code without generating spaghetti, in fact most languages use it in such limited way that it is impossible. Its use is no more dangerous than using a return in the wrong place.

*edit - "meat more", I just woke up.

Old timer here, you want W3schools.com and for the tricky stuff wwww.quirksmode.com. Most JavaScript tool kits are pretentious and try to do everything. Kits that specialize on things are usually quite good, however I would not recommend using either to start learning.

If you like that, read this one on one of the main systemd developers-> http://www.theregister.co.uk/2014/04/05/torvalds_sievers_dust_up/

Imho, the systemd team are a bunch of arrogant f@ckwads who deserve the flack. Eventually they may make better code later in their career, but the world shouldn't be using their code right now.

Conversely, if you aren't already very familiar with both you likely aren't writing assembly to begin with.

#include <stdlib.h>
#include <stdio.h>
int main(int argc, char *argv[]) { 
   printf("Greetings program!\n");
   return 0;
}