- Machiavelli, The Prince
>Therefore any cruelty has to be executed at once, so that the less it is tasted, the less it offends;
That doesn't say to mitigate negative experiences, it says to do them quickly to get them over with
>while benefits must be dispensed little by little, so that they will be savored all the more.”
This says to dole out benefits slowly little by little so the masses can savour each little good thing given.
That's not humanitarian that's Pavlovian.
Fitting that most top-tier business schools quite literally use The Prince as a textbook for building and maintaining organizational power structures. Future executives are taught that Machiavellianism is very bad... unless you're the one doing it.
The quote I listed above is a good example. M. is essentially just saying that, "if you have to do bad things, do them quickly and all at once." Generally good advice, I'd say.
A modern analog would be firing employees - avoid it if possible, but once it's determined to be absolutely necessary, just do it. Don't waffle, give conflicting messages, or build an atmosphere of dread. Make the tough decision, execute it quickly, and then move on. Of course, one could argue that the manager should have made better decisions to avoid the need to fire people in the first place, but that's a deeper discussion.
Machiavelli is still taught because, frustratingly, it still applies.
Good news for you though, 24-packs of Gummy Bears are available on Amazon for just $8.79, thanks to the demand for them from large companies as a low-cost perk that can be doled out across quarters cheaply. ;)
You're completely wrong here. My business school (global top 10) had multiple required courses on political philosophy -- both corporate politics and government politics. Navigating complex political situations is the most important skill to have as an executive in corporate America. In fact, those classes are usually the most popular with students and consistently rated as being some of the most valuable by alumni.
Granted, it's taught as "here are things to look out for from your subordinates" -- but if you read between the lines, it's "here's how to walk the line on this stuff and get away with it".
This has been happening at both Google and Facebook over the last 5 years. I think the fact that they're driving off their most talented (and expensive!) employees is part of the plan for transitioning from explosive growth to maintenance. The growth mindset has become a liability for them.
For reference: https://martin.kleppmann.com/2008/05/11/ruby-on-rails-vs-jav...
> I believe that if there was a full standard distribution for Java EE (e.g. Icefaces+JSF+Seam+EJB3+JPA+Hibernate+Glassfish, to name just one possible API stack out of thousands of different combinations), people would write a lot more good documentation for that particular stack, and it would become a lot easier for more developers to start using it effectively. With the right tools and good documentation, productivity could potentially be about the same for Rails and Java, but at the moment Java is shooting itself in the foot in this regard.
Moreover, Java on the web (first in the form of JSPs, later Spring-based frameworks) was largely a reaction the shortcomings of LAMP, which was largely a reaction to the shortcomings of Perl5 CGI-BIN (what I consider to be the first widely-used web framework). The great irony is that Perl had an advanced dependency management system in CPAN in the mid-1990s and PHP had nothing for years. Ruby on Rails succeeded largely by combining a CPAN-like dependency management system with a web-native development framework.
Rails has disadvantages yes, concurrency and its lack of ability to support long-running tasks foremost amongst them, IMO. But dev speed, for standard "startup web app" features? There is no contest and I'm baffled as to why you would claim otherwise.
I try to stick to Clojure for most of my JVM-ing these days. Right now I've got this one large Java/Spring-boot service I've inherited sitting in the middle of an otherwise micro-services-based architecture built using Clojure/ring and Python/flask services (for the ML stuff). I keep thinking about how I want to start calving off chunks of that thing to re-implement in something not Java/Spring.
Because Spring magic is great until it's not. And then you're banging your head against your desk for a week chasing down some weird heisenbug related to some nonsensical Spring behavior. And there's no sense of accomplishment when you finally resolve it, because the entire exercise only served to increase your esoteric knowledge of Spring, which you never wanted to deal with in the first place.
That said, as a subordinate, I hate it when no rationale is given. And it can be counterproductive too because people will start to speculate about "true reasons" behind the decision. Instead a reasonable thing to do seems to be to publish a rationale but make it clear that the debate is over and everyone has to commit to the decision even if they disagree with it.
Giving a rationale hasn’t engendered trust, and instead has contributed to conspiratorial discussions (they say it’s about x, but it’s really about y!) and often times the conspiratorialists were kind of right. There is no good answer but a straight directive with little food to chew on leads to less counterproductive speculation. And often it is less “dishonest”.
I think people are fairly good at noticing when they are just getting “spin” or an incomplete answer. The conspiracy theories pop up to fill the void. The only way to avoid this is to give enough information. Once you are caught withholding key information you will never be fully trusted again.
Giving no information is probably better than giving misleading information but it certainly doesn’t engender trust.
If you want your employees to be honest with you then you must give them a reason to trust you. Personally I believe part of that is being as transparent as is rationally/legally possible.
Maybe that much trust is naive but when your decisions can amount to things like censoring the internet for half the world it’s maybe not the best plan to just pull the trigger and tell everyone who works for you to just deal with it.
Instead, explain at length and let people discuss, but at some point explain that the decision is final unless some major new elements come up.
But these are places of work not town hall. Get on with your work.
All I’m saying is it’s like getting into an argument with a kid and you try to explain every ensuing “why”? At some point it’s “because!”
The middle son is already employed in Silicon Valley, in some startup I can't pronounce. Getting bored, might want to move on.
The third is a trained pianist and cellist. Now is in IT in Target's national deployment center in St Paul. Definitely interested in broadening his experience, and would welcome a call to talk about other opportunities.
Can't guarantee it would be a fit -- the stuff I do is either incredibly interesting or incredibly boring to people, depending on their interests.