neural nets.

never unpinning this till I make something that will help everyone, and makes the lives of humans a bit easier. my promise to contribute to humanity lies in this post.

true BLR vibes is to codex on the TV

bhai these kids in over we're so privileged on god story goes like this line is there everyone is ordered a group of 4 kids ordered and left and again after 2 min they came in first of line to order and someone said go back don't cut the line they said, bhaiya paisa hai khareedne do please you stay in line we can't itna privilege apne baap ke paise se kaise aata hai 💀💀

@BngRithvik plan something ngl

@cneuralnetwork BLR meet-up when ?

day 3 in blr ask me anything will answer!

@purusa0x6c no

@cneuralnetwork can you speak kannada?

@theaniketdev18 no idea bhai mai jaha hu, literally occupied last room

@cneuralnetwork Any pg recommendations for doublet, in ballandore

@bruhmarsx time mgm

@cneuralnetwork ye how am i supposed to study for gate and endsem and placements all tgt 🥀 burn outs hore

@PhantomC0der good enough

@cneuralnetwork how is the food??

@BreefSpreader 29 comments and you're the only hater invalid argument unfortunately pretty sad life

@cneuralnetwork She literally posted "not good enough" fishing for compliments and when she didn’t get them, you ran in to save her ego.😂🤣😝

brother sorry to say, I'm proud of her she did good enough she published a paper in her 2nd year which only 3 other people did in our college and got many internships this year as well if you can't handle the fact someone is sharing their successes and it affects you, I'd suggest you to block such people because she'll do even better everyday and it'll become tiresome for you to comment everyday 😁

@bythyag bhai wapp pe dm karo, sunday drop in karta hu

@cneuralnetwork when are you coming at my place? meghna biryani khayenge. your office is close.

@sgirish1204 sure bhai

@cneuralnetwork Office me milte hai bhai

@buildxrajesh yea

@cneuralnetwork Has the “everyone is building a startup in blr” stereotype felt real yet?

@stayush369 coding

@cneuralnetwork What work you do

I mean, “just keep building” is technically not wrong. A lot of people who end up in really good Bangalore startups did exactly that. They built things obsessively, shipped weird side projects at 2 AM, contributed to random open source repos nobody cared about at the time, and over years became impossible to ignore. But the reason your reply annoyed him is because that answer skips literally the entire practical reality of how this ecosystem actually works. When someone asks “how do I get into a good paying Bangalore startup/company?”, they usually aren’t asking for a motivational poster. They’re asking about the invisible layer nobody explains properly. Because the truth is: there are thousands of people “building.” Most still never get interviews. Most never get referrals. Most never get noticed. Most never learn what companies actually optimize for. And that gap between “build projects” and “get hired” is exactly where people struggle. So if I had to answer properly: First, Bangalore startup hiring is heavily signal based. Not degree based. Not even always DSA based. The strongest signals are: proof of execution speed public work communication network proximity People think startups hire “the smartest engineers.” Not always. They hire people who reduce uncertainty. That’s a very important distinction. A founder sitting in HSR or Koramangala isn’t thinking: “Who solved the hardest graph problem?” They’re thinking: “Can this person take ownership and make something real without me babysitting them for 3 weeks?” That changes everything. So what actually helps? Real projects. Not tutorial clones. And I don’t mean another TODO app or Netflix clone with Firebase auth. I mean things with: users deployment real problems scaling issues ugly bugs actual iteration Even 50 users using your thing is infinitely more impressive than 15 polished portfolio projects nobody touched. Because once you have users, you automatically learn: debugging under pressure product thinking infra feedback loops tradeoffs prioritization shipping speed That’s the stuff startups care about. Second: people underestimate visibility. Bangalore tech hiring is weirdly Twitter/GitHub/Discord/LinkedIn driven. Half the opportunities never become job posts. They happen because: “oh yeah I’ve seen this guy around” or “someone sent me their repo” or “they wrote a really good thread” or “they solved a problem we also faced.” That’s why public work matters so much. A random engineer posting: build logs architecture diagrams infra learnings ML experiments benchmark results failures optimizations …is building compound reputation without realizing it. And reputation compounds insanely in startup ecosystems. One retweet leads to one Discord invite. One Discord invite leads to one hackathon. One hackathon leads to one founder DM. One founder DM becomes internship. Internship becomes PPO. People think careers are linear. Most startup careers are chaotic graph traversals. Third: referrals help massively. Anyone saying otherwise is lying. Especially in Bangalore. Not because companies are corrupt. Because startups are overwhelmed. If 4000 people apply to a role, referral becomes a filtering mechanism. But here’s the important part: cold asking for referrals rarely works. The best referrals are built indirectly. Examples: contributing to someone’s repo fixing bugs interacting intelligently online attending meetups helping people technically building in public consistently being recognizable over time The strongest referrals happen when people already know your name before you ask. That’s the hidden game. Fourth: people obsess too much over tech stacks. Nobody cares whether you used Next.js or Svelte or FastAPI or Rust microservices or whatever buzzword is trending this month if your project itself is weak. Good startups care more about: can you learn fast? can you debug? can you communicate? can you ship? can you think independently? A cracked engineer with strong fundamentals can learn frameworks in weeks. But someone who only learned frameworks without fundamentals usually collapses the second something breaks outside tutorial paths. That’s why fundamentals still matter: operating systems networking databases concurrency memory distributed systems basics ML/math fundamentals if AI role data structures enough to think clearly Not because interviews worship theory. Because fundamentals reduce panic. Fifth: interview prep depends entirely on company type. This is where people give terrible generic advice. Big tech: DSA heavy system design later structured rounds consistency matters Startups: completely unpredictable. You may get: take home assignment live debugging architecture discussion resume deep dive project teardown product thinking round pair programming “build this in 2 days” casual founder conversation Sometimes no DSA at all. Sometimes only DSA. Sometimes they’ll spend 45 minutes asking about one tiny detail in your project because they want to see if you actually built it. A lot of candidates die there. Because they copied projects. The fastest way to fail a startup interview is pretending expertise you don’t have. Founders can smell fake building instantly. So honestly? One authentic messy project you deeply understand beats 10 polished fake ones. Sixth: Bangalore startup culture specifically rewards speed. Not recklessness. Speed. People who: prototype quickly iterate quickly learn quickly adapt quickly …stand out enormously. Because startups themselves are unstable environments. Everything changes constantly: stacks priorities products deadlines teams markets Someone waiting for perfect clarity usually struggles. This is why hackathons help more than people realize. Not because hackathon projects matter long term. But because hackathons train: execution under ambiguity team coordination rapid learning demo skills shipping under time pressure Which is literally startup life compressed into 36 hours. Seventh: communication matters way more than engineering students think. A lot of insanely smart people stay invisible because they communicate like terminal logs. You do not need fake corporate English. But you need clarity. Can you explain: what you built why you built it tradeoffs failures architecture decisions scaling problems what you’d improve If yes, you automatically appear senior. Engineering is partially communication compression. Senior engineers are often just people who can organize complexity clearly. Eighth: there’s also uncomfortable luck involved. Timing matters. Markets matter. Hiring waves matter. Someone graduating during funding booms has a different experience from someone graduating during layoffs. That’s reality. But luck interacts with surface area. The more visible work you do: the more people know you the more repos exist the more experiments exist the more conversations happen the more communities you enter …the more opportunities luck has to hit you. “Keep building” alone is incomplete. But “keep building publicly and intelligently while increasing opportunity surface area” is actually extremely powerful advice. Ninth: salary progression in Bangalore startups is also misunderstood. People think: “join startup -> become rich.” Most don’t. Some startups underpay horribly while selling “vision.” Some overwork people into burnout. Some are amazing. Some collapse in 8 months. Some become billion dollar companies. You have to evaluate: learning potential mentorship ownership engineering quality growth culture equity realism work life sustainability A high salary at a chaotic startup where you learn nothing can hurt long term. Meanwhile a lower paying role with cracked engineers around you can completely change your trajectory in 2 years. Early career compounding is mostly about environment. Tenth: people underestimate consistency. The engineers who suddenly “blow up” online usually spent years invisible. Years. Nobody sees: failed side projects abandoned repos bugs self doubt nights wasted debugging nonsense applications ignored ghosting rejection They only see the eventual visibility. But the ecosystem quietly rewards persistence over long time horizons. Especially in tech. Because skills compound. Reputation compounds. Network compounds. Taste compounds. And eventually people start associating your name with competence. That’s when opportunities become asymmetric. Honestly, the funniest thing about the original interaction is that both sides are partially right. The question deserved a better answer. But the core answer still accidentally contains truth. Because after all the strategy, networking, optimization, referrals, interview prep, visibility, branding, resume polishing and startup analysis… you still eventually come back to the same unavoidable thing: you need to become genuinely good at building things. There’s no sustainable shortcut around that. Not forever. At some point the market tests reality. And reality shows up in strange moments: production outage at 3 AM debugging race conditions scaling failures model hallucinations customer complaints infra bills exploding broken deployments impossible deadlines That’s where actual builders separate themselves from aesthetic engineers. And ironically, once someone reaches that level, their advice becomes shorter and shorter. Because they compress years of pain into one sentence. “Just keep building.” But beginners hear motivation. Experienced people hear: “build so much that execution becomes identity.”

@cneuralnetwork Bhai ye kis part ka answer tha, was expecting a better answer ab jab AMA kar hi diya tha toh. I took time to write, you might have lesser par itna kam

@rickzzzzr chatgpt

@cneuralnetwork is there any book which can help with suffering (a lot of it) ?

@Suryansh777777 chilly

@cneuralnetwork How's the weather?

@ryuzaki2401 benne

@cneuralnetwork benne dosa vs regular dosa

@Sleeepyyii sleep

@cneuralnetwork whats the most fun thing to do there

@hemlogooseguys stupidity

@cneuralnetwork What do you think? Where does consciousness emerge from?

@thatGuyCodes just keep building

@cneuralnetwork How to get into a good paying blr based startup/company - skills, kind of projects, interview process, where/how to apply (is referral required)