What an unimaginable horror! You can't change a single line of code in the product without breaking 1000s of existing tests. Generations of programmers have worked on that code under difficult deadlines and filled the code with all kinds of crap.
Very complex pieces of logic, memory management, context switching, etc. are all held together with thousands of flags. The whole code is ridden with mysterious macros that one cannot decipher without picking a notebook and expanding relevant pats of the macros by hand. It can take a day to two days to really understand what a macro does.
Sometimes one needs to understand the values and the effects of 20 different flag to predict how the code would behave in different situations. Sometimes 100s too! I am not exaggerating.
The only reason why this product is still surviving and still works is due to literally millions of tests!
Here is how the life of an Oracle Database developer is:
- Start working on a new bug.
- Spend two weeks trying to understand the 20 different flags that interact in mysterious ways to cause this bag.
- Add one more flag to handle the new special scenario. Add a few more lines of code that checks this flag and works around the problematic situation and avoids the bug.
- Submit the changes to a test farm consisting of about 100 to 200 servers that would compile the code, build a new Oracle DB, and run the millions of tests in a distributed fashion.
- Go home. Come the next day and work on something else. The tests can take 20 hours to 30 hours to complete.
- Go home. Come the next day and check your farm test results. On a good day, there would be about 100 failing tests. On a bad day, there would be about 1000 failing tests. Pick some of these tests randomly and try to understand what went wrong with your assumptions. Maybe there are some 10 more flags to consider to truly understand the nature of the bug.
- Add a few more flags in an attempt to fix the issue. Submit the changes again for testing. Wait another 20 to 30 hours.
- Rinse and repeat for another two weeks until you get the mysterious incantation of the combination of flags right.
- Finally one fine day you would succeed with 0 tests failing.
- Add a hundred more tests for your new change to ensure that the next developer who has the misfortune of touching this new piece of code never ends up breaking your fix.
- Submit the work for one final round of testing. Then submit it for review. The review itself may take another 2 weeks to 2 months. So now move on to the next bug to work on.
- After 2 weeks to 2 months, when everything is complete, the code would be finally merged into the main branch.
The above is a non-exaggerated description of the life of a programmer in Oracle fixing a bug. Now imagine what horror it is going to be to develop a new feature. It takes 6 months to a year (sometimes two years!) to develop a single small feature (say something like adding a new mode of authentication like support for AD authentication).
The fact that this product even works is nothing short of a miracle!
I don't work for Oracle anymore. Will never work for Oracle again!
This guy has gone to the zoo and interviewed all the animals. The tiger says that the secret to success is to live alone, be well disguised, have sharp claws and know how to stalk. The snail says that the secret is to live inside a solid shell, stay small, hide under dead trees and move slowly around at night. The parrot says that success lies in eating fruit, being alert, packing light, moving fast by air when necessary, and always sticking by your friends.
His conclusion: These animals are giving contradictory advice! And that's because they're all "outliers".
But both of these points are subtly misleading. Yes, the advice is contradictory, but that's only a problem if you imagine that the animal kingdom is like a giant arena in which all the world's animals battle for the Animal Best Practices championship [1], after which all the losing animals will go extinct and the entire world will adopt the winning ways of the One True Best Animal. But, in fact, there are a hell of a lot of different ways to be a successful animal, and they coexist nicely. Indeed, they form an ecosystem in which all animals require other, much different animals to exist.
And it's insane to regard the tiger and the parrot and the snail as "outliers". Sure, they're unique, just as snowflakes are unique. But, in fact, there are a lot of different kinds of cats and birds and mollusks, not just these three. Indeed, there are creatures that employ some cat strategies and some bird strategies (lions: be a sharp-eyed predator with claws, but live in communal packs). The only way to argue that tigers and parrots and snails are "outliers" is to ignore the existence of all the other creatures in the world, the ones that bridge the gaps in animal-design space and that ultimately relate every known animal to every other known animal.
So, yes, it's insane to try to follow all the advice on the Internet simultaneously. But that doesn't mean it's insane to listen to 37signals advice, or Godin's advice, or some other company's advice. You just have to figure out which part of the animal kingdom you're in, and seek out the best practices which apply to creatures like you. If you want to be a stalker, you could do worse than to ask the tiger for some advice.
---
[1] The ants are gonna win. Hölldobler and Wilson told me so.
Yes, there are tons of resources but I'll try to offer some simple tips.
1. Sales is a lot like golf. You can make it so complicated as to be impossible or you can simply walk up and hit the ball. I've been leading and building sales orgs for almost 20 years and my advice is to walk up and hit the ball.
2. Sales is about people and it's about problem solving. It is not about solutions or technology or chemicals or lines of code or artichokes. It's about people and it's about solving problems.
3. People buy 4 things and 4 things only. Ever. Those 4 things are time, money, sex, and approval/peace of mind. If you try selling something other than those 4 things you will fail.
4. People buy aspirin always. They buy vitamins only occassionally and at unpredictable times. Sell aspirin.
5. I say in every talk I give: "all things being equal people buy from their friends. So make everything else equal then go make a lot of friends."
6. Being valuable and useful is all you ever need to do to sell things. Help people out. Send interesting posts. Write birthday cards. Record videos sharing your ideas for growing their business. Introduce people who would benefit from knowing each other then get out of the way, expecting nothing in return. Do this consistently and authentically and people will find ways to give you money. I promise.
7. No one cares about your quota, your payroll, your opex, your burn rate, etc. No one. They care about the problem you are solving for them.
There is more than 100 trillion dollars in the global economy just waiting for you to breathe it in. Good luck.
I left home at 15 and some adults who worked together let me move in with them and be their maid. I paid $150 a month in rent and got $10 a month to live on. I worked out how to live off Milo (a Jamaican malt supplement), Chips Ahoy cookies (1/2 a cookie a day for a treat) and dumpster dived vegetables (mostly cabbages and carrots). I lived like this for years, when I got my first real jobs I made sure to save at least 80% of every paycheck. I retired at 35 and now I write about the apocalypse (one feature film, various shorts, one book, graduate degree in Equity Studies/lots of essays and conferences). I know live a very easy comfortable life, but most see me as bizarre because i have no furniture and do not buy any beauty products (I've never purchased shampoo or paid for a hair cut - I am female). There is an equal proportion of happy memories scattered throughout my life, some of my happiest were when I had literally nothing but one dress and 4 pairs of stolen Zellers underwear and was sleeping in a car. The form of our lives impoverishes experience of reality as much, if not more, as the content. It's a whole we do not see for the misplaced desire for displays of wealth over relationships with everything and everyone.
This is a great post and so spot on. At some point in my career my 'review prep' (which was the time I spent working on my own evaluation of my year at a company) became answering the question, "Do I still want to work here?" I categorize my 'review' in four sections (which are each rated at one of five levels, needs improvement, sometimes meets expectations, meets expectations, sometimes exceeds expectations, or consistently exceeds expectations)
I start by reviewing how I'm being managed, I expect someone managing me to be clear in their expectations of my work product, provide resources when I have identified the need to complete jobs, can clearly articulate the problem I am expected to be solving, and can clearly articulate the criteria by which the solution will be evaluated.
Second I review my co-workers, using a three axis evaluation, can I trust what they say to be accurate/honest, can I count on them to meet their commitments, and are they willing to teach me when I don't understand something and conversely learn when their is something they do not know.
Third I review what level of support do I get to do my job. Am I provided with a workspace where I can get work done? Do have have the equipment I need to do what is being asked? Is my commute conducive to the hours required? And finally and most important, does this job allow me to balance work obligations and non-work obligations?
Fourth I review whether or not the company mission, ethics, and culture is still one that I wish to be a part of. Am I proud of the company's mission? Do I believe that the leadership will make ethical calls even if doing so would mean less profit margin? Can I relate to and am I compatible with the values that my co-workers espouse and the actions they take? (this is the "company culture" theme, is it still a company that fits me culturally)
A company that receives lower than a 3.0 rating I put on a 90 day "company improvement plan" (CIP). I bring issues to the leadership who are in a position to address the situations that I've found wanting and try to secure their commitment to change. If after 90 days they haven't been able to (if they choose not to they're done right away), then I "fire" the company and work to process my exit as expeditiously as possible.
I took Equifax to small claims. When that didn't pay up, I appealed and removed to higher courts. I continued doing this until it wasn't worth it for me. I think I cost Equifax a total of at least $20K USD. They had to keep flying lawyers back and forth from Atlanta to where I lived and put them in hotels.
I think I got them to spend more than I would have received in any settlement.
Fun note, my judge in small claims dismissed my case but said the following before dismissing it, "Mr. tuxxy, I would not trust Equifax with my dog's vaccination records. I'm absolutely appalled in the lack of protections Equifax provides for the personal data of Americans, however I'm afraid I don't see a case for negligence..."
She lectured Equifax's lawyers a bit on what a shitty offer credit monitoring was for the loss of my PII for a bit, then sent us out.
I trolled their legal team a bit near the end and tried to settle for $3.50 after mediation failed, but I wanted them to refer to the $3.50 as "tree-fiddy" in the settlement, but they refused. Oh well...
I worked in over 10 films as a camera guy/DOP. I think what grain can really do, is to give you the feeling you are looking ONTO a picture rather than INTO a world. They might not know it, but by using this aesthetics, they say: look at the picture of me, rather than "look at my world".
Nostalghia might be a factor for sure, but the driving factor is materiality. Many of us grew up in a very material world, this included film and photography. Everybody tried their best to make the media invisible (get rid of vinyl crackle, tape saturation/noise, colour shifts of badly treated optochemical films, glitches in maladjusted VHS heads, etc.) Today it is the polar opposite. Because the digital image can be so perfect, young people feel the urge to give it materiality, they add vinyl crackle to their music, they imitate the mistakes of old technology to make what they do something you look ONTO rather than INTO.
As you become successful in your field (or wherever), and further internalize the habits that are necessary to be successful, it's clear that many of these things are easy to do, it's just that people don't want to do them.
In other words ... it's obvious that many people don't want to be successful, and if they were to introspect deeply, they would see this clearly. In fact what they want is to be somewhere comfortable in the middle of the herd, not having to do too much work.
Most people want to be comfortable, not 'successful' in a way that requires ambition. But many people are brainwashed enough by the rhetoric of success that they don't realize it's not what they want.
There's also something I haven't figured out yet. Every time I give advice, I get a number of responses from people with self-defeating attitudes, explaining how this advice can't possibly apply to them because blah blah blah. These people build up belief structures that are obviously intended to keep them mired in their current situation, smelling of low self-esteem and defeatism. "Obviously" it's better not to be stuck in these belief structures, yet people will defend them vigorously, and in some cases fiercely. I don't yet fully understand why, except maybe that if someone believes there is a solution to their problem, then it must be their fault that they haven't solved it, and/or that there will be a clear failure that is their fault if they attempt to solve it.
My hypothesis is that everybody fakes their way into Fashion Week. It's all one giant LARP event that somehow spun out of control, and now nobody knows how it manages to keep going all by itself without any GMs, or how to stop it, if there were somehow an emergency that required it to not take place.
Now go re-read the Verge article or watch the video, presuming that everybody is faking, and see if the hypothesis can be falsified at any point.
The part where he gets the badge? That's just some person with a badge printer, playing the part of the registrar.
That part where he's trying to convince Italians that he's Italian? They're not Italian either. "Oh, of course I'll speak English to you, another completely genuine Italian person, for the sake of your photographer, obviously."
It's sort of surreal, actually. Because then you can expand the hypothesis outside of Fashion Week, and it never stops.
Being alone and hiking and camping in the wilderness without human contact for longer period can be amazing experience. There can be initial anxiety and intense desire to go back after romance goes away and your internal shit comes to light. When there is constant need for do chores to survive but also free time and no human contact, no books, radio or music, mind gradually settles into itself.
It's like coming from bright light into a dark room. Gradually your eyes adjust and you start to see more. Coming back into the civilization is similar to someone pointing flashlight into your eyes. So much external triggers for behaviour. Realizing that I'm not actually me with other people and I'm disappearing into network of others. Me with others is mainly just bunch of triggers that fire based on conditioning.
If I can feel intense otherworldliness from just week or month alone, I imagine that if someone spends decades alone, civilization might seem like miserable alien ant colony. Everybody is responding to commands from others and carrying stuff they don't care about.
ps. It also can trigger psycosis, panic or some kind of madness (prairie fever, cabin fever) in some people. Romanticizing it as escape from all your problems might give people the wrong idea.
Of course there can be value in a synopsis. The synposis in your comment was fine. But "tl;dr" doesn't add anything about the topic at hand. What it signals is: "you don't need to read anything else". On HN, readers should be reading for themselves, thinking and deciding this for themselves.
We want users to have to work a little. The key is "a little". It's not like it's hard, but it requires engaging one of the slower cognitive gears. That gear shift is annoying if we expect everything to be laid out for us. On HN we try to thwart that expectation. Why? We want fiber—thoughts and comments of substance.
It's fashionable to talk about opinionated design. One opinion baked into HN's design is: this should be the kind of site that people who don't want to be reflective find boring. When pg was showing me how to moderate HN he said the front page should be "bookish".
You wrote something here that I find fascinating:
> We all of us value substance and content, of course. (Need I really write that? Really? C'mon man.)
What's fascinating is the "of course". It seems so obvious that it's irritating to have to say it. It's such a cliché that there's even a cliché follow-up: "But we are all of us limited in our time and attention".
But, on reflection, it's not true. We mostly value a stimulus-response reward cycle. We value having our preconceptions mirrored back to us. We value the feeling that we understand things (recognition) more than the effort of working through material in order partly to understand it. This is also the dynamic in flamewars, so substance and civility are related.
There can't be many of us who are free from this—certainly not me. But HN is an experiment in trying to grapple with this problem on the internet (https://news.ycombinator.com/newswelcome.html). That's what this site is. It may not do it well, and is probably doomed, but the driving idea has always been "maybe we can stave off doom a little longer".
“Finishing a good book is like leaving a good friend.”
― William Feather
2) What is the author doing in actual reality that makes it so pale compared to VR?
It's interesting that the first example brought up is about interacting with a phone.
For god's sake man! Play a sport, have sex, go for a walk and smell the leaves, go for a swim in the ocean. Sweat, strain, climb and explore. Be an _animal_ because that's what we are!
Go and get barrelled on a wave in the ocean and then come back and tell me that VR is better. :-)
It is close to 25 million lines of C code.
What an unimaginable horror! You can't change a single line of code in the product without breaking 1000s of existing tests. Generations of programmers have worked on that code under difficult deadlines and filled the code with all kinds of crap.
Very complex pieces of logic, memory management, context switching, etc. are all held together with thousands of flags. The whole code is ridden with mysterious macros that one cannot decipher without picking a notebook and expanding relevant pats of the macros by hand. It can take a day to two days to really understand what a macro does.
Sometimes one needs to understand the values and the effects of 20 different flag to predict how the code would behave in different situations. Sometimes 100s too! I am not exaggerating.
The only reason why this product is still surviving and still works is due to literally millions of tests!
Here is how the life of an Oracle Database developer is:
- Start working on a new bug.
- Spend two weeks trying to understand the 20 different flags that interact in mysterious ways to cause this bag.
- Add one more flag to handle the new special scenario. Add a few more lines of code that checks this flag and works around the problematic situation and avoids the bug.
- Submit the changes to a test farm consisting of about 100 to 200 servers that would compile the code, build a new Oracle DB, and run the millions of tests in a distributed fashion.
- Go home. Come the next day and work on something else. The tests can take 20 hours to 30 hours to complete.
- Go home. Come the next day and check your farm test results. On a good day, there would be about 100 failing tests. On a bad day, there would be about 1000 failing tests. Pick some of these tests randomly and try to understand what went wrong with your assumptions. Maybe there are some 10 more flags to consider to truly understand the nature of the bug.
- Add a few more flags in an attempt to fix the issue. Submit the changes again for testing. Wait another 20 to 30 hours.
- Rinse and repeat for another two weeks until you get the mysterious incantation of the combination of flags right.
- Finally one fine day you would succeed with 0 tests failing.
- Add a hundred more tests for your new change to ensure that the next developer who has the misfortune of touching this new piece of code never ends up breaking your fix.
- Submit the work for one final round of testing. Then submit it for review. The review itself may take another 2 weeks to 2 months. So now move on to the next bug to work on.
- After 2 weeks to 2 months, when everything is complete, the code would be finally merged into the main branch.
The above is a non-exaggerated description of the life of a programmer in Oracle fixing a bug. Now imagine what horror it is going to be to develop a new feature. It takes 6 months to a year (sometimes two years!) to develop a single small feature (say something like adding a new mode of authentication like support for AD authentication).
The fact that this product even works is nothing short of a miracle!
I don't work for Oracle anymore. Will never work for Oracle again!