It is good from the perspective of comparing this to other ML models. It is not good from a real world perspective.
2,170 karma · joined January 19, 2010
It is good from the perspective of comparing this to other ML models. It is not good from a real world perspective.
Introducing unnecessary complexity is, by definition, unnecessary. But we shouldn't be introducing complexity because DRY tells us. We should introduce complexity - some, but not more than needed - because some day a developer will know to update 2 of these 6 line snippets, but won't know about the third.
No, everyone experiences this. This isn't a non-technical vs. technical thing either: I've certainly talked to non-tech people who left meetings unsure what the point of it was or what was even being discussed.
There are several reasons why this happens.
The first reason might sound cynical. There are people out there that do things that don't really need to happen, or need to happen but you shouldn't really need to worry about.
Sometimes this stuff matters, but it matters to the business but not to the tech team, or the way it affects those of us in more technical roles is maybe not apparent unless you've seen that sort of thing before. To take the example you provided: to "allow customers to collect and return online orders from our regional stores" probably requires changes to several different systems, some of which your team might be responsible for, but some of which might be a different technical team, or might require putting manual processes in place. Return handling by itself opens all sorts of process questions, and some of those processes will be automated in code.
Sometimes this stuff matters, but it's explained poorly. [Robert Smith] should be able to articulate the "So what?" in his [quarterly review]. If not, hopefully he gets appropriate feedback to make it more clear next time. In this case, it's not you, it's the person communicating who failed to communicate, but often everyone is too afraid to look like a dummy to ask the obvious question to explain what's going on.
Some specific tactics you can use:
1. Ask why should I (or if you'd rather, my team) care about [transformation strategy] or omnichannel strategy or whatever other thing gets raised. No one person can know everything, and your boss should be able to tell you what part you care about and why.
2. Rather than worry about [transformation strategy], worry about the metric that project is trying to drive. Tech and non-tech people alike use "SMART" (specific, measurable, actionable, relevant, time-bound) goals for projects. If the organizational stuff disinterests you, look instead at the metrics.
3. Hopefully you have permission from your boss to not attend meetings that aren't pertinent to you. If you did (1) from above, and your boss's response is, "oh, don't worry about that," then you should feel like you can ask your boss "Next time we have a meeting on that topic, can I decline and focus on my own project instead?"
* "The Art of Writing Less and Saying Basically The Same Thing [sic - that's not even a complete sentence]"
* "Don't say anything more than you need to / Revision 1: Don't say more than needed / Revision 2: Say only what's needed"
* "If I Had More Time, I Would Have Written a Shorter Letter"
* "Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all sentences short or avoid all detail and treat subjects only in outline, but that every word tell."
* "When revising, pretend to be your own worst enemy. Is there anything that can be misunderstood? If so, change it so that it can’t!"
I'm confused about whether the author read this advice and chose to ignore it by repeating it 6 (or, 5 times, and alluded to it with a sentence fragment), or whether this is some self-aware-meta-I-know-the-rules-but-I'm-ignoring them, or what's going on here.
Whether this counts as being "ruined" will certainly depend. Having worked both at early stage startups and large tech companies, there are definitely trade-offs that come with size, and I can imagine some being attracted to one environment and not the other, but I think a lot of that is a matter of taste.
His non-fiction books are easy to read and full of lots of wonderful turns-of-phrase. A lot of what he wrote back in the day sounds like it could be written today. There is a fair amount of his books that was very of-the-moment, making references to people from the time that I suppose were well known then that you need to read around.
I've only read two of his fiction books (Napoleon of Notting Hill and The Man who was Thursday), both of which are really funny.
> 'When I use a word,' Humpty Dumpty said, in rather a scornful tone, 'it means just what I choose it to mean — neither more nor less.'
> 'The question is,' said Alice, 'whether you can make words mean so many different things.'
Whatever caveats need to be added or however much it would differ from our ideal, I've never seen anyone call the form of government of Athens in the period between the Persian War and the Peloponnesian War anything other than "democracy." The Roman Republic, for whatever it's short comings, was a republic. America in 1790 or 1850 was at least as democratic as either of them (by the six measures you list, or by any other useful measure).
One bit of advice I've given many people I've mentored in the past is to not wait to get assigned the "promo project." It's hard for people to object with "your too junior to do that kind of work" when you've shown them a plan that's on par with what a senior engineer would provide. Sometimes, they might do that anyway, but then the problem lies not with getting the right promo project, it lies with not having a manager who will be a partner in developing your career.
Having a document to read gives the time to read faster through things that don't require as much attention, and read slower through things that require more attention, and maybe even stop and google things that you don't know so you have needed background.
> The promise of a relaxed, comfortable commute to work could even make some people move farther away from their workplaces and accelerate suburban sprawl trends.
At least where I live (suburbs outside of NY), more self-driving cars will not likely lead to more people commuting from farther away. The road capacity is already maxed out. Everyone I know either takes mass transit. In most other cities where I have coworkers, the roads were not built for the number of commuters, and again whether it's comfortable or not, people would rather not be commuting an hour and a half by car each way. This is especially true now in a world where we've all gotten used to a commute of walking down the hallway.
> it’s unlikely to evolve that way on its own.
They don't really explain why. They mention the idea of having shared fleets of cars, which would greatly reduce the cost of ownership and which become more plausible when cars are driverless. It seems like most people would have sufficient financial incentives (saving hundreds of dollars per month) to move in that direction.
The article also doesn't explore the downstream impact from moving to shared fleets, and how great that would be for the environment. We dedicate a huge amount of resources, both real estate and financial, just to parking. If we have fewer total cars in existence, we would have less need for parking. There's also environmental impact of battery production [1], and as we move to electric vehicles having fewer total cars on the road will mean we need to produce fewer batteries, creating fewer mines for metals needed and using up less water which is needed by mining processes.
> It all boils down to making the employees working as hard as possible
This has not been my experience. The way I've looked at it as, these are more explicit ground rules for how decisions are made. At most other places I've worked, the mechanisms for making decisions was often quite arbitrary, and boiling down to whatever the most senior person in the room wants. When the Leadership Principles are done well, you'll see there are checks and balances built in. For example: yes, we have "customer obsession," and we try to work hard for customers, but if my boss told me to work unreasonable hours, he would fail in the "Earn Trust" area, and he would be in danger of losing his team.
I've found my work-life balance at Amazon to be pretty reasonable, and much better than pretty much any where else I've worked.
This can work sometimes and with some groups of engineers, but the engineers I worked with in my career who most needed this (1) would never ask for another set of eyes and (2) were the exact type of person who think a code review equals "people don't trust me."
When I started at my current large tech company as a senior software engineer, I learned a ton from having "more junior" engineers review my code. I also learned a ton from reviewing other people's code. Even now that I have the fancy title of Principal Software Engineer, if I want to make a change to our team's code, I need two ship-its from my teammates, same as everyone else. It's not about "not being trusted," it's about earning trust of others by not pretending your poop doesn't smell.
> Code reviews aren't high priority for engineers.
Well there's your problem. On teams I've been on that do code reviews well, code reviews are considered a high priority. When code reviews are given high priority, and when engineers take the time to plan their work so that changes are small enough to understand, code reviews really don't take that long and are not a blocker to productivity.
> It's up to you and your colleagues to set the rules for your team. Don't adopt best practices in a dogmatic fashion. Rather, ask yourself if the circumstances of others apply to you.
This is true - companies shouldn't blindly copy practices from other companies. I have been a part of teams before that didn't have required code reviews and were still effective, but this required a unique set of circumstances in which all engineers were pretty senior, and so we were doing a lot of owning features end-to-end. It is fun to be part of a team like that, but it doesn't scale very well.
What this article also doesn't address is that reviewing code is its own skill, and many engineers are not naturally good at it. Just as it is bad to blindly copy other companies, it's also not great to blindly equate "we're not good at a thing" with "this thing isn't useful."
According to [1], more precisely the word came into English around 1300. According to [2], Petrarch coined the term "Dark Ages," a term that many historians now reject because the Middle Ages were not dark, around 1330. Whether the claim by this article about how "b" made its way into debt is true, I don't know. But the claim that the "b" was added in "the dark days" obfuscates that it happened around 30 years before the birth of the idea of the Middle Ages as a dark time, and after the Renaissance started in some parts of Europe [3].
[1] https://www.etymonline.com/search?q=debt [2] https://en.wikipedia.org/wiki/Dark_Ages_(historiography) [3] https://en.wikipedia.org/wiki/Renaissance