To be fair, the article doesn’t quite deliver on this promise. The examples are mostly focused on improving work-related workflows, so I guess that’s what they think “daily life” is.
I agree, but some (most?) software being written doesn’t require a deep understanding to verify because the domain is small enough or you’re not required to solve for all of its intricacies. E.g. prototypes, internal tools, low scale CRUD apps, personal projects, etc.
I believe this is where the huge divide in perceived AI productivity in SW comes from. It’s folks working on low-understanding-required domains talking to folks working on high-understanding-required domains.
Agreed. I kinda concluded that the expected `doctor` usage is to have an agent run it for you and then they can try to figure it out when `doctor` can’t fix the issues.
I tried both Beads and Gas Town and had the same experience.
These fully vibe coded tools seem to have near zero QA. The fact that they ship with a `doctor` command that you regularly need to run (even if you didn’t change anything about your environment) tells you all you need to know.
Meta has been known for years to only negotiate if you have competing offers. I guess being the only place with high TC hiring right now complicates things but this negotiation strategy is not new.
Some quick feedback: It’s hard to parse your CV quickly because there are no actual job titles. I have to dig into the bullet points to get some idea of what your role was.
> Is a google employee in US somehow more competent than the one in India?
Yes. I can’t speak for Google employees but I’ve worked with Indian FTE teams at another big tech company. Indian FTEs are generally less competent than US FTEs at the same level. Upper management knows this and they don’t care because US employees are 3-4x more expensive, so they can hire 3 senior engineers in India for the cost of 1 in the US, which is still a good deal on a cost-per-output basis.
I think the reason for this competency discrepancy may be the huge incentive to move to the US because of pay. In other words, if Indian engineers were as good as their US counterparts, they would move to the US and make 3-4x as much, which leaves only those incapable or unwilling to move in the Indian market.
Flashy product announcements without an immediate release are part of the “big company game”. Usually they are just a mechanism to make leadership more confident about the product by showing them how excited external people are about it, creating hype, etc.
I made this comment when the submission title was “Tech salaries largely unchanged as skills shortages continue”. It seems like the title is more accurate now.
This is not a consumer-facing, social payment platform (e.g. Venmo), it is another payment rail (e.g. ACH, wires).
Laypeople are not the target audience for this, payment rail users are (i.e. entities who regularly utilize ACH/wire transfers or build services on top of them).