If you have great ability, do t squander it. Get another job where you can be more effective. Find your passion and your fortune will likely follow.
I eschewed advice like the others give, and I didn’t have to work after 35. Yes I got lucky but I also worked hard and failed and got back up and found a place to succeed.
Big companies are mostly for drones.
It was amazing to see how productive he has been the past few years working on it while also being at Stripe. Not surprised to hear it got to be a bit much.
Unfortunately the only current and sane way to allow users to aggregate their financial data seems to be by having users pull .csv files from all of their accounts (at least where I am, in Canada).
It’s not targeting technical users but it would be cool to add a SQL integration like Stripe Sigma, etc at some point.
Sometimes you see or believe something that others simply can't or don't, and you want to do something about it. Trying to find a (usually narrowly-defined) job that lets you work on these things can be very hard because there usually has to be someone looking for solutions to these hard-to-see problems, and you sacrifice a bunch (more) of your autonomy in the process.
Founding a startup is a great solution to this problem; convince some capital that you have deep conviction and competence to make a material change in the world and put in your own elbow grease to prove it. If you are willing to work hard you don't need very much money to amplify the impact of your own decisions and efforts and the snowball grows, attracting more resources along its path.
It's still really hard to do, but founding a startup remains one of the best ways to prove out a hypothesis in the real world and achieve actual change, while still allowing for a decent income even in the event of failure. It is worth it if the mission is compelling.
- Don't need to know jsx!
- Sane way of scripting puts the script in an object and each component is <template>html</template> <script>javascript</script> <style>css</style>
- Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!)
- v-for looping is saner than reacts mapping
- v-if allows v-if statements without renderIf component or multiple render statements in react (antipatterns boo!).
- two way data binding with vue-model
- native vuex with an index file that holds state sanely, rather than just having state held in each reducer as done in react
- Great documentation!
- Yay !
With age comes maturity. It's allowed me to get along better with my co-workers (so many upper 20s, lower 30s tend to be a bit... hot headed) and I'm not afraid to negotiate. The older I've gotten, the more comfortable in my skin and in my skill set I've become.
If there's ageism I've yet to experience it and I've worked with people well in their 50s doing mobile. It comes down to who you're working for, what your skill set is, timing and, in my opinion, health. You've got to stay healthy and look healthy! Also, I tend to prune my resume, no one wants to see your experience 8+ years ago.
Or maybe it's all luck, ask me in five years what I think when Objc/Swift goes the way of PHP, I might be singing a different tune.
For myself, I still have not decided whether I like JSX or not :) My colleague finds it great, and I like the declarative nature of it, just need to persuade myself to accept it mixed in JS file.
Yes on .bind, but I got used to not having to care about it in Aurelia (and Angular also). Got my fair share of `this` handling in pre-ES6.
And of course, thank you for the links. Bookmarked! :)
The only annoyance is dealing with binding event handlers to items/components in a list. Generally you need to abstract the list item into it's own component and do the event handler binding there.
I don't use .bind() anywhere in my react code.