arms way too open, body weight on both legs, right arm should not be bended, distance between two feet is way to long, left hand should be pointing up, etc.
4,486 karma · joined June 11, 2015
arms way too open, body weight on both legs, right arm should not be bended, distance between two feet is way to long, left hand should be pointing up, etc.
And I tried to tell my kids. And it failed mostly.
But in the long run (a decade), what is exceptional and proprietary will become common FOSS. And everybody will benefit.
Sidenote: I code fluid dynamics stuff (I'm trained in computer science, not at all in physics). It's funny to see how the math and physics deeply affect the way I code (and not the other way around). Math and physics laws feels unescapable and my code usually have to be extremely accurate to handle these laws correctly. When debugging that code, usually, thinking math/physics first is the way to go as they allow you to narrow the (code) bug more quickly. And if all fails, then usually, it's back to the math/physics drawing board :-)
Side projects requires passion, not discipline, not effort, just passion. And that's what I'm looking for. When you like what you do you're generally good a it.
Now, I have hired people who don't have side projects, of course, they're not that common but not rare neither. And the side project question is sure not the main question. But that's a cool differentiator.
Moreover, questioning people on their side project is always more fun for them.
And of course, people with side project sometimes day dream so you have to keep them busy :-)
And having a github repo is a 15 minutes job. And most of the time, nobody will care about your side project. It's not like your marketing yourself. As I have said, I don't care about the stars. Just looking at what you do on the side, what interests you in a domain that is not far away from your job.
And side projects are always cool: I have interviewed people who were working on their game engine, planet trajectories, web sites for friends, playing with machine learning, writing little tools like Javadoc,...
Sounds great but... I have migrated a big cobol codebase several years ago. Knowledge stored in the experts is 1/ very wide 2/ full of special cases that pop up only a few times in a year 3/ are usually complex cases involving analysing data, files which are on paper, etc. I strongly doubt an AI will be able to spot that.
The knowledge that usually misses the most is not "how is that done", because spending a few hours on COBOL code is frankly not that hard. What misses is: "why". And that is usually stored in laws, sub-sub-laws, etc. You'll have to ingest the code and the law and pray the AI can match them.
So in the end the AI will make probably 50% of the effort but then you'll need 150% to understand the AI job... So not sure it balances well.
But if it works, well, that's cool because re-writing cobol code is not exactly funny: devs don't want to do it, customers do it because they have to (and not because it'll bring additional value) and the best outcome possible is the customer saysing to you "okay, we paid you 2mio and the new system does the same things as before we started" (the most likely outcome, which I faced, is "you rewrote the system and its worse than before). So if an I can do it, well, cool.
(but then it means you'll fire the team who does the migration which, althgouhg is not funny and not rocket science, requires real expertise; it's not grunt work at all)
If there's no github project, I ask the candidate what website, web communities he watches/participates in regularly. I check if they are related to programming or building software (bonus point if you read HN :-)).
Both are good signs that there is an interest in the job that goes beyond paycheck.
wandering the web to find an exploit is way beyond my spare time.
it sounds like "guy felt down in a volcano, but fortunately, he had a life vest"
"For conditional probability, the hypothesis is treated as a given, and the data are free to vary. For likelihood, the data are treated as a given, and the hypothesis varies."