r-s
r-s on Hacker News
> 58. Trying to police commit history is going to be painful
This has been my experience. Very painful
Smaller smaller world - I work with him today!
Some bigger cities (such as Edmonton, 1M people) still have a somewhat sane real estate market. In Edmonton a single family detached home averages around 450k CAD, while average household income is over 120k.
Carpal tunnel and poor posture causing back pain
In some cases it lasted even longer than that. In 2004 at a Canadian University I was told during the student orientation that CS was not a great choice due to outsourcing.
There is no reason someone couldn't change commit dates and be prolific far earlier than December
Its been one hell of a rough go for Heroku lately.
I think you would be insane to start a new project with them today. Which is crazy for me to say, as I was one of their biggest fans for the last decade.
"Travel K for 20 feet, take the first L and immediately get in the H-most lane"
Some small part of me wants to use vim-clutch and make a manual transmission version of this.
Did Shopify have a choice?
Many Canadians who got computer science degrees left to work for American companies for 2x-3x more money.
Many many years ago I was hired to convert a Fortran app to C. The first person to try it ran it through a software called "f2c". It worked fine - but the code was totally non human readable so it couldn't be extended later, so it provided almost no value in this case.
Thread safety in Rails is a total pain in the ass. So many libraries out there are not thread safe. I have worked with many large rails codebases and there always are gems that somehow work their way in with major threading issues. I think its a legitimate strategy to run rails apps single threaded and multi process. Not necessarily for all apps or workloads of course.
I came to a similar conclusion years ago. Yes, there are examples of applications that have done it, but they often have very elite engineers. Most teams are comprised of various levels of engineers and its extremely difficult to get right.
I work more in web dev now and I suspect the majority of my team does not know the difference between a thread and a process. HN readers may scoff but these are productive engineers who have build some honestly pretty impressive apps and systems.
So does the "PHP4" book on the shelf.
I don't regret it at all, but finding high paying roles can be a little more difficult. Its a tradeoff though, because after a few years at a role its often seen how valuable you actually are so in bad economic times you may be the last to get cut.
I also think generalists get pushed into management at a higher frequency. Not something I am personally interested in, but I get asked yearly at least at every role I have been at.
I am at a similar level / write a lot of Ruby. I have pretty mixed feelings. I do enjoy writing Ruby and echo the low friction between an idea and running code.
However, on very large Ruby projects I have inherited I do see a common flaw of a large (often insane) amount of exceptions being thrown due to type errors. Undefined method blah on nil class. Some of these apps have had 100s of developers working on them of various skill levels. For mission critical code paths I am often the biggest proponent of Sorbet.
While my personal projects involve heavy use of meta programming and taking advantage of duck typing, I have altered my writing style and opinions for large projects.
Part of my frustration with Ruby type system could be explained by the fact great Ruby developers are becoming pretty hard to come by and I have often had to work with developers who are picking it up.
There is a surprisingly small amount of senior rails developers. Many who learned it when it was cool, have moved on. There are so many legit companies making tons of money on Rails stacks with 0 intention on leaving. The market is excellent for rails developers and likely will be for the foreseeable future.
If I find myself having a hard time with a big decision, that almost certainly means both sides have pros and cons and its a very close decision. If one side had way more pros and less cons, it would be a pretty easy decision. If its a very close decision, one side can't be much worse than the other. Flip a coin.
I too have seen something very similar to this. I am extremely nervous all my private repos got compromised. Watching this very closely.
Its not fully clear to me, entire private repos been confirmed stolen?
I did these drills in Canada sometime before 2005 (when I graduated).
2006 Honda Element, manual transmission, AWD. Reliable, can fit an insane amount of stuff in it, consumables are cheap for it. Fuel efficiency is not great but i drive very little. Under 100,000km on it.
I bought it used several years ago and with used car prices surging and vehicles that can be slept in going up in value, I suspect its gained around $2000 of value.
Its slow but has major utilitarian charm.
Rails API + React
Just because after years of being in both ecosystems I am ridiculously productive and don't fall into as many traps. With heroku in 30 mins I could have app deployed production ready with auth, CI, API, database setup, and deployment pipeline.
If this system did not error out and display the error messages to the mall shoppers, it would still be unknown.
I rarely seem to see that on the FIRE forums. It seems like 99% of people on those forums are trying to achieve FIRE, and very little discussion about those who have.
I bought a CPAP off an Amazon seller here in Canada a few years back. I have a large neck and would wake up gasping for air in the night. It was going to be several months to get the sleep study so one day I impulse bought it. First night I slept 8 hours, couldn't remember the last time I did that. Best $600 I ever spent.
Generally the FIRE crowd stays heavy in equities and considers a 3-4% withdraw rate to be safe.
Will this slow down a lot of early retirement plans? Almost certainly. However the market is not 0, lots of these people still have substantial amounts of money saved.