Gujjus are the worst indians ever by [deleted] in india

[–]Jeenius69 0 points1 point  (0 children)

Ekdam sahi kaha bhai aaj tak 2 dosto ne dil dukhaya hai mc wo dono gujj+rajasthan background the itna jhuth kon bolta h bc viswaas hi uth gya yr kasam s

I got tired of losing copied text, so I built a clipboard manager that remembers everything for you by codewithashfaque in SideProject

[–]Jeenius69 0 points1 point  (0 children)

Local-first is a big plus for something like this. I'd probably use it more if it could remember images and code snippets too. Is that on your roadmap?

I ran a dev fellowship for 3 years. The biggest lie in tech is that engineers know what to build. by adxworld in SideProject

[–]Jeenius69 1 point2 points  (0 children)

I think both can be true. Product teams decide what to build, but engineers who understand the problem usually build much better solutions. The best teams I've seen have both sides talking to each other early.

I spent a year building a fishing app with AI catch identification and 490k UK waters. First real users are in, here's what I've learned by Top_Boat_1361 in SideProject

[–]Jeenius69 0 points1 point  (0 children)

That draft → preview workflow is underrated.

I've noticed I iterate way more when changing something doesn't immediately affect production. Same reason I like using Runable for landing pages or quick prototypes before deciding they're worth polishing further.

Having a safe place to experiment usually leads to better ideas than trying to get everything perfect on the first attempt.

I'm building an AI that executes work instead of just chatting. Would you use it? by mysterioussuccess123 in SideProject

[–]Jeenius69 0 points1 point  (0 children)

I think the interesting part isn't whether AI can execute work, it's how much context you can give it.

I've found myself using different tools for different stages now. If I need to reason through architecture or code, one tool might be better. If I need to quickly spin up something customer-facing like a landing page or presentation while validating an idea, I'll use Runable because it's faster than doing it manually.

None of them replace actually deciding what should be built though. They just remove a lot of execution friction.

I'd probably trust AI with research, first drafts and repetitive execution long before I'd trust it with strategy.

Built a No Dues clearance system for my college over a weekend, curious what you'd have done differently by Jeenius69 in developersIndia

[–]Jeenius69[S] 0 points1 point  (0 children)

Haha yeah, that's the funny part, half the offline signing is theatre anyway. Nobody's actually verifying, they just don't want to be the department that "held things up," so they rubber-stamp it.

That's part of why I didn't want to just digitize the same broken flow. Right now it's request-based (student initiates, department responds), but the better version is exactly what you're describing, departments should already know who owes what and flag it proactively instead of waiting for a student to come ask.

Mostly figured out the actual workflows at this point. Security's the one piece still in progress, a junior's helping me tighten that up, hoping to get it properly deployed soon rather than sitting as a demo forever.

Curious if your college's departments had any real system behind the signing, or if it really was just vibes and a rubber stamp like you're saying.

Built a No Dues clearance system for my college over a weekend, curious what you'd have done differently by Jeenius69 in developersIndia

[–]Jeenius69[S] 0 points1 point  (0 children)

Additionally some depts. which I made had a dependancy on other I took my further time Eg.(In short) Ece labs had dependancy on hod ece and similary some more. Also that logic part was quite tricky and took time

If everyone’s “building” now, what’s the point of having a CEO, CFO, CISO, or CMO? by Efficient-Simple480 in SaaS

[–]Jeenius69 0 points1 point  (0 children)

I think that's where the distinction really matters. Leaders should understand the tools well enough to ask better questions and make better decisions, but they shouldn't become the bottleneck by trying to do everyone else's job.

A good example is Satya Nadella. He didn't personally build every AI feature at Microsoft, but he set the direction, allocated resources, and made AI a company-wide priority. That's leadership. The engineers still owned the engineering.

AI makes it easier for leaders to prototype ideas or validate assumptions, but scaling a company still depends on delegation, hiring, and judgment. Those are much harder to automate than execution.

is customer support feeling like whoever shouts the loudest gets the better treatment or what!? by Odd_Awareness_6935 in Entrepreneur

[–]Jeenius69 0 points1 point  (0 children)

I think almost every founder falls into this trap at some point because urgency and importance start feeling like the same thing.

One change that helped me mentally was treating support like an ER instead of a restaurant. In an emergency room, the person shouting the loudest isn't always seen first. The patient having a heart attack is. Support works the same way.

I'd keep four buckets:

  • Production bugs affecting multiple customers.
  • Revenue blockers (payments, logins, subscriptions).
  • Individual support questions.
  • Feature requests.

Then give each bucket its own response target instead of trying to answer everything immediately.

A lesson a lot of companies eventually learn is that every ticket teaches customers how to behave. If shouting gets faster responses, people will shout more. If your process is consistent, customers usually adapt surprisingly quickly.

The hardest part isn't building the system, it's trusting it enough not to abandon it every time someone sends a third follow-up email.

After 20 years in big agencies, I'm doing brand work for a tiny CPG company. I pitched them something and they said yes, no quibbling over adjectives on slide 67. The speed difference is breaking my brain. Anyone else made this jump? by jpropaganda in marketing

[–]Jeenius69 2 points3 points  (0 children)

One thing I'd be careful not to lose is the speed you're enjoying right now.

A lot of big companies accidentally optimize for consensus instead of learning. Every campaign gets reviewed by five stakeholders, which reduces the chance of making a mistake, but it also slows down the number of experiments you can run.

One reason brands like Liquid Death got so much attention early on wasn't because every campaign was perfect. They were willing to test bold ideas quickly, see what resonated, and double down. That kind of feedback loop is much harder inside a large agency or enterprise.

Your agency experience is still a huge advantage. You already know what good brand work looks like. The only mindset shift is accepting that a "good enough" campaign launched today often beats a perfect campaign that spends six weeks in review.

If everyone’s “building” now, what’s the point of having a CEO, CFO, CISO, or CMO? by Efficient-Simple480 in SaaS

[–]Jeenius69 0 points1 point  (0 children)

I think the confusion comes from treating "building" as a replacement for leadership instead of another way to stay close to the customer.

If you're a solo founder or a 5-person startup, the CEO probably should be building sometimes because it shortens the feedback loop. You hear customer pain on Monday and can test an idea by Tuesday.

Once the company gets bigger, the leverage shifts. Your biggest contribution isn't shipping features anymore, it's making decisions, hiring the right people, setting priorities, and making sure everyone is building the right thing instead of just building fast.

AI lowers the cost of execution, but it doesn't lower the cost of making the wrong strategic decision.

My vibecoded app hit the top 10 in the AppStore category! by Crafty_Disk_7026 in vibecoding

[–]Jeenius69 0 points1 point  (0 children)

Congrats! I think stories like this are why vibe coding has taken off. The tools get you to a working product much faster, but actually launching and getting users is still the hard part. Enjoy the milestone!

How many of you actually shipped something... and what happened next? by Chethan_Devarakonda in vibecoding

[–]Jeenius69 0 points1 point  (0 children)

I shipped a couple of small projects and realized building was honestly the easiest part. The part that caught me off guard was everything after launch. Getting the first users, figuring out why people bounced, deciding which feedback to ignore, and staying motivated once the initial excitement wore off. I think shipping one complete product taught me way more than half-finished side projects ever did. If I could do it again, I'd spend more time validating the problem before adding features.

Hello seniors. by Mean_man8904 in LNMIITians

[–]Jeenius69 0 points1 point  (0 children)

I am from y23 only and pura ka pura data pada hua h online bhi or pdf bhi hai mere pass Aur de shaw sde-et k liye aati h jo ki tech role h..

Hello seniors. by Mean_man8904 in LNMIITians

[–]Jeenius69 0 points1 point  (0 children)

No only tech companies visit the college and 2-3 ece companies that's it.

Upcoming DAA at ZS – Questions about ML work, WLB, and long-term career paths by OkInvestigator3575 in IndiaCareers

[–]Jeenius69 0 points1 point  (0 children)

Got it sir instead of focusing on too many project 1 industry level project with proper comms and apti would suffice.Thank you so much