kislayverma

5 ms·

1.
by kislayverma 6y ago
Just fixed it. Sorry for that!
2.
A layman's guide to understanding the Cloud(kislayverma.com)
49 points by kislayverma 6y ago|11 comments
3.
The Golden Rule of Building Technical Platforms (Eat Your Own Dogfood)(kislayverma.com)
8 points by kislayverma 6y ago|0 comments
4.
Essential Highlights from “Thinking in Systems:A Primer”(kislayverma.com)
1 points by kislayverma 6y ago|0 comments
5.
Control “microservice hell” by layering domains using API Gateways(kislayverma.com)
2 points by kislayverma 6y ago|0 comments
6.
by kislayverma 6y ago
>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
7.
by kislayverma 6y ago
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 expl
8.
by kislayverma 6y ago
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
9.
by kislayverma 6y ago
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, Ji
10.
by kislayverma 6y ago
I'm still writing it :)
11.
Independence, autonomy, and too many small teams(kislayverma.com)
214 points by kislayverma 6y ago|173 comments
12.
A layman's guide to distributed systems(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
13.
A narrative approach to software design(kislayverma.com)
1 points by kislayverma 6y ago|0 comments
14.
Essential highlights from things every software architect should know(kislayverma.com)
2 points by kislayverma 6y ago|0 comments
15.
Considerations in Designing Distributed Systems(kislayverma.com)
2 points by kislayverma 6y ago|0 comments
16.
Simple checklist for reviewing code involving distributed systems(kislayverma.com)
2 points by kislayverma 6y ago|0 comments
17.
Launch Announcement: Rulette Home, Rulette Server, and More(kislayverma.com)
1 points by kislayverma 6y ago|0 comments
18.
All business problems are platform problems (a.k.a. dogfood everywhere)(kislayverma.com)
1 points by kislayverma 6y ago|0 comments
19.
The right abstraction for a business rule management system(patreon.com)
1 points by kislayverma 6y ago|0 comments
20.
An API strategy is not a Platform strategy(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
21.
Ask HN: Would 3D architecture diagrams be more or less easy to understand?
1 points by kislayverma 6y ago|0 comments
22.
Evolving business rules: a Rulette case study(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
23.
Case Study: Building a taxation system with Rulette(kislayverma.com)
1 points by kislayverma 6y ago|0 comments
24.
Enforcing Constraints in Software Platforms(kislayverma.com)
6 points by kislayverma 6y ago|0 comments
25.
Building extensible data models in Platform systems(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
26.
Learning React in 24 Hours(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
27.
Control and Chaos in Platform Systems(kislayverma.com)
21 points by kislayverma 6y ago|0 comments
28.
Build extensible platform services with rule engines(kislayverma.com)
2 points by kislayverma 6y ago|0 comments
29.
Why I Love Eclipse Vert.x(kislayverma.com)
3 points by kislayverma 6y ago|0 comments
30.
Learning Golang in 24 hours by building a REST service(kislayverma.com)
2 points by kislayverma 6y ago|0 comments

More ›