307 karma · joined June 15, 2016
I am not a financial professional but rely on one to guide me.
Later in the article they begin to talk about overall net worth including regular savings and investments and the numbers are better but could still be problematic:
>> In terms of the average retiree’s net worth, the Federal Reserve data puts it at approximately $1.2 million for those aged 65 to 74. The average net worth drops to $958,000 for those aged 75 and older.
Do you like building software? Based on your post I get a feeling (which may be wrong) you’re looking for the $$.
If you like it, stay with it and keep studying. It will pay off.
(Edit: my experience) I left college and started out writing COBOL. Several dot com busts later and I was lucky enough to lead several SaaS teams and have wonderful exits.
I would encourage you to put together a story that illustrates the pain being caused by this software and get with the purchasers. Not only might it help your organization figure out they need to do something different it could also show off your skills to the orgainization.
Could you collect the time you and other people are spending working on these problems? How many issues are reported to you? How many bugs you've filed and have not had fixed by the vendor? Rolling this up into a real dollar coast it's having on you and the school district users.
Recently retired engineering manager here. Manager I all the way to VP of Engineering at several successful startups and a few big companies.
I was continually surprised that fresh and new challenges continually appeared, until I got wise enough to know there will always be something you not run into before.
Be wary of anyone who think’s they’ve seen it all.
Edit typo while on my trainer. Lol
Because of our (over 40s) years of watching bad policy after bad policy destroying our work places, and speaking up.
I suspect with Netflix’s recent crackdown on sharing, this will get much more common and their recent gains in membership will reverse.
They just don’t have that much good stuff coming out, nor do many of the services.
Currently really enjoying Hulu on their 1.00/month plan from Black Friday. Many many shows and movies we’d not seen.
But I believe you are correct in that reducing requirements for car seats could increase the number of kids people have.
(I was not allowed to reply to your post)
I picture a construction company counting the total inches / centimeters each employee measured every day. Then at the end of the year firing the bottom 20% of employees measured in total units measured in the last 12 months.
Not only do we uncover bugs, it’s a great way to get the whole company learning about the new things coming and for the product team to get unfiltered feed back.
The claims processing system I worked on used a number system that would only go to 4 digits, it would roll over to 0 if we ever processed more than 9999 claims overnight.
Our VP would not listen to us when we said we needed to change that. He said "Claims process fine every night! There is no problem." I had left before they got to that 10,000th claim (thankfully).
That said, anyone need an old COBOL developer?
Edit: now I’m the VP of Engineering. We do work on tech debt regularly.
It still hurts a little every time I think about it. I really liked that product.
“ If the goodwill asset becomes impaired by a decline in the value of the asset below the purchase price, the company would record a goodwill impairment. This is a signal that the value of the asset has fallen below the amount that the company originally paid for it.”
Edit: “ Broadcom has not returned CRN’s request for comment about the job cuts. The company, which closed its acquisition of VMware Wednesday, had previously stated it could find $250 million in synergies once it completed the deal.” Synergies is code for the redundancies I mentioned above.
Gold! My week is made, no matter how many deadlines I blow past.
Now if it hits you square in the chest, lights out.
I’m far from knowledgeable in this area but I’ve never heard of a relationship before. (ed)
The product that was the breakthrough is likely (somewhat) wonderful and loved (or at least used) by many and generates the bulk of your revenue. However we all know that solution that has gotten you this far has problems and there are many ideas to be able to go to the next level.
But any idea that is seen to take away from the focus of that main revenue generator will be fought unless there is VERY strong leadership. Anything "new" will impact marketing budgets, Sales incentives and revenue goals, threaten those who are working on the "legacy" project, not to mention external forces who are only interested in the bottom line revenue and EBITDA numbers for the next quarter, not the next 1, 3 and 5 years.
I've had this happen at 2 startups I've been through. Both had successful exits, but could've been more and build a much better future path for themselves.
Now trying to avoid this in my current home.
What if Apple had stopped the iPhone for fear of it cannibalizing* the iPod line of products revenue? * https://www.imd.org/research-knowledge/economics/articles/ap...
It was a wonderful product in the early 2010s.
I am also from a SaaS vendor and we are using a 3rd party to integrate to the various SSO providers our customers have. We have not tacked on any additional cost to our customers for this as we also believe this to be baseline. But I do like the approach of at least covering costs.
For us it was not a matter of "not being bothered to implement saml in-house". We carefully considered our options. However, implementing it ourselves means we must have an in house expert on SAML and understanding the various IDPs.
It also requires someone to tightly monitoring any security issues that may appear in the wild that could impact our implementation. (We do still need to keep our eyes open, but we can leverage our vendor for help here.)
Resources required to this ourselves is a minimum of at least 1 full time engineer and someone who can be their backup, we need additional testing resources, and more. Making this roll < full time will hurt you down the road.
I'd rather our people can be focused on the problems our product is built to solve for our customers and then we can work with experts in the SSO space to guide / help us in solving that problem.
On the other hand: the 3rd party we're working with likes to come back every few months with a "Oh! We didn't know you were going to do (fill in the blank), we need to add another dollar per user per month for that."
Neither approach is perfect. But I lean towards keeping our teams as focused as possible on our product.
(PS: I have been with other orgs who've done SAML in house, and it is not simple. Don't underestimate it. It hurt, and we burned a lot of resources that could of been making our product better.)