277 karma · joined April 17, 2017
Not buying this...
His father should have told him that he was taking ownership of his company for the loan. The fact is, the guy loaned him $20K, had him sign "paperwork" and didn't tell him is the issue here -- pretty sure right there what he signed was a loan and sales of 90% of the company.
I've read Siver's stories over the years. Entertaining and certainly one of the Ruby guys to listen too... but this is just a bit of a stretch to say "I'm not mad at my Dad." -- he should have been furious unless he knew and this is just another one of Derek's "stories".
Dad sounds like he wasn't forthcoming with what Derek was signing -- or maybe Derek knew and needed a good blog post?
I'm not sure what the value of this is.
Assange was a useful idiot that got played OR he was willing and just good at acting. Either way, WikiLeaks is not our friend.
My issue with this whole WikiLeaks thing is that they are clearly a Russian operation that posed as a "truth seeker" early on and then started to steer their operation 100% at damaging the US. If you're truly a journalist operation, you'd do more to publish and "seek truth" in other countries. You won't find a single story about Russia that's damaging.
Bottom line for me? I think the US believes he's a Putin sympathizer. Or worse, he's a Russian asset.
But for me these days, there's very little difference between stacks as to "what's better". For me it's mainly "best tool for the job and who are are your carpenters?"
But these days, NodeJS seems to be the right choice for many of these jobs and it's hard to sit here and knock it. Why?
Unfortunately, Rails suffers from what a lot of other Web stacks suffer from -- the browser requires some level of JavaScript marshalling that all the other stacks have transform to. When you can code on the server and on the client in terms of the same language. It just makes the process cleaner and far more manageable. When an object on the server is the same as the one on the client. Your life just becomes a little less stressful.
And I love other stacks. I'm a Python fan.
But It's really hard to not embrace NodeJS when you've got developers who work on the frontend (Maybe in React, Vue, etc.) and server developers who are on NodeJS and they can speak together, moreover, work within each others codebase and not kill each other.
That doesn't mean Ruby is a bad stack, it just means like all the other stacks, you have to move data between the backend and browser and it's "Oh, I need this change on the server, I'll have to wait for..." -- no, you can do that, if you've got the ability to code in JS, and you're a fullstacker, you can do both.
With Composer that changed and it appears now they are doing a much better job of standards and changes to the language.
With that said, it's not a concurrent system. It's blocking and that's a problem for modern Web languages.
I do think PHP growth is on the way down... but slowly.
BUT...
When the client is 100% JavaScript on a browser (which nobody is avoiding) and you're marshalling JSON around and JS Objects, any other stack outside of Node is going to have to do the "JSON object" dance, which we all take for granted as "no biggie", but matters when your code base is spending 20% of the time doing that dance.
Node's also super fast and the community is massive. Not to say Python isn't another good choice but you give up performance in that choice.
Again, this is a "Web stack", so I'm assuming web client talking to the server. Right now, for me, it's Node / React.
I worked for a mini-computer company in the 1980's that ported Oracle (I'm thinking the version stamp was 22.1 when I was there from 1986-1990). It was one GIANT mess of standard "C" with makefiles that were in some ways larger and more complex than some of the actual kernel code it was building!
Took 24 hours to build the product... lol
So yeah, I've focused on the executive level, CTO, VP, etc, But with that, you have to either give up coding and just manage or go to a tiny company to be the "key player", but then you're typically at a smallish company with little to no funding. I've been doing that lately, I'm at a small start up running engineering, but I'm an "employee", not a founder.
There seems to be a clear bias with VC companies against someone my age and background. Not to say I don't have a network I could probably work and get funding, I could. But I also wanted to get back to square one and work with people again and NOT have to deal with things like Healthcare, stock options and "hey, that person needs a week off because their cats sick." -- I'd rather just CODE and learn more, enjoy the art of buildings things without the pressure of an investor looming over you.
I've made enough money to be comfortable, but I still need to earn a living -- I haven't made that "FU" money and my wife laughs and jokes that for as much success we've had, even if I did get the "FU" money, I'd still want to work 70 hours a week and write code... ;-)
About your Skype coding comment. Yeah, new trend is to "pair" with someone online in an interview process and go through programming challenges. I'm OK with that, but I don't work well that way. I work better in a situation where I can think and spend the time myself on the problem. My brain isn't wired for "fast and rapid", it's more of a "trial and error" until I get it working, then later on optimize and make it better. I do terrible at that first pass, always been more of an interactive developer who starts with something that works and then over time perfects it. That style SUCKS on a pair programming exercise.
I had a three year earn out, finished that and decided to get back into the workforce and get a job at a senior or above level (thinking Director, Manager, etc). Guess what, not only did my age hinder me (I'm 53), but my lack of CS math background seemed too in an interview process. Various interviews had me solving what I consider not only impractical, but almost silly puzzles / math problems that not only didn't apply to the company I was interviewing with, but didn't apply to anything real-world -- it felt like it was a way to:
- Weed me out because of my age - Make the company seem like their vetting process was "Google like" and "trendy" - Make the interviewer feel entitled or the company be "elite" in their process
Part of me realizes that some of this is to see how well someone problem solves. I get that. However, I had one interviewee actually bungle up the questions, in fact, I had to point out at one point that it appeared that they described the problem wrong. When I got my answer wrong, and then asked for the answer, the interviewee clearly realized he setup the whole problem incorrectly.
Oddly enough, this is the part that bothers me the most. I've been asked many times for my GitHub. I have lots of solid examples to see my work. I've also been asked to do a programming challenge, which almost always I nail 100%. But it's always these "trap" CS challenges that I feel are used to eliminate someone based on either HOW they solve it or a way to justify them out and not hire them based on other factors (age, fit, etc.)
I actually had one that was a whiteboard session where the CTO asked me to solve the problem on the board "using code of your choice", so I stated, "Look, since I know multiple languages, I'll use pseudo code to walk through the problem and explain the answer"
When he described what he wanted me to solve (badly I might add), I wrote the pseudo-code on the board and described the problem as being solved by using regression. Which was 100% the right answer but because I chose to use pseudo-code not say, Python or JavaScript -- he told the recruiter, "he couldn't solve the problem I was looking for him to solve." When pressed by the recruiter about the solution, he gave a link to the problem in his Github, which of course was verbatim of what I described but in Python -- using regression.
What I've learned from this is that I should contract and consult. Most of these smaller companies want what they want in the way of an employee and are seeking the 10X developer, culture fit and someone in their own age group...
Age discrimination at its best. Cap it at 45?
How many people over 30 (45 in the US) are trying to retool and get educated on programming?
Yeah... so I'm out. Where's that card going to fit into my iPhone?