Table of Contents
Hi readers, this is the ninth (actually 9c) chapter of “my story“. Please take a look at the other chapters for some context.
I only touched “Corporate BS” superficially.
This chapter is about Corporate BS at Hooli, but you can find similar – or even worse – problems in your company as well. This is to remind me that there’s no ideal “job”. That the discontent with working for “the man” is so deep that the only way out is actually Out.
I planned to write more about my experience at Hooli, but it’s been 5 months since I quit, and almost 7 months (February 6th 2020, resignation day) since I kind of stopped working (and going to the office). My memories are fading.
I’ll probably write another chapter on “the death of Passion”, which will be more centered on me than Hooli, and that’s it. The 29 pages of anger diary will be buried with my master degree once I’ll retire.
So long, Hooli, and thanks for all the fish.
I know some readers and current Hooli employees will be pissed off by my statements, but I’m not here to fix Hooli’s or corporate America’s problems (didn’t you notice that I quit? If I wanted to fix – and I did my small part while employed – I’d still be there). I just want to be vocal about the issues, and warn the young idealists to keep their expectations low.
A couple of important disclaimers:
- I think the problems are industry- size- and capitalism-specific, not just Hooli’s. Maybe Hooli does even better than the others in the same industry. I don’t have much experience outside Hooli. My previous experiences as a Software Engineer (In Research, In the VideoGame Industry, as a Freelance) have been way more rewarding in terms of Mastery and Autonomy, but it was a different era for software development, and it was a different me. So… I don’t know!
- As I said many times, I’d still recommend you to take this job at Hooli! Hooli is still an amazing company under many aspects, including but not limited to the stellar compensation! You want to startup? Yes, great, spend two years at Hooli first! You’re not sure you want to be a Software Engineer anymore and want to write poems? Awesome! Please tell me your Net Worth… what? Ok, work at Hooli for a couple of years and then I’ll read your stuff, Mr Shakespeare!
- The Corporate BS was just the icing on the cake. It’s not the main reason I quit, I guess. Now that I think about it, most of the actual development is driven by Corporate BS (perf driven development and technical debts, team defrags, acts of fake leadership, change for the sake of change, “we are still a 6 digits employee startup yo!”). Ok, cancel this number 3 please 😀
I’d like to start this post by unrolling most of the common issues people reported in the Quora Thread I linked in my previous post, and adding my thoughts on them.
If some of the issues I hinted in my email to Mr V will be uncovered, I’ll face them after.
Note: the following are not sorted by my perceived importance, the order is mostly random.
Many quora answers point out the lack of specialization. Take this one for example. I split it in two, since it faces two different problems in my opinion.
The engineers Hooli hires fit the mold of generalist system types. They are good at algorithms, database concepts, transaction processing, scaling, etc. They generally do not have domain expertise in product areas.
This is not that bad on itself.
It’s true: you don’t need to know any specific software framework to work at Hooli as a SWE. Your coding interviews will be algorithmic, or system design oriented, and you’ll be able to pick a language of your choice to solve the problems at hand!
And in your career at Hooli you’ll mostly use internal products, most of them unknown and useless outside of Hooli.
It’s true that “everybody wants to interview you” after you quit Hooli, but it’s also true that unless you devoted your free time (and your work-life balance) to keep up with industry standard, you’ll feel obsolete, overpaid, and essentially unemployable in the real world as an engineer.
But while you’re within Hooli walls you’re protected, well paid, comfortable. And unemployable outside 😉
The culture rewards engineers who solve knotty technical problems and leaves behind those who enjoy the harder part of product development, moving a product from version 1 to a truly great version 3 by smoothing out the rough edges and adding functionality based on customer feedback, and by maintaining and debugging a product. This is one reason why years after release, Hooli products tend to still look like a version 1 product, not a honed version 3 that unquestionable beats the competitors in the market.
I’ve already talked about it in last post, and I confirm it here again.
“Hey RIP, but if those are the rules why not just go for it yourself! Just solve some cool technical problems and leave the boring robustness and maintenance to someone else!”
Yeah, good suggestion… except that I joined too late the Software Development Ponzi Scheme Pyramid, also known as Detonator Pattern. Had I joined few years earlier, or got promoted a couple more times before the zombie horde of technical debts showed up, maybe I could have survived.
Plus, I’m the kind of person that needs to understand everything. That needs to have cleared all the steps from idea to assembly code, at least in my mind. Offering software time bombs and short term solutions is not what I studied Software Engineering for.
From another quora answer on the same thread:
Too much complex stuff to learn that is Hooli-specific and cannot be applied elsewhere
Yep, so true!
Diversity of Thought (lack of)
Hooli talks a lot about diversity. They want to hire without respect to race, religion, or gender. That is an extremely good thing. Hooli means it too. While I was there, I saw efforts to combat hidden prejudices and to make the environment better.
True. To the extreme though.
To the extreme of hearing rumors of recruiters celebrating their “diversity hires”.
I interviewed many candidates. I think I was pretty good at it. the correlation between my interview scores and final hiring decisions was pretty high. Except for two Asian women. I was asked to review my score multiple times. One of the two was embarrassingly unskilled. She was offered a job. I’ve seen several skilled candidates not being extended an offer.
It’s not the best way to achieve diversity. Not even good for the people benefiting from your policies.
This is just bad.
However, the type of diversity that is truly crucial for a company is the one they do not want: Diversity of thought. They want innovative employees, but only ones who think inside an algorithmic box.
Didn’t think about it, but it’s actually true. I never fully understood what was this “Hooliness” we were supposed to evaluate in coding interviews.
Anyway, yes, at Hooli they want a colorful herd. Same person, in infinite variations.
Metrics are Everything
Metrics are everything, regardless of what they measure — I think metrics are crucial. You cannot manage what you cannot measure. But, at Hooli what you measure is merely something to be gamed. That is, the ability to measure can take precedence over the wisdom of what to measure.
I can second this as well.
During my Hooli Shopping Express years, we were essentially just gaming metrics all the time.
You must be data driven, even where a metric is useless, inaccurate, gameable.
This is of course just a byproduct of Perf Driven Development.
Don’t listen to the users. Just pick a metric and optimize it.
“But RIP, metrics are good!”
Yeah, but if they become the target, they cease to be a good measure.
Excellent engineering managers, but poor connection to business objectives — Engineering managers at Hooli tend to be bright technical minds. […] Business sense can be lacking.
I don’t have strong opinions on this. I must say I’ve always wanted to be as far from “business” as possible. I never felt connected with “what’s going on” on the business side of things, but I didn’t put any effort to know more.
For example, I found a bit weird that we never talked about real numbers, money, revenues, profitability of what we were doing. Just technical stuff. I was ok with it, but that doesn’t mean we were unaffected by business decisions. When Hooli Maps in Switzerland defragged most of the teams it was clear that it was due to a lack of product profitability, but we hadn’t a say the entire process, and no warnings before. Everything is awesome, until one day it isn’t – and it’s too late to awesomize it back.
No involvement in the business, but you pay the consequences of wrong business decisions.
Maybe the reason I didn’t care much was that it never affected me directly. My teams survived all the reorgs and defrags. I was lucky in this respect. In my Hooli Maps here, mine was one of the only teams who survived two huge reorgs.
Also about Eng Managers:
Engineering management with extraordinarily poor EQ — Most of the management at Hooli has been raised through engineering culture. Technical chops are selected for. People skills are not. It shows.
I mostly disagree with this.
I was managed by 9 different managers in 7.5 years. My managers were on average nice people. Even those not born with “empathy skills” were trained for it. I also tried to do my best to establish empathy grounds, sharing feelings and personal life with them.
Ok, maybe my perception is skewed due to Superboss huge impact on my Hooli career (he managed me for 1.5 years and got me promoted), but my average manager was way better that I expected both on the technical and on the human side.
But of course I heard horror stories from colleagues, so… make your judgement 🙂
In retrospect maybe I could say something not great about a couple of managers of my Hooli Video era, but on their defense I was on the verge of burnout and a hard person to manage.
“But RIP, that’s where a great manager shows up!”
Yeah, but also they have the business to keep going. I’m not attached to the romantic idea of a manager who should only care about the morale and the well-being of their employees… They’re also playing their own perf driven development.
From RIP Hooli Anger Diary, page 22:
Monday November 12th, 2018: in our 1:1 MyManager said that next Wednesday team meeting is not mandatory.
Wednesday November 14th, 2018: I skipped the team meeting due to a lunch-time event I wanted to attend (team meeting was scheduled at 1pm). MyManager scolded me “it would be great if you attend team meetings, RIP”.
Thursday November 15th, 2018: Our CEO is visiting our office. Well, not the CEO CEO, but one of his reports. No, wait. There’s another CEO between them. Anyway, our Hooli Video CEO is visiting and there’s a Town Hall event I’d like to attend to know what’s Hooli Video 2019 road-map. I guess half of the office will be there, the huge meeting room will be fully packed. I sent an email to MyManager to ask if we are having this yet-another-useless-team-meeting today at 11.30am, because, you know… CEO is here. He didn’t reply. I sent an email to the entire team. Nobody replied. Checked the phone 5 minutes before the meeting should have started, while I was listening to our CEO in a room full of people. Again, nobody replied. I left the crowded room to go to this shitty, useless meeting. I was alone. Nobody showed up. 10 minutes later, 11.40am, TechLeadColleague replied to the email: “let’s cancel it”. Fuck you, asshole. I’m quitting this shit!
Introversion and Loneliness
You may feel alone and isolated, as everyone’s just so focused on their work and have no time or desire to just take it easy and chat.
I do think one of the best quality of working at Hooli was the sense of emotional safety. You don’t feel judged for who you are, what you dress, what you believe, what you like.
This is good, very good.
I come from Italian working environments where it was “normal” to make jokes about colleagues, judge their clothing, their haircut, their belly, their sexuality and so on. I didn’t like that. For example, I don’t give a crap about appearance. I wear the same clothes every day (but of course I do care about cleanness), and you can find me on the vocabulary under “opposite of fashion”. While working in Italy, I was sometimes mocked for my clothing, or for my shaving habits, or for not even owning a suit. I survived 5 or 6 weddings by borrowing clothes from family and friends. it’s one of the things that pisses Mrs RIP off 🙂
Even though I’m this kind of guy, I was surprised to realize that many colleagues were way less curated than I was. For example in my first team in Hooli Maps I had a female colleague who dressed t-shirts with holes in them, put her fingers in her nose all the time, burped frequently, and used to scratch her body in not very polite manners. I was kind of surprised… I thought “wow, if she worked in any Italian company they would make her cry day and night!”
I got used to it, and actually loved the “respect” and “safety” associated with “I am what the fuck I want, given I’m not acting like an asshole”.
The problem is that the meaning of “acting as an asshole” changed over time, in the direction of limiting personal freedom. A lot.
In the end everything became “a sensible topic”, and you couldn’t do or say anything.
In order to not offend anyone, the “I’m what the fuck I want” had to shrink a lot.
You have no idea in how many ways you can offend someone if you don’t make any assumption, as you should always do. People complained about everything. People complained about playing “Dire Straits” songs in cafeteria that offended black people. People complained about not using gender neutral pronouns. People complained about reinforcing stereotypes. People complained about t-shirts being inappropriate for work.
We had a monthly mailing list named “Yes at Hooli”, managed by HR, with all the complains visible for public shaming. Of course the behavior was under judgement, not the person committing the bad behavior. At least not in public form.
I saved few of them because some of the issues were so hilarious I couldn’t believe them.
I ended up on the wrong side of public shaming twice thanks to my geeky t-shirts.
One said “I don’t need Hooli, my wife knows everything” – reinforcing gender stereotypes.
Anther one said “Sorry ladies, I’m in the Night’s watch” (from GOT) – not appropriate.
Nobody ever told me why was this t-shirt not appropriate for work.
I was just anonymously reported to HR and ended up in the wall of shame
Reading the Yes at Hooli mailing list teaches you what you can’t say or do because it may offend someone (answer: everything).
LGBT: “There was ~7 min of Pride content and ~27 minutes of AI content at the TGIF. That’s just shameful.”
People below the Equator: “When referring to dates in terms of seasons, people should keep in mind that southern and northern hemispheres have opposite seasons at the same time of the year. Months or quarters are easier to understand and more inclusive.”
People with bad teeth: “In the MK today, I was carefully selecting the dried fruits out of the trail mix using the provided scoop. A colleague came up to me and joked that I was just going for the sugar. I have bad teeth and can’t eat nuts, but honestly, it’s not anybody’s business what somebody else chooses in the MK.”
Irish people: “Today I learned we have an internal product called “paddywhack“, which is a racist term for an Irish person”
So what do you do when even Irish are allowed to get offended??
Haha sorry, it was to good to skip! I didn’t mean to offend anyone 🙂
Anyway, what do you do?
You just don’t talk to people. Of course, talking about working projects is welcome. And maybe about the weather. And geeky stuff, given that they’re inclusive to all religions, genders, ages, ethnicities, disabilities, and so on.
I remember there were a colleague of mine in Hooli Shopping that was visibly pregnant. I noticed it when she was probably 4-5 months pregnant. Nobody said a shit about it. Never. Nobody acted like she was pregnant. Not even her. I was scared to ask if she was pregnant because – god (pick one of your choice) forbids – I don’t want to think what that would have happened to me in case she were not pregnant but affected by a rare disease that grew her belly… I’d be crucified in the main cafeteria for having hurt her feelings! Why take such a useless risk?
Time passed, she was probably in her 8th months and I felt safe enough to ask. My wife got pregnant few months before, and I wanted to share some… you know… HUMANITY.
I was willing to risk my career by asking her the unaskable.
I put on my best “empathy & listening face” and made my bold move:
“Hey, Julia… you… you’re… pregnant, right? 🙂 ”
“YES, I am! 🙂 ” <– oh shit, using pink color will reinforce gender stereotypes!
She felt so relieved that someone asked! We spent quite a lot of time that day and the following weeks talking about becoming parents, the feelings, the fears, the excitement… we connected!
That’s amazing, that’s human.
The fear of offending someone killed so many potential human connections, but not that time.
It was an ephemeral victory though.
I let the fear win many subsequent battles, and turned myself into an introvert at work.
Maybe it affected my life as well.
Maybe it’s also a cultural issue. Maybe since I’m Italian (Oh no! reinforcing cultural stereotypes!) I’m not used to NOT talk to people I spend more time with compared to my family… maybe. But the office started to get filled with silent drones.
Most people are introverted and don’t talk much, so you may become introverted too or quieter than you were before.
I’m not advocating for Michael Scott’s idea of “respect”, but there could be some middle ground where you can still be an accepted social animal and TALK.
Another reason for solitude is that there’s no teamwork, just a bunch of individuals working on their own projects (getting promoted).
I loved pair programming, I used to do a lot of it in my previous work experiences.
At Hooli? Forget about that.
Slower, and not as dynamic as other companies, maybe because Hooli trusts no one to self-approve their own code. Every single code change (called changelist, or CL), no matter how big or small, important or not, risky or not, needs to be looked at and approved by someone else, often by 3 people: the owner, someone with ‘readability’, and someone on your team. This process involves a lot of waiting sometimes, like days of waiting after you write a few lines of code. Only a few lines since you’re supposed to submit the code in small chunks / small CLs. So most ‘engineering’ time is spent not in writing code and doing actual engineering work, but in writing tests, asking for reviews, defending your code in reviews, and doing reviews, and in reading and writing emails. Then you may spend a lot of time in changing configs, more than in writing code. Do you become a better engineer like this? I doubt it.
I hate slow iterations. I hate it so much!
At Hooli everything is slow.
Let’s say you want to make a change. First you have to clarify your idea. Design it. Write a design doc (good for promo). Ask for feedback, get many approvals (good for promo), consider several points of view, hunt people down especially if they live in a different timezone (it’s your promo packet, not theirs). Consider privacy, security, production issues, scalability, impact, effectiveness, alternative approaches…
You get your design approved, awesome! Let’s start writing code!
Wait, not so fast.
“Oh, RIP, but that’s all good stuff! You better make sure your work is useful before you make the move, no?”
Yes, sure, that’s what I do when I feel I have some mastery in the topic, and when I know what I’m doing is going to last for decades… not when I’m trying to make a plan with hundreds of unknowns that will very likely get deprecated or de-prioritized at random times in the near future, if you’re lucky enough “right after your next performance evaluation”.
Time to write some code!
Wait, not so fast.
Test! A lot of them! Write unit tests, tons of them, even when they’re useless!
“But RIP, again, this is a good practice! it’s called TDD”
Let’s say that TDD is usually good, but there are times when it’s a real pain in the ass. You write simple functions, your code is data heavy and not logic heavy, your code uses many backends that need to be mocked… I don’t want to bother you with engineering details, but most of the time I wanted to write 3 lines of code I had to add 100 lines of tests that took days to find out how to write,a dn that are more costly to maintain every time you change backends. Frustrating. And unavoidable. Your presubmit pipeline checks for “code coverage above X%”, and you don’t want to be that guy who tried to submit a changelist to reduce the minimum coverage for your project!
Anyway, even if unit tests were to magically appear while you write your production code, this won’t be fast enough anyway.
Debugging is painful when your code doesn’t run on a machine 1 meter from you. When you can’t step into the code and check memory and processor status. I miss it so much! I miss my Windows and Xbox360 game development, so fucking rewarding to debug!
Ok, code written, tested, and debugged (locally). Time to push it in production!
Wait, not so fast.
First you have to submit it into your repository.
Submitting your code require rounds of code reviews. Sometimes you need reviews from people on a timezone with no work-time overlap with your working day (hello California!). Plus, you need to please many automatic presubmit tools that your team has configured on all your CLs, depending on how paranoid your Tech Lead was.
One of the things not mentioned here is the Draconian code review process, where Those With Readability and code review trolls get to tell you that you need to add more whitespace or write clearer documentation, and yet miss big architecture faults.
Ok, cool, code submitted… Let’s see it in production!
Wait, not so fast.
Launching and productionizing is another slow process: you need to get many approvals to finally put your code in binaries on Hooli servers and see it at work.
Then you need to finalize your story around your launch: gather metrics (good for promo), prove it was useful (good for promo), check for regressions, monitor… until you submit your perf/promo packet, then it can rot, who cares!
The only thing that’s fast in this process is code compilation and linking. Wow, billions of lines of code are compiled and linked in seconds! Wow! It used to take much more time to build a repository from a clean client in the outside world. Cool! Sadly, it matters ZERO in your iteration cycle.
Unnecessary optimization. But still cool.
Everything else is so slow it will depress you.
Let’s also not forget that we’re not talking about rocket science.
The problems you’re facing are both extremely complex and extremely simple. You need to change the color of a button, and to do that you need to show Nobel prize winning technical and communication skills, pass thru five or six reviews, reverse engineer half of the codebase, and get your code in production annoying some directors who don’t give a crap about you.
An enormous expenditure of personal energy to change the color of a fucking button.
the smartest mind of our time are wasting time in making you click ads.
Someone also complained about the strictness of the “coding standards”, but I actually liked them. I
t’s the only place where “order” rules in a land of chaos. Yes, ok, it slows your first CLs down by a lot, but then you’ll grow to appreciate the marginal reduction in complexity that a codebase that seems written by a single person brings.
But it hurt when I got 120 comments on a CL over 10 rounds of review by Superboss – who was well known for his deep and picky code review style 🙂
I often say Hooli has a great problem: Too many outstanding people. For example, when I left, my direct reports were outstanding, my boss was outstanding, my peers were outstanding, my boss’s boss was outstanding, my boss’ peers were outstanding.
Too many people who are smarter than you may make you feel dumber than you are
Yep, impostor syndrome all the way down!
In such an environment you’re stressed to perform at your best all the time, which is not bad on its own, but it comes with high stress attached. It’s like you’re on the Olympic team all the time. One false step and you’re outpaced by your smarter (and younger) colleagues. False step can also include “have a family”, “age a bit”, “have other issues in your life” and so on.
100k employees, everyone pushing as hard as they can.
Maybe one should approach it like one approaches a sport career: you know it’s not going to last for long, so stash as much money away as possible, and say goodbye before it’s too late.
And as I said, all these talented people are not working on meaningful projects.
Here’s something to ponder. The only meaningful organic products to come out of Hooli were Search and then Ads, which itself was enabled by the purchase of SomeCompany, and got its legs from CoFounder.
HooliDroid – awesome, purchased.
Hooli Video – awesome, purchased.
Hooli Maps – awesome, purchased.
Hooli Plus is a flop.
Hrome browser is great, but no direct monetization (indirectly protects search), etc.
Tiny number of wave creators, huge number of surfers.
Too many great people, doing work that just doesn’t matter, and they’re being paid off not to care in an explicit effort to starve the rest of the valley of extraordinary talent.
Stagnation — Most people are over qualified for the jobs they are doing. Because of this, people do not increase their skill set at the same rate they would in a more challenging environment. This is a horrible thing for someone newly entering the workforce because your first few years of work will have a large influence on the rest of your career. You will establish your professional discipline and your professional bona fides in an environment which has rewarded you for learning the politics of surviving in a big organization as opposed to advancing your technical skills. Your peers who took more technically challenging positions with other companies will have a leg up on you within a couple of years.
Boredom — part of being underemployed is doing work that is neither professionally nor intellectually satisfying. This might not hit you for a while, but it is one of the major reasons people eventually leave Hooli.
Insignificance — being a small cog in a big organization means your work has little chance of being significant. This is the other major reason people eventually leave Hooli.
There’s a joke that, as a software engineer, the most challenging task at Hooli is the interview process. After you are in the program, you will need to use very little computer science.
So it’s actually like being in the Olympic team of your country, training with the strongest athletes in the nation, but never actually competing in the Olympic games! Just impressing each other during workouts, without the outside world knowing noticing anything.
The worst part about working at Hooli is how, when you weren’t looking, it takes over the majority of your time and energy. If you are not intentional about how you approach your time, it can quickly become your life.
(read the whole answer here)
That’s a good point, and I admit I’ve been swallowed by this monster as well. I still am somehow. I still only wear Hooli t-shirts (I have like a hundred of them) and use every single Hooli products for my personal life.
But I guess this is true in many companies. Wouldn’t bitch too much.
Many Hooli tech employees are isolated from the outside tech world. For example, don’t be surprised if you talk to a Hooli engineer and s/he has never heard of Slack.
Conferences? Communities? What are they?
You may gain weight from all that free food.
“Haha c’mon bro! Seriously, are you complaining about that?”
Haha no, I’m joking 🙂 I wanted to close this post (which is dangerously getting close to 6k words) with a reminder that in exchange for your energy and your life you get a lot of perks, including free food and amazing insurance coverage, generous pension contribution schemes, more vacation days that required by law (at least in Switzerland), a real parental leave even for the father and much more.
“So the free food is great? 🙂 ”
Yes of course!
Well… most of the time 😀
Bonus 1: Take a look at this amazing post by Michael Lynch, former Hooli employee. You’ll enjoy another great tour of Corporate BS: from promo driven development to sudden project canceling, from stressful and continuous priorities shifts to mountains of technical debts, from corporate politics to team defrags. Michael’s experience was very rough, but that’s how to take a driven, motivated, skilled developer and drain his passion for the job.
Bonus 2: Mission Statement
Bonus 3: I finally realized my why:
What I hate is the performance required. I hate the charade of working 8.5 hours even when it’s not necessary. I hate that half hour that has to be unpaid because of lunch. I hate having to consider the optics of your decision to work a different schedule, take a three week vacation, or having a long lunch. I hate the endless meetings and documentation required to assure everyone you are, in fact, working. I hate the contests people have with one another on who is skipping lunch, who is coming in early and staying late, and who can’t take vacation.
It’s bullshit. It’s inefficient. It’s unnecessary. And so that is why I want financial independence. To free myself from bullshit.
Bonus 4: Litany of Office Hate:
I hate getting myself to work every morning.
I hate pretending like I want to be there when I don’t.
I hate being fake and peppy, keeping a benign smile on my face and making small-talk even if I don’t feel so hot. I hate when I notice that other people are faking it, too — I wish I could tell them that it’s OK to be real with me, that I don’t want to go through the motions, either.
I hate reviews. I hate self reviews and peer reviews, reviews of vendor products, reviews of prospective hires, and reviews of managers. I hate setting goals for myself for the following year. I hate having goals set for me. I hate how the bar always goes higher, never lower, never laterally or even in a circular motion. Just: Higher. I hate how I feel compelled to pretend that I like this ridiculous model because it’s “challenging.
I hate the use of jargon and Three Letter Acronyms (TLAs). I hate MBAs, MBOs, SLAs, SOAs, and having to CYA. I hate people who ask for things to be completed ASAP or, worse, fucking yesterday.
I hate documenting the use of my time, filling out time-sheets that book hours against specific projects so that other people in the organization can further optimize the use of human resources.
I hate doing things this way because they’ve always been done this way.
I hate being on-call.
I hate being expected to come up with new projects and initiatives on my own because this shows to management how plugged into the company I am. I hate that work takes over my mind.
I hate that this parade of things that I hate lasts for five straight days and after two short days that usually are devoted to catch-up life and family maintenance at a breakneck pace you are back to day one of another five day cycle.
I hate the fact that even though I generally enjoy my core function, it typically constitutes only a third of my week. (RIP Note: good for you! I guess during my last 4 years at Hooli what I enjoyed constituted ~1% of my week)
I absolutely love the fact that being financially independent allows me to leave all of this behind.
Love, love, love.
Bonus 5: Quote from John Green:
It is so hard to leave—until you leave. And then it is the easiest goddamned thing in the world
— John Green
Ok, that’s all for today!