200 karma · joined June 2, 2022
I didn't knew a thing about how the business operated and the rationale behind the loans and the transactions. The parts of the application that had unit and behavior tests were easy to work on. Everyone dreaded touching the old pieces that didn't have tests.
I've been trying to use my Google pixel buds and it's the same garbage experience you're mentioning. Random disconnects, output/input device swapping, and if you're using MS Teams or a video game that controls the devices it's a nightmare...
Got laid off because sales goals were not met while they retained people which I think were incompetent in their work. Even some guys which I think were better and more critical to the projects were dumped.
I'm not climbing that ladder by being proactive and "pragmatic" again...
Call me a paycheck stealer, quiet quitter etc.
Just give me some JIRA ticket and let me read books while I get my job done in 1-2 hours a day.
Usually the POS rate is around 2% so at the end of the day you'll split it evenly and get a 3% discount. A few years back it was even highter and I bought several home appliances and saved around $100 so it's worth for both parties.
Now imagine people that deal with ranges from 10K to 100K - It's definitely worth it shaving a few bucks here and there
I mean it's a great achievement, however I feel that until we get our hands on a product that fully enhances the life of regular person I'll truly say "AI is here, I can't imagine my life without it"
Of course if it's specifically used behind the scenes to create products for the general consumer no one will bat an eye or care
That's why there are lots of people who don't even know that Chat GPT exists
At the end of the day they operate the same way a business does, once you scale your product your org becomes bigger and cluttered, therefore some people prefer a more "customized" religious experience and end up abandoning these megachurches
Tbh if I didn't have knowledge on the framework I know I wouldn't have been able to complete it. However I found it disheartening the fact that they just checked that the app worked, didn't have any bugs but didn't even cared to ask around if I actually did it.
These days I can't even imagine how easy it is to cheat with ChatGPT. Last guys I have interviewed I tell them to download a repo with a sample app and poke around with questions. I can quickly tell if someone is BSing and how deep they actually know about the language/framework. I've found this to be better than live coding or take home.
On the other topic, remember that the hiring side doesn't have an incentive to tell you how well or how much you suck at coding, interviewing etc.
At the end of the day I'd say it's luck + marketing/attention grabbing. If the algorithm doesn't show your content and the content itself is boring or doesn't have a market you won't make it through
What makes it worse in the front-end framework world is that either:
1-Projects become convoluted with 3rd party libs to solve a problem
2-The framework maintainers eventually introduce APIs that aren't backwards compatible and existing ones stranded or deprecated
The part I don't like about useEffect is that developers tend to overuse it and when they get stuck in infinite render loops you can see the whole mess it can lead to and how hard it can be to untangle monkey patched logic.
Another factor why we don't bike around is the irregular terrain with slopes. Biking in places like the Netherlands, New York is really fun as it's really effortles. Biking in places like Bolivia, Guatemala, Costa Rica or any city built within slopes not so much, and don't tell me that with a good bike gear it's solved...
I think this "documentation framework" has helped me a lot to write precise docs and how to structure everything regardless of the platform
- People look down on console/logging, but it's useful specifically when there are race conditions or too many variables. It's way better to have several outputs and logs rather than a "standstill" picture you can only look while using the debugger.
- "Learn to debug" - This advice is thrown too vaguely around, but I'll tell you that the 2 essential pieces that helped me debug are 1- using watches to keep an eye on variables, props that are relevant to the problem 2- Use conditional breakpoints - About the 90% of the people I've paired programmed with don't know about it or even if they know it exists they don't use it and when I put in place some conditional break points they look with awe at how it can make a change.
- A somewhat counter intuitive or controversial advice: read the code involved and look for inconsistencies, dumb scenarios, flags, awful named variables and clean them! - Sometimes my attention span and memory range is entangled with garbage code that makes it harder to reason about. By throwing away the pieces I don't like and improving on them I get the benefit that in the future it will be easier to maintain and reason.
The reason being: no one around the company likes maintaining those projects because they hate the framework and we haven't been able to hire people willing to learn/work with Angular.
I love the framework as it has almost everything you need out of the box. At the beginning I hated it but as any tool/language once you get the architecture, patterns and ways to build stuff you feel it's a great tool.