HN user

kislayverma

189 karma
Posts53
Comments30
View on HN
kislayverma.com 5y ago

A layman's guide to understanding the Cloud

kislayverma
49pts11
kislayverma.com 5y ago

The Golden Rule of Building Technical Platforms (Eat Your Own Dogfood)

kislayverma
8pts0
kislayverma.com 5y ago

Essential Highlights from “Thinking in Systems:A Primer”

kislayverma
1pts0
kislayverma.com 5y ago

Control “microservice hell” by layering domains using API Gateways

kislayverma
2pts0
kislayverma.com 5y ago

Independence, autonomy, and too many small teams

kislayverma
214pts173
www.kislayverma.com 6y ago

A layman's guide to distributed systems

kislayverma
3pts0
www.kislayverma.com 6y ago

A narrative approach to software design

kislayverma
1pts0
www.kislayverma.com 6y ago

Essential highlights from things every software architect should know

kislayverma
2pts0
www.kislayverma.com 6y ago

Considerations in Designing Distributed Systems

kislayverma
2pts0
www.kislayverma.com 6y ago

Simple checklist for reviewing code involving distributed systems

kislayverma
2pts0
www.kislayverma.com 6y ago

Launch Announcement: Rulette Home, Rulette Server, and More

kislayverma
1pts0
www.kislayverma.com 6y ago

All business problems are platform problems (a.k.a. dogfood everywhere)

kislayverma
1pts0
www.patreon.com 6y ago

The right abstraction for a business rule management system

kislayverma
1pts0
www.kislayverma.com 6y ago

An API strategy is not a Platform strategy

kislayverma
3pts0
news.ycombinator.com 6y ago

Ask HN: Would 3D architecture diagrams be more or less easy to understand?

kislayverma
1pts0
www.kislayverma.com 6y ago

Evolving business rules: a Rulette case study

kislayverma
3pts0
www.kislayverma.com 6y ago

Case Study: Building a taxation system with Rulette

kislayverma
1pts0
www.kislayverma.com 6y ago

Enforcing Constraints in Software Platforms

kislayverma
6pts0
www.kislayverma.com 6y ago

Building extensible data models in Platform systems

kislayverma
3pts0
www.kislayverma.com 6y ago

Learning React in 24 Hours

kislayverma
3pts0
www.kislayverma.com 6y ago

Control and Chaos in Platform Systems

kislayverma
21pts0
www.kislayverma.com 6y ago

Build extensible platform services with rule engines

kislayverma
2pts0
www.kislayverma.com 6y ago

Why I Love Eclipse Vert.x

kislayverma
3pts0
www.kislayverma.com 6y ago

Learning Golang in 24 hours by building a REST service

kislayverma
2pts0
www.kislayverma.com 6y ago

What's What in messaging jargon

kislayverma
1pts0
www.kislayverma.com 6y ago

Saving the Day with Continuous Refactoring

kislayverma
1pts0
www.kislayverma.com 6y ago

Throughput,capacity,and backpressure in distributed systems

kislayverma
4pts0
www.kislayverma.com 6y ago

The full stack team of the 20s must own its data

kislayverma
2pts0
www.kislayverma.com 6y ago

Analyze large scale architectures in broader terms than usual software “ilities”

kislayverma
2pts0
www.kislayverma.com 6y ago

Stop calling “marketplaces” by the name “platform”

kislayverma
2pts0

It sounds like the teams they ended up with just weren't cross-functional teams.

You are exactly right! And yet everyone thought they were organized by functions/objectives/OKRs or whatever. The blind spot is what I want to highlight here.

"Data-Delivery" is an anonymization. The team shipped a specific data set that I did not want to name.

That is well put, and I'm going steal some of those words in the follow-up I'm writing. I essentially feel that teams should grow when tech and process initiatives have led to creation of a whole new problem space that can be explored independently.

Consciously applying Conway's to identify communication boundaries sounds like a good way to get there.

That is correct. Wen I am wrote about "communication overhead" I meant having to talk to other teams to get the work done. Talking within the team (including PM, stakeholders etc.) is, IMO, desirable to set the overall team vision and to keep everyone on the same page.

I feel that once two teams, no matter how closely related, get the feeling of two different "mandates" (often personified by two managers, sometimes not), it becomes very expensive to keep them aligned. It is probably faster(wrt achieving the end goal) to go with fewer people in one team.

I agree. Looking at the "final practices" of a well-oiled team and just picking them up without any of the context about "why" they work "for that team" is half the reason no good idea (Agile, microservices, Jira) stays that way in software industry.

Very very awesome.

I'd take some trade-off between between crazy optimization and maintainability, but I'd definitely rather do this than slap on any number of frameworks because they are the new 'standard'.

Of course, the guy who has to maintain my code usually ends up crying like a little girl.

[dead] 13 years ago

Has this made headlines in all kinds of mainstream media yet? Because it bloody well should.

Three cheers for startups that manage this!

I attended a talk given by the Hyderabad Angels some time ago and found their outlook to be very strange. "We only fund companies with a proven and existing source of revenue. We don't fund ideas. We are here to sponsor growth of an established idea."

For angels level investors to take this line was very strange for me. It is likely due to this that mostly clones are getting funded in India.

True. I think if we analyzed the predictions of so called 'experts' before and after the fact of any event, the result would be extremely embarrassing.

But then, we should already know that.

>>> The key thing to remember is that you are not enriching your experiences by sharing them online; you’re detracting from them because all your efforts are focussed on making them look attractive to other people. >>> I wouldn't agree with that fully, because I (and I assume many others) often share stuff because I think it's cool and others might like to check it out. Think of the number of time you have discovered neat stuff because someone shared it.

So if you are sharing compulsively and simply in order to make yourself seem awesome, that's messed up - but it is also the cost of content discovery on an ever expanding internet.

The "Outliers" argument. The only way for a meritocratic system to work is by creating an absolutely level starting plane for all competitors. Which is in itself somewhat ironic because meritocracy reminds of capitalism (indirectly, I admit) while the level playing field requirement suggests a socialistic-ish system.

I haven't checked it out in detail, but Jeff Atwood's 'Discourse' (http://www.discourse.org/) does seem to have some of this stuff. It's a forum, but I wonder if it could be used as a blog.

And although I agree that the prevalent blogging software could use some lovin', but I hardly think it is as broken as the article seems to imply.

Bigoted idiots. This rant is surprisingly similar to press release before every western invasion of a country - freedom, threat to 'small' consumers etc.

"we will lose the opportunity to monitor and protect our privacy" Really now!!! So my privacy is best served by sharing all my data? This is so Orwellian. Noam Chomsky should have something to say on this :)