rxhernandez
Joined 10 years ago
Joined 10 years ago
There is absolutely no reason you should assume "testers" know what they are doing. I have met plenty of people with decades of experience in "testing" barely know what they are doing. Even in the case they know what they are doing, they shouldn't be testing a *deadly* vehicle with potentially broken software on heavily populated *public* roads.
I just look at those behaviors as huge billboards that broadcast what's wrong with that person (as long as it's a stranger; if they're not a stranger it's a completely different story)
That's... That's a huge stretch. I've been on an outdated version of pycharm for nearly a year now because they broke support for docker-compose in a pretty huge way. Moreover, I have yet to have a pycharm project where I didn't need to create my own docker override file.
I had zero success in entrepreneurship in my 20s and I was delusional to think I could accomplish anything in entrepreneurship without both of those properties (and I tried multiple times a year for the decade of my 20s). It would take someone truly amazing* to pull off starting a successful business while working a full-time job.
* And I say that in contrast to myself, who has been called talented more than a few times by my managers and still couldn't pull it off until I earned enough money to take time off
In the popular sense, they've been on the down and out for years now.
> It turned in to a bit of a mess until I went for a refactor into classes and everything became much more clear.
in my experience, once the logic starts to become complex, you need to develop custom hooks so that a given component stays readable.
The hooks paradigm is a lot harder once you get past the basics, but I wouldn't go back for reasons I could articulate if there's any interest.
I've encountered them with other languages and they're the sort of thing where one time is more than enough to make me feel like it could get me fired; they're Never (with a capital N) okay imo