Opens profile photo
Follow
Ajey Gore
@AjeyGore
learning and building journey , - built & scaled engineering, founded , spent a decade
Science & TechnologySingaporeajeygore.inJoined April 2011

Ajey Gore’s Tweets

Pinned Tweet
Thinking about old age, I should practice more meditation, eventually every sensory organ will degrade, May be only logical way to remain sane, in incommunicado state, is to go towards hours of meditation.
3
30
Messaging has killed the conversations! People don’t interact anymore, they just inform and inquire!
4
97
Laptop doubles up as power bank, a bulky one though, but if you are carrying it anyway, might as well use as power bank.
4
18
I think people have forgotten that we used to display user interface on html web front-end pre-javascript framework days. You can always render a plain html and it might be better, if you are building portals for internal consumption. Less accidental complexity.
8
45
Design, Product and engineering should listen to each others pain and understand where they are heading together. And the crucial question to ask - how do we enable each other
1
36
Show this thread
If you have 100-200 sized engineering/product/design org, then having separate engineering/product/design townhallon or all-hands is the first step to create silos and beginning of broken communication.
2
102
Show this thread
Storytelling is one of the most important tasks not only for founders but early-stage CTOs/CPOs as well. If you need to hire people, you must be able to tell them your story, why your company's story is the most exciting journey they should be part of.
2
77
Looking at a team it’s like looking into a kaleidoscope, move a bit, you get a whole new perspective on the same team.
12
Two most important things we should do day minus one - observability and testing, so that we know things break down before users do. -
1
62
Almost every CTO is the first SRE or (devops) downtime ninja. It almost always starts there… maybe because the buck finally stops there…
6
198
Fantastic and critical people will have a demand. Question is how do you define fantastic engineering talent? Or a PM or Designer?
3
20
some colleagues (or co-founders) are annoying siblings, but they are siblings after all.
13
To sum it up - first, prioritize the most important user persona, then within that, prioritize core features, what we stand for - anything that helps to get there should get prioritized, and following important thing - don't fall for non-functional "fun" engineering problems.
7
Show this thread
These "friend's persona" users don't mean bad; they mean well; it's just that they aren't our frequent users and don't represent critical mass. Also, they sometimes opine on tech choices, tools, and many more things... listen to them and filter out these requests with our needs.
1
5
Show this thread
One of the ways to think through this situation is to ask - is "our friend" persona a prominent one? and you may find it's not, then go back to solving and prioritizing for the most critical user persona that covers most of the use cases.
1
5
Show this thread
Sometimes, our close friends are not frequent users, but they have strong opinions on how some product features should be implemented or why this "feature" isn't there. it's elementary to fall into this trap, we start scrambling to prioritise that request.
1
4
Show this thread
I get this asked this question - how do you prioritize, I think one of the good solutions is to prioritize for user persona, ie, who is the MOST critical persona for your product. Obviously, it's the user... but there is a catch. There are few different types of same users. 1/n
3
27
Show this thread
If you can go gaga over Bengaluru over weather, Singapore has its place in terms of being a clean, disciplined, and safe country... way to go #Singapore.
5
77
Over engineering decisions for startups in early days - ideally you don’t need them day one. 1. Kafka 2. Distributed databases 3. Big query? 4. Mostly micro-services 5. Fully staffed SRE - ahem devops team 6. In-house small services because we can. What else?
44
488
3. For Fraud and Risk, in the early days, depend on a lot of manual analysis; once these analyses are proven, convert them to ML models for scale. Bonus: get a project manager, to manage all these strategic programs across your org. She is the one to keep the progress humming.
5
Show this thread
2. Setup guard rails before and after the code is pushed to production. Deploy code analysis, quality, and style checks. After production brings a lot of monitoring into place - monitor everything.
1
7
Show this thread
1. Definitely try to put in a generous bug bounty program; you will be surprised by how beneficial is ethical developer community! Also, you will have a huge hivemind to navigate you through security risks, and you will know about them almost before anyone. 2/3
1
5
Show this thread
A common question - how to deal with security risk in the early days of startups, and what's the right time for building a security team. As always, the answer is "Depends" there are no clear winners here, but here is my advice on how to approach security in startups. 1/3
4
27
Show this thread
In short, don’t hire devops people, but hire developers who can do more stuff around managing and automating infra, if org is too big then start a sre or platform engineering team.
Quote Tweet
While DevOps is the "practice" of let developers do the "things" usually done by the admins, SRE is the "way" to keep things stable while bringing reliability and scalability. Both make software upgrades easy and manageable. Please hire SRE people and make DevOps mainstream.
1
23
Built on WhatsApp for Business’ API, WATI has created smart tools & features for the app so that SMEs in emerging mkts can scale their customer support, engagement & acquisition🚀. Glad 2 have been a part of the journey w Bianca & Ken since 05
1
10
While DevOps is the "practice" of let developers do the "things" usually done by the admins, SRE is the "way" to keep things stable while bringing reliability and scalability. Both make software upgrades easy and manageable. Please hire SRE people and make DevOps mainstream.
4
26