ankan sircar retweeted
Replying to @theojaffee
Prioritizing applications that actually improve people’s lives (eg health), rather than immediately going for raw economic value or intelligence. Obviously there are strong incentives to aim for the latter, which is another reason why coordination is important.
ankan sircar retweeted
Elon Musk fired 6,500 employees at Twitter.
A little birdie told me it's down to:
- 2 designers
- 6 iOS developers
- 20 web developers
- Around 1,400 sales and operations people
How is it possible that we are still using this website?
Two words:
Parkinson's Law.
Have you ever wondered why seemingly simple tech companies have tens of thousands of employees?
Sometimes, it's because they have huge sales forces or tech support/operations people.
But often it's also due to Parkinson's Law.
Parkinson's law is like lighter fluid for bureaucracy.
It's a business tapeworm that slowly eats away at companies, making them less and less efficient and innovative over time.
Parkinson's Law is the idea that the work will generally expand to the amount of time, budget, and number of people allocated to it, and no matter how many people you allocate to it, those people will feel busy.
They'll feel busy because, due to the excess time/slack in the system, they'll start focusing on less and less important tasks.
Here's how it manifests on an individual level:
Let's say you have a report due in a week.
The report might only take you around five hours to finish if you really focus and work efficiently. However, because you know you have a week to complete it, you might find yourself spending a lot more time on it than you need to.
You'll be more prone to distractions, take longer breaks, or perhaps decide to add more details, tables, graphs, and so forth.
Essentially, the task becomes more complex and time-consuming purely because you have more time in which to do it.
And here's how it manifests across organizations:
Imagine a big tech company. A social media company with various departments. Each department has tasks that it must complete to contribute to the overall productivity of the company.
Now, suppose each department is given a budget and a set amount of time to complete its tasks for the year.
According to Parkinson's Law, each department will use its entire budget and the entire allotted time, even if the tasks could have been completed more efficiently.
This is because as resources and time increase, departments tend to become more complex and less efficient.
For example, a department might add more steps to its procedures, requiring more approvals and creating more paperwork, which slows down the process.
Or it might use the full budget on additional personnel or equipment that doesn't necessarily improve productivity.
The department might also use the full budget to justify the same or larger budget for the next year, since budgets in many organizations are often determined based on the previous year's spending.
This is a phenomenon known as "budget padding" or "spend it or lose it" mentality.
Inefficiencies can also develop in staff allocation. If a department expands, it might add managerial positions that aren't strictly necessary.
More employees are hired to manage, creating layers of bureaucracy that may not contribute to productivity and can even slow decision-making.
I have seen this occur over and over again in my career. The larger the team, the larger the budget, the longer the timeline, the less gets accomplished.
I'm very curious to see how many more tech companies come to this realization.
So often, good times + revenue growth = Parkinson's Law.
ankan sircar retweeted
something I wrote to a colleague that I think is worth sharing more widely:
"Whenever you get comments from a reviewer, including myself, you should always remember they are imagining the book they want you to write, which may not be the book *you* want to write."
ankan sircar retweeted
"We’re going through history, right now, and Facebook is on the wrong side of it. No one wants that on their resume"
we developers cannot evade responsibility for the outcomes of the code we write.
daringfireball.net/linked/20…
ankan sircar retweeted
37Tbs....the portion of S3 traffic handled by the next generation load balancers in a single region #reInvent
ankan sircar retweeted
I just can't even. this is pure gold. culmination of what I've been trying to drive for years
AMAZING
#reinvent teapawt.net/marknca/status/9357428…
every CIO, CTO, and CISO should listen to this 5m segment from Stephen Schmidt
#reinvent #security #automation
ankan sircar retweeted
"It is dangerous to be right in matters where established men are wrong." Voltaire
ankan sircar retweeted
"It's better to get half the right thing available so it spreads like a virus. Once people are hooked...improve it."
Richard P Gabriel
ankan sircar retweeted
Software maintenance is not "keep it working like before." It is "keep being useful in a changing world".
@jessitron












