stutsmansoft
Anyone able to confirm/disconfirm that?
I hated the namespaces on the code-generated classes and ended up manually wrapping them, obviating the benefit.
It was also super brittle, when the back end would change something it would break the clients.
I would add though, "leetcode" is also why companies struggle to hire.
I avoid outright companies who use this as a filter, and cut the process short if I encounter it along the way.
Prima donna? Sure. But I believe quite strongly these things measure memorized puzzles, not skills.
Those things test one thing: how many of those puzzles have you memorized the solution to.
I'm also an "old" and suspect you're right about the young-pass-filter.
I've been developing professionally for almost 30 years. I still love making software and I'm good at it.
When I started in this industry, being able to do it at all was the barrier to entry. The processes were light; "here's what we need it to do, go figure it out." Responsibility (and impact) were both high.
Somewhere along the line that changed. Teams blew up to be dozens of people. Process fads weighed things down with tons of meetings, silly ceremonies and other things that actively slow down productive developers.
Add to the mix the hell that is tech interviewing now. If you're interviewing for anyone that will pay well, you're going to be subjected to "leetcode" style puzzles under pressure and stress scrutiny. If that's not how you best think and solve problems, tough!
So yeah...I can absolutely relate. I still love building software and I hate the industry.
The only escape is entrepreneurship or possibly consulting, both of which I am actively looking to do.
Whiteboard leetcode crap is simply a test for "have you heard the trick for this one or not?"
Why? They want to protect that recurring service bay revenue. Oil changes, plugs, belts, etc.
I've been severely disappointed with the psyche of man - we've discovered a large chunk of humanity doesn't believe in science and cares only about themselves.
That doesn't feel like a recipe for long-term success.
Agreed. And there's a lot of great talent that doesn't even want to try with some of these companies solely due to the hostile interview process.
It becomes hard to find a job you can live with.
Some mistakes I've made attempting to go it alone:
- Let a client go too long without paying me resulting in them stiffing me for a 14K loss.
- Took on too much work without hiring help resulting in burnout.
- Over-estimated jobs and under-charged them, resulting in my pipeline running out sooner than I expected and leaving me hungry (see #2)
I've often wished for some kind of "software Jerry MacGuire" who can front-end my work, sell me to clients, deal with the contract shuffle/payment and get me what I'm worth.
Remember the twitter app was originally written by one guy - I bet that team has 50 people on it now, and it’s not better for it.
This, coupled with exploding team sizes and heavy-handed process fads, have left me to consider entrepreneurship as the only viable option from here on out.
But once it backfired and affected a single paying customer, I decided to change my course.
I will say it certainly -felt- like removing the DRM was a mistake at the time, because the cliff was dramatic and immediate.
As others have pointed out this was a product in the 2009 era, and it did eventually get replaced by a first-party app from TiVo at which point I just shut it down.
I sure own my Porsche EV.
I don't have the daily thrills/hassles of the constant OTA updates, because they don't do them except for the radio.
Not concerned about repairability when the designs are so simple there's almost nothing to break...plus it has a good warranty.
I had an iOS product that was doing well, and it had some DRM to prevent jailbreakers.
I had a legitimate buyer complain and after soul-searching I removed the DRM.
Sales immediately dropped to near zero and never recovered.
So at least in my experience, piracy affected sales.
Mame 1.0 should have been the first public release to the world.
Most companies want to push me upward into management (which I don't want to do) - and I feel like I'm aging out of eligibility for most development jobs.
How did you manage to stick with it? I still love it.
I get form letters loosely related to the issue I complained about, and sometimes not even remotely related.
The person who did this didn’t even have a conversation with me about it before doing so.
This was before GitHub and forking and such, but it made me feel angry and unappreciated.
The code that went around was almost entirely my work.
I’m still bitter 25 years later and I’ve never contributed to Open Sores again.
I don't need or expect payment, either. If I'm legitimately interested in the company, I am happy to spend a couple of hours showing them my stuff. Hell I'm proud to do it. I do enjoy programming, after all.
Thinking in a quiet, relaxed environment beats trying to reason through a problem while also thinking about how you are "performing."
I'm not at all worried about 8 "unpaid" hours.