GitHub is slow bloatware at this point. I can get a PR to load at least 2-3x faster in Graphite than GitHub. I avoid going directly to their UI at all costs now.
They say money is the root of all evil, and I think that is the core issue. It's unchecked greed and blind nationalism. Political and racial polarization is profitable. Selling guns and ammo is profitable. Being a corrupt politician who helps their rich friends make more money is profitable.
I've always done a lot of the things listed in the post, but just considered it as part of the job. I like laying it out like this as a strategy. I think this is a great strategy for anyone starting a new job, entry level and up!
The “suggest change” feature in github is a great way to suggest nitpick fixes without coming off like a jerk. You actually do the work, and the author can easily merge in all those changes with one click. They’ll avoid making those small mistakes / style choices over time. Also it feels more collaborative and less “do this because i said so”.
The garbled text is included in the tree as relevant, pronounceable, and constantly changing text. Here's Chrome's accessibility tree: https://imgur.com/a/V1589Jr
(I'd love if a screen reader user could upload some audio of how awful this sounds, by the by)
Please use `aria-hidden="true"` for stuff like this, it just removes the element from the accessibility tree. I've also emailed Reactive a link to this thread.
Big props for ARIA attributes - they’re so crucial for differently abled and impaired users. I’ve been combing through our project’s components lately to bring them up to design spec and have been taking a look at our accessibility - it’s so important and so easily missable for most engineers.
The amount of fraud and scammers out there is insane. I worked on a platform that only had a few hundred in revenue a month (just starting out). We did many smaller transactions, and getting hit with disputes was a killer. If someone did 15 transactions, they could get hit with 15 chargebacks up to 3 months later. So for every transaction, even if it only generated $3 in revenue, the chargeback could be potentially $15. (And you lose the revenue!). So for one customer who only spent $45, you could lose $270.
Even when we knew the person was legit, and just wanted a refund, they would do disputes. We only won a handful of disputes. The bank / credit card company will almost always side with their customer, even when provided receipts / terms of service / conversations with the customer where they admit the product met their needs.
How come the chargeback value could be that much higher than the revenue? (NB: revenue, not profit)
If I buy a $3 product and chargeback, then I get $3 back, right? Or does the payment processor bill you $15 for each chargeback no matter the transaction cost?
My guess is that the systems are running image recognition models, and maybe OCR on images, and then just piping that data as tokens into an LLM. So you are only ever going to get results as good as existing images models with the results filtered through an LLM.
To me, this is only interesting if compared with results of image recognition models that can already answer these types of questions (if they even exist, I haven't looked).
Maybe the service is smart enough to look at the question, and then choose one or more models to process the image, but not sure as I can't find anything on their sites about how it works.
I've had people apologize to me for trying to make me do one. The interviewer was smart enough to realize that I was the senior in the room. I would have gotten that job but I declined it for another, more interesting one.
The mistake many companies make with attempting to hire senior developers is losing out on the opportunity to hire the good ones by assuming the candidate will fall on their knees to get the job and do the silly test and be subjected to some prolonged process. The better ones will simply not do that and lose interest the second you say "coding interview". They are only on the market for limited amount of time and all your competitors will be eager to hire them.
Hiring senior developers is mostly a sales job. You need to do your homework (i.e. read the CV, look at the Github) and really sell the notion how amazing it would be for the candidate to work for you and what a great fit they are. I speak from experience; having hired and built a few teams. If there's a lot of doubt after you did your homework, the interview needs to be about building a case that the candidate still has some redeeming features. If there isn't the interview needs to be about quickly confirming key points and then moving onto sales. If after all that you still doubt the person can code, then don't hire them.
reply