685 karma · joined January 25, 2017
As an aside, I’ve just re-read a Terry Pratchett novel and your description of the good engineers’ behavior made me think of Leonardo da Quirm :)
Pricing is completely linear with usage (and very low/free for low traffic) and I don’t have to worry about uptime or scalability.
Slightly different but I like to reason in states and will often draw up cellular automata to represent the different states of the system and how to move from one to another.
Note that this was an executive MBA, so the base assumptions are a little different; in particular, attendees have a pretty good idea of what they're worth on the market and the effect of the EMBA is pretty well quantified: most EMBA participants change jobs/companies after the program, usually with a nice salary bump (although of course signing up for an EMBA in the first place is a good indication that you're willing to invest in your career, so at least part of that progress would have happened in some way or another even without the EMBA).
In my personal case, the salary increase is close to 100% 5 years after enrollment - so the investment was well worth it.
To answer the rest of your questions, the program was in the FT top 10 (now at #12 or so) and tuition was around 50k€. Yay for European business schools :D
Even with an EMBA, which happens later in a career, the NPV is quite positive.
I think that each level distorts the message to bring it more in line with company culture (e.g. make it look better, or highlight blocking points, or focus on financial topics, etc.). It follows that the quality of the information doesn’t necessarily have to decrease - in theory, the right company culture will ensure that only the most relevant information is kept (and I’m pretty sure you can tie this to successful company traits)
More generally, I think that in this context you can’t treat information quality as a purely objective measure. Here quality is (at least partly) in the eye of the beholder, so you could argue that making the reporting more in line with the expectations of you higher-ups actually increase quality.
In my experience, employees get told which project to work on by management, usually through a formal budget / roadmap process which allocates resources to the initiatives being pushed by different stakeholders such as marketing, sales, IT (e.g. for maintenance projects), etc.
So the need is not so much to know what the employees are working on but rather how the projects are going. This is usually handled by steering committees or similar governance bodies, where each successive hierarchical level gets a broader (but necessarily more concise) overview of all the projects they are involved in.
What makes it through these different sieves depends on the company culture and what is considered the "right" level of information. In the worst cases, bad news will be edulcorated, then removed, until every line on the dashboard is green. In more result-driven companies, what makes it to the top is what is susceptible to impact business, so it's going to be the project delays and other bad news. But this process is like the "auto-summarize" feature in Word: a lot of nuance gets lost in the different layers and there's alsways a risk of ending up with nonsense. There's also a lot of mediation being done by middle management.
The closest I've come to direct feedback from the junior employees to the execs at large (>10k FTE) companies is when execs tour the office and come take a look at the grunts in the trenches (this will happen once or twice a year). Inevitably there's an awkward roundtable with a chosen team (usually the one working on the most visible project) where the exec asks each person in the room "what is blocking you and what can I do to help you" while that person's boss and grand-boss glare at them from the back of the room, silently promising retribution to anyone who raises any actual issue.
I am just going outside and may be some time > I’m committing suicide, don’t wait up for me
I discovered Stephenson with Anathem and I was hooked. This book doesn’t get a lot of love it seems, maybe because it’s not Stephenson's usual cyberpunk / near future sci-fi (and maybe because of all the made-up words and history—there’s even an xkcd comic about it). But (SPOILERS) you gotta admire a book that starts like The Name of the Rose and finishes in a nuke-propelled starship.
Honest question: is it not best practice to have an isolated, dedicated management network? I can’t for the life of me understand why a misconfig on the production network should hamper access through the admin network. Unless on Google’s scale it’s not the proper way to design and operate a network ?
Security auditing firms cost a lot of money. Money you don’t have when you’re a small startup. Besides, an auditor audits and the hard part about this list is implementing it. Until you can afford to hire someone to take care of security, it’s usually the CTO’s job to make sure security is not an afterthought.
> I don't see any value in relating anything to the financial stage of the company because it's irrelevant.
It is extremely relevant, for at least two reasons. The first one is that the company’s financial resources dictate what you can or cannot do (e.g. hire a dedicated security resource, pay for pen testing). The second is that some recommendations just don’t make sense before a certain size (e.g. there’s no sense in setting up an AD and GPOs when there’s just 3 of you in the company).
1) as mentioned in the article and comments elsewhere, the majority of employees in FT at that time were civil servants. This meant (as per the privatization deal that was defined by the French govt at the time) that they could not be fired. Ever.
2) the population was pretty old (the average employee age when I joined in 2004 was 48 years old). A lot of people were hired in 1976-1980 by the then-“ministry of posts and telegraphs” to bring copper to every home in France. Those linemen and women were around 50 in 2004. Needless to say, every home in France had long since been plugged to the telephone network so their original work no longer existed. It’s not fun being a 50 year-old civil servant whose skill set is obsolete and no-linger needed.
3) FT was in pretty bad financial shape after purchasing Orange at the height of the dot-com bubble. I remember endless cost-reduction plans at that time, initiated by Lombard’s predecessor (Thierry Breton, who is now C.E.O. of Atos). As an example, the 2003-2005 objective was 15B€ in savings, IIRC.
4) Competition in the French telco space was already fierce at that time. FT, as the incumbent, was under obligation to provide its infrastructures and bulk service at cost+ to all the newcomers. Suddenly it could no longer charge what it pleased, and had to learn about marketing and sales and customer service. At the same time it also had to become a competitive internet provider and mobile operator.
5) Of course the obvious answer was to transition the historic workforce to new jobs required by the change in context and technology: telemarketing, customer service, IT infrastructure (my first job was web developer, and the ops team for our production infrastructure was party made up of ex-linemen. Needless to say, not all of them were comfortable with system administration, and I spent a lot of hours on the phone with them spelling out bash commands). Besides the skills gap, it’s also a very large mindset shift to go from proudly contributing to the modernization and wellbeing of your country, to trying to upsell your customers on a faster Internet offer. (Think going from Bell in its glory days to current-day Comcast)
6) for a very long time, FT’s top leadership (and I mean like the top 4-5 management layers, including all the excom and the CEO - basically anyone at VP level or above) came almost exclusively from a small group of engineers, the “Corps des Télécoms”. These people are extremely bright but not always gifted on the emotional intelligence scale. And they’re very loyal to the company. Plus, there was a huge amount of groupthink — they basically all reason the same way. This only started to change with Lombard’s successor, Stéphane Richard. I mean, he’s also from the Grandes École elite circle, but he went to a business school rather than an engineering one, so, you know. (/s)
Now, I absolutely do NOT condone what happened in FT at that time. But its management had to deal with massive debt, eroding revenues and margins, intense competition, and a large, ageing workforce who needed to be reskilled and had trouble transitioning from public service to competitive market. And who could not be let go.
It was a pretty shitty context, and arguably a textbook example that too much worker protection can actually be a bad thing for the workers themselves. I mean, if a mass layoff (with healthy compensation packages and re-training and so forth) had been possible, FT’s management would most definitely have gone for it, rather than bullying people until they left of their own accord (or took their own life).
The challenges usually involve static analysis / disassembly, breaking improperly configured crypto, etc. The best part (for me at least) is that competitors must submit a write-up of how they cracked the challenge, and the best write-ups are published. It makes for fascinating reading even if you’re not really into that scene.
How do you store seed values in password managers? More specifically: how do you export them from Coogle Authenticator? (I’ve not found that option). And how do you import them again?
After this episode I made damn sure I had recovery codes stored in a safe place.
To be clear, it’s absolutely your manager’s job to set expectations and to walk you through the cultural norms of the company, but bad managers happen. Maybe it’s worth having a chat with some of your colleagues who’ve been in the company for a few months to understand how their integration went and see if they have some tips for you (assuming your manager isn’t more forthcoming on how to get a higher score).
js targets the browser (angular, React...), the back-end (node), the desktop (Electron) and mobile (React native). Just like the Java of old with applets, javax, JME, and of course weblogic and friends, js today allows you to code anything, as long as you don’t mind doing it badly, insecurely and/or wastefully.
Due to this ubiquity, a large majority of job openings list js in one form or another as a prerequisite (remember when entreprise code was synonymous with Java?)
Once you know enough js to be dangerous, there’s little incentive to pick up another programming language.
UP (uncle post) mentions a home-made Android app to sync... is there a more mainstream option?