2,530 karma · joined January 16, 2012
1) did the code use a third party library while a standard lib is sufficient? Is there a way to use native language features (e.g. list comprehension) to make the code more idiomatic to people familiar with the language?
2) are the namings make sense in the business context? Can a new hire read just the public interface and be able to guess the usage?
3) do people have to jump around, full-text-search the code base to understand what's going on? Is automatic dependencies injection being overused? How many things people need to keep in their head to be able to follow this code?
It's all readability there, and I'd argue it's not only about style or formatting.
Software engineering is a collaborative process. I don't write code for the machine; I write it for my colleagues and my future self to read. Code we write 6 months ago looks like someone else code. Readability is important unless you're convinced that it's prototype/throwaway code.
After readability then I'd look for tests. It's a theme: good tests are also meant to be read as documentation. Beside ensuring correctness, it's also the example my colleagues or future self can refer for the module usage.
IMHO, 76% accuracy is honestly low. If the person has to sacrifice so much accuracy to hit 267 I'm not sure it's worth it. For most typing, making a mistake actually interrupts your thought process. This speed is only achievable/useful when there are text on the screen that you blindly retype.
This reads like a PR article.
It seems like I should go stock some of the old version in case they decide to discontinue it and only offer non-Fn version later.
Beginner's mind can be simulated by anyone who stays humble.
I can give you the most humble and competent person. The most they can do is to "guess", or in a better term, simulate how another mind will think. It depends on multiple factors, including culture, education, and environment they are in. Sometimes, the best way is to just ask/observe a real beginner's mind.
I don't want to go back to the office not because I want to WFH. It's because COVID is still a big threat. I'd go back to work in the office in a heartbeat if there isn't a pandemic around. The office is cool, and the in person interaction is great, despite me being an introvert.
Unless we have data on how many people choose to work remotely due to COVID, I would not hastily attribute those people to the camp of "only want to work remotely".
https://en.m.wikipedia.org/wiki/Cambodian%E2%80%93Vietnamese...
This view is only correct if a) the US border is completely open and b) all the candidates around the world can speak professional English. We know that both the above conditions are false.
I don't think this is recommended to use internally at Google because it's not supported on Safari.
If you rely on a "not-leaked" interview to filter out bad candidates, it's likely that you may not be conducting an effective interview.
Good interview is about figuring out "what the candidate is good at" not about "gotcha I proved that you're a bad one to filter out". I don't have a set of questions I ask all the candidates. Instead, I based the questions on their experience and projects. It's common that I found out "the candidate is not as good as they claim for this subject", and that's fine. The interviewer can switch the topic and see if the candidate is good at another subject.
Everyone is good at something. The job of the interviewer is to find out that, and whether that fits the business needs. The job of the hiring committee is to decide whether it's worth paying for that compared to other candidates. The only "filtering candidates" job is the recruiter, not the interviewer.
If you haven't, give it a try (free): https://stadia.google.com/games/destiny-2
Best practices are necessary. The value of "best practices" rests not on whether it is good. Its value is that there is an enforced standard across a business/organization. The existence of a standard (and recommended way) helps smooth out the execution/operation. In software engineering, that means easier refactoring, easier migration, easier tooling development, easier training, easier for people to move around within an organization instead of moving out...
I'd recommend any organization to find, install and periodically improve their "best practices". Just the virtue of their existence is a net positive to the business.
Your argument is like hiring only minimum wage workers to build rockets, then complain that on average they don't provide that much value and can't solve integrals in their heads.
If we want better teachers, the solution is not surprising: pay more.
The common saying in engineering is you use the right tools for the job. Likewise, you place the right people to the right job. It would be a mismatch to put an L5+ to do some low impact work. That would be an inefficient use of limited resources. The SWE would also be unhappy since that affects their perf/promo. Depends on the potential impact/difficulty/urgency, it might be more appropriate to save that work for an intern, fixterm, or TVC.
It's not about "so against having good old employees". It's business.