rmb177
Joined 16 years ago
Joined 16 years ago
I'm pretty conservative in my predictions and just think there is a lot of free money on these sites. Maybe that just supports the sentiments of this article and most of the negative comments on this post.
There are certainly cases where I got run over by the steamroller picking up nickels, but in general that's few and far between. A good example is getting trump losing the 2020 election at 90% after the election in November. If you find those types of markets and compound the earnings it's a pretty nice savings account.
I've also been burned by insider trading and vague rule interpretations but at this point, you chalk it up to the nature of prediction markets. I now try to stay away from markets that are more manipulative (e.g. mention markets).
I don't understand the hostility to prediction markets. There are definitely hedging opportunities and we're all adults.
I could go on and on...
https://chrome.google.com/webstore/detail/hacker-news-saw-it...
Edit: Oops didn't really read your question. So this isn't exactly what you're looking for, but I still find it useful.
I would look at the clock every 45 minutes to see that only 10 minutes had passed.
I was one of the lucky ones though because every hour or so, I got to move to another station to hang newly-formed hats from another station on a drying rack that would take them to the next floor.
Pros: Salesforce abstracts a lot of the DevOps/database work that I don't have a lot of experience with and lets me focus on building the applications we need. Much of my current work is building out Lightning Web components, which is your basic JavaScript web development work built on top of some pre-existing components provided by Salesforce. There is a ton of documentation and it's easy to pick up on things you need to learn.
Cons: Salesforce has a lot of quirks to it that you'll become familiar with as you get into it. Build/test/deploy cycles are slower than normal, but they are working on tools to make that experience better. In some ways, their focus on no-code is nice and it's really easy to get simple things done. In some cases though, it feels easier just to write code to get things done, especially if you suspect the feature you're working on will get more complicated over time.
All in all I'm not sorry for getting into this space. I've had enough variety in my jobs that I've done some work outside of Salesforce and I don't feel pigeon-holed. The Salesforce ecosystem seems to be growing and their is a lot of work available. I'm in my mid-40s so if I can get steady work over the next 10-15 years with decent pay, I'll be more than happy continuing work in this space.
FYI: I haven't bothered with any paid certifications though I do complete Trailheads when I need to learn something new as a way to both learn things and provide a signal to potential future employers that I know what I'm doing.
https://www.amazon.com/Working-Effectively-Legacy-Michael-Fe...
That being said you have to do what is in your best interest. In both cases, the move I made was just what I needed at the time and improved my outlook and passion moving forward. To make up for some of the guilt, I worked like hell the last two weeks, cleaning up as many outstanding issues as I could and documenting everything I could. I also made myself available for questions after I left, though you want to be careful about committing too much time there.
And guess what...in both situations the company moved on and eventually got past the initial hurdles of replacing me. It's likely the same will happen in your case and you'll realize you spent way too much time worrying about something that should you decide to leave, is no longer your responsibility.