Achieving "Financial Independence" -- when a portfolio meets all basic income needs -- can greatly enable this. The question is why people postpone their own "freedom" in favor of little wins now like trying expensive restaurants, etc.
247 karma · joined September 11, 2016
Achieving "Financial Independence" -- when a portfolio meets all basic income needs -- can greatly enable this. The question is why people postpone their own "freedom" in favor of little wins now like trying expensive restaurants, etc.
I ended up having a job writing programming language tools for a bit. Then there was some graph stuff one time in 10 years. It can come up occasionally. I still find it's something nice to know.
A more realistic example might be understanding the limits of regular expressions/languages and what they can/can't do well. Like the bus conversation I overheard glorifying some "smart" guy parsing XML in a stored procedure using regexes.
http://jlcollinsnh.com/2013/05/29/why-your-house-is-a-terrib...
Don't forget that leverage works both ways; it magnifies the downside as well.
I would like to respectfully disagree. While I am not "old", I'm on my way. I am actually super on-board with simply removing a desire to achieve, and it has made me much happier. But I'm achieving all sorts of things anyways.
The second part of this is the assertion that options to change decrease with age. I have found exactly the opposite. As I gain more experience, build a solid chest towards an exceptionally early financial independence, and go out to find more like-minded but different people I tend to feel like options to change and expand my life start exploding in a way that requires picking and choosing more and more carefully between different things.
What do you think about the reduction of "ambition" as a helpful thing being replaced with a calm but strong "passion" as a potentially more positive alternative?
this is exactly the strategy described at the Google Cloud Summit 2017 relating to how security is managed for their platform ... so it lines up
the FIRE (Financial Independence / Retire Early) movement is showing how most people can do this in a matter of 20 years instead of 40, with those who are highly-compensated doing it in 5-10 years.
20 years of drudgery is much better than 40-60, so I'd say we're at least making progress. The hard part of realizing that goal is the much more difficult skill than the math: establishing what is "enough" for a good life.
"[over-]extending themselves" - risky
"underestimated the tax consequences" - poor; this is a straightforward computation assuming you exercise your rights to get the latest 409a valuation after exercising a single share
We're growing to the point of needing a few distinct components after building a Rails monolith that already had very strong internal boundaries. As we split out different parts to run on different machines, they will either get an immediate re-write, or eventual re-write from behind the service interface.
Many in the Financial Independence community are upwards of 70%. Having a partner with the same goal can keep that savings rate as high even with kids. Otherwise it's not very likely.
Why is this some "special ability" of 20-somethings? I definitely prefer the approach of becoming financially independent and then having 50+ years to do what I want ... seems like having 50+ years to take risk after saving aggressively for 10-12 allows for even more risk/reward tradeoff by eliminating the worst consequences of failure without a safety net.
That said, at the new place that uses Rails we instilled a culture of avoiding stateful updates, preferring hash structures to mountains of object definitions, and use of functional transforms as much as possible.
Then we needed to ramp up to the next level and chose the JVM for writing concurrent code. But we started with Scala as something that has functional concepts baked in since it's "easier to hire for". Not the same, but there are other paths to dealing with lack of Clojure.
Oh, and the Scala only makes up for part of losing Clojure because we actually use it in a similar way to Clojure plus a bajillion type declarations. With the occasional workaround for a compiler bug (I've encountered three in the past 6 months).
Yep, and that part is sad. To me it feels like they're projecting the few arrogant new-hires' attitudes onto everybody. Also, as a female dating in Seattle, there's the all-to-real reality that one eventually picks up on the stereotype of the inflated-ego-Amazon-guy. This happens to the point of people refusing to date those that work at Amazon.
I used to work there, and I feel the same about the stupid egos TBH. I just feel that I choose to apply that assessment selectively rather than across all Amazon employees.
At the end of the day, with start-ups I really value that mix of system and hands-on code. Without initial hires having both, it's harder to build a solid system while iterating so quickly. Amazing people skills are also key.
Over-leveling and bad hire situations are no good for anybody.
IANAL. You cite a concept from contract law, but forget another: frustration of purpose. Saying there is an implied contract that you get access would frustrate the purpose of the original access contract.
It's not just cutting corners in the actual implementation, but also the metrics and management infrastructure for post-release operations.
absolutely true (at least in my case). I'd rather do that than end up on the other end, though. Without stronger protections for employees, I'll hold out for a stronger financial position on my own before I start negotiating hard about "work/life balance".
so much this. Why do companies get to receive all sorts of incentives to hire when candidates they reject walk into other great tech firms, make bank, and generate boatloads of value?
Maybe some should just pay more, too. There are plenty of firms just being too cheap to hire great talent, including some large, well-known ones.
A choice, conscious or not, to dedicate time to raising a child at the opportunity cost of myriad other ways to spend time is not related to ageism at all.
There's also an immense cost to not having CS fundamentals in terms of performance and wasted time; I don't want to pay someone to try and solve a version of the halting problem, or matching opening and closing delimiters with regexes.
The tone of this implies that lining up a new job without first quitting is outdated and negative. From the other side, quitting before having a new position can look irresponsible.
I have never quit a job without another lined up and have done quite nicely, myself. Why ever invest in trashy projects when one can get good jobs quickly and easily?
If you ever find yourself pulling back the curtain of many ruby modules, it's time to dig in and swear as you go.
"Users can comment on files, send them to others for feedback, and upload new versions without having to resort to emailing multiple versions of their files as attachments. Users can take advantage of these capabilities wherever they are, using the device of their choice, including PCs, Macs, tablets and phones. Amazon WorkDocs offers IT administrators the option of integrating with existing corporate directories, flexible sharing policies and control of the location where data is stored."
sounds like a great way to push up prices!
The market would price this in, and then renters would just pay more for that right. Why not just leave the system as-is and let them buy if they choose?
OR there would be people getting kicked out of their rentals in order to avoid the "option" to buy becoming active, and then reactive legislation, and then ... a huge spiral of fights over market distortions that layer on top of each other.