Bhuvaneswaran Mohan

Great insights in simple words. Please read it like 100 times!

5

 𝗔𝗿𝗲 𝗮𝗻𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗴𝗼𝗼𝗱? This elegant, seamless animation shared in the post below is very appealing. But is it comforting when users are browsing the site and toggling between pages multiple times, especially on a site like Airbnb? Such intense animation will surely cause discomfort to motion-sensitive people. Especially for a travel app, when users are walking or moving in a vehicle if they constantly see these animations for a long duration, they may experience motion sickness. 𝗗𝗼𝗲𝘀 𝘁𝗵𝗮𝘁 𝗺𝗲𝗮𝗻 𝗮𝗻𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗴𝗼𝗼𝗱? In my opinion, animations are beneficial when you are trying to convey an experience or tell a story about your product. However, if your website or app provides a large catalogue of items where users are expected to browse through many options before making a purchase, then it is not a good decision to have animations on your website. Be very particular when adding animations to your website. While animations might enhance the look and feel and make your site very appealing, they might also impact the overall interactive time on your website, which you definitely want to increase. Some supporting research says: 1. 𝗗𝗶𝗴𝗶𝘁𝗮𝗹 𝗘𝘆𝗲 𝗦𝘁𝗿𝗮𝗶𝗻 (𝗗𝗘𝗦): Prolonged use of digital screens, including viewing animations, can lead to digital eye strain (DES), characterized by symptoms such as dryness, irritation, blurred vision, headaches, and difficulty focusing. This is especially prevalent among individuals who use computers and smartphones extensively. 2. 𝗠𝗼𝘁𝗶𝗼𝗻 𝗦𝗲𝗻𝘀𝗶𝘁𝗶𝘃𝗶𝘁𝘆: Users with motion sensitivity can experience discomfort and even nausea from intense animations. This is particularly problematic for applications used in dynamic environments, such as travel apps, where users might be on the move and more prone to motion sickness. 3. 𝗜𝗺𝗽𝗮𝗰𝘁 𝗼𝗻 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆: Digital eye strain affects comfort and reduces productivity and accuracy in tasks performed on digital devices. Continuous exposure to animations and other dynamic elements can exacerbate these issues. 4. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗥𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀: To mitigate these effects, it is advised to use animations sparingly and strategically. Simple and purposeful animations that enhance user experience without overwhelming them are recommended. Additionally, providing users with options to reduce or disable animations can help cater to those who are sensitive to motion. #UserExperience #WebDesign #UXDesign #MotionSensitivity #WebDevelopment #Accessibility #TechHealth #Productivity #TechTips #WebAccessibility #DesignThinking #UserComfort #WebAnimation

17

If you doubted the rise of India as a powerhouse, Pine Labs, a significant fintech player, is now relocating its headquarters from Singapore to India following approval from a Singapore court. This strategic shift mirrors other successful Indian startups like PhonePe, Razorpay, and Groww, embracing the trend of ‘reverse flipping’. The move signifies growing confidence in the Indian market and its potential. Key factors enabling this move include: - Favorable economic policies - Growing domestic market - Increasing investor confidence - Greater certainty of an exit at a higher valuation - Ease of accessing capital - Regulatory changes - Maturing capital markets - Cost-effective listing process All great signs for India! #India #Fintech #PineLabs #Startups #BusinessGrowth

92

2 Comments

🌍❤️♾️🗝🔓⚡️🌅🧬🌌 My apologies to all sending msg's to my inbox. I have been quite busy as of late. 🌍🌅🌌⚡️📞☎️ Real #GENESIS #EPOCH "System Contracts are contracts initialized during the Genesis block." 0x-System Contract Installation- MasterKeys- Genetic Energetic Codex validation implementation #DIVINE MECHANISMS #GalacticTrust #MasterRoot #BlockchainUniverse #PureQuantum #CryptoScience #QuantumNodeNetwork

5

2 Comments

Most interviewers approach system design interviews the wrong way. It’s a big hiring scam. I find it pointless when interviewers ask irrelevant questions to a person who has worked for 5 years in edtech, fintech, or any other domain. They will ask you about Netflix system design. How will he be able to answer such a complex topic? 2 things can happen: 1- Either he will not be able to answer 2- He has crammed the answer from resources Both of these things show he doesn’t have hands-on experience. Interviewers don’t want both of them. They want candidates who can give real-time solutions. System design complexities need real-time solutions. But it can’t happen if we ask such questions. Rather than focusing on their problem-solving ability or how quickly they deliver the solutions. Interviewers tend to judge on: -technical knowledge of the position they are applying for. -their need to change the domain, which they don't appreciate Rather, the interviewer should ask questions from their fields to know their knowledge. Obviously, none of us has worked in 1 domain at one point or the other. We all have changed. Hiring managers do not encourage the changing of multiple domains. They judge you by changing one. No matter how good you are. Interviewers should ask questions that should be related to the field. Or something general anyone can attempt. Good interviewers focus on their general awareness of how you can solve problems in real-time. If you’re not doing that, that is just a waste of time for the individual.

78

7 Comments

Somehow, I ended up creating yet another effect system. JIO is a very basic effect system in Java, equipped with all the classic functional operators. It allows handling, transforming, and composing different effects, as well as performing asynchronous computations using VirtualThreads or parallel asynchronous execution with StructuredTaskScope. https://lnkd.in/eUaw7f8J #functionalprograming #opensource #java

3

2 Comments

Being comfortable with chaos is a great skill for a software engineer There is always uncertainity - Changing requirements - Changing priorities - Re-orgs - Layoffs - Changing timelines The art is to keep moving and keeping your sane. Chaos is where growth happens. #softwareengineering #chaos

169

4 Comments

NoBroker.com Your app and services are degrading slowly. You guys have added a bunch of new services to your platform and in doing so, the focus from the core product seems to have shifted. I guess it's time to shed the excess weight those product and growth managers have added by showing you hockey curve numbers of revenue growth. Empower your engineering to deliver quality releases of your app. Reasons : - Your RM allocation for the topmost subscription ironically called "Super Relax Plan" is all over the place. - Property visits by FRMs are disconnected - I end up hitting a blank screen on almost every other deeplink you send me on WhatsApp! - Your web experience is lacking far behind your mobile experience and even that isn't consistent. App navigation is a pain! NoBroker Support #stability #product #prioritisation #userexperience

10

7 Comments

Wondering if Splitwise Inc. should re-evaluate its Pro subscription, currently priced at INR 149/month (INR 999/year) Here is pricing for a few other popular subscriptions in India: Netflix at INR 149/month (Mobile) Swiggy One at INR 75/month (starting) JioCinema at INR 999/year Assuming that primary target segment of Splitwise Inc. is bachelors, either in college or recently employed, is current pricing really the most optimal? Splitwise Inc. has 100M+ downloads on Android, so clearly it has resonated well with users However, recent reviews on Android play store show that users are not willing to convert to customers at current pricing. And they dislike the daily limits and Ads What can Splitwise Inc. do? Not to overstep, but I can think of a few things: 1) re-evaluate pricing - while revenue per customer will go down but more customers and hence higher overall revenue may make up for it (there are services such as Licious that ask for nominal subscription fee, offer significant value in return and keep you hooked) 2) offer group plans - splitting expenses is a group thing, why keep plans for individuals (not straightforward but can be worked out) 3) communicate benefits better - currently "Unlimited expenses" seem to be the only perceptible benefit, value of rest of the benefits can be communicated better (if users indeed see those as benefits) PS: all of this is based on very high level assumptions #product #monetization #pricing #subscription

168

19 Comments

My team and I were brainstorming the backend architecture of one of our core systems at Zomato. While creating the HLD diagram, we kept adding the most intuitive microservices and their interactions within the mesh. At this stage, we were only thinking in terms of abstract functionalities that these services would offer. Meanwhile, one of the team members proposed why we couldn't combine three (out of N 😛) services and just create one for now. From a bird's-eye view, it felt not so convincing. He explained the rationale by justifying the similarity in functionalities, flows, and data modeling. Trust me, that was not so intuitive when we were putting those three white boxes in the HLD diagram. I still had concerns about the independent scalability of those three pieces and possible challenges due to noisy neighbor issues. We asked ourselves a question: "What business outcomes do we expect from this system?" Ultimately, we got convinced with the suggestion of a merger. Learnings: 1) Technical experience in a business domain matters. Identifying similarity would have been a non-trivial job for someone who had not worked with those systems in the past. 2) Engineering efforts should (also) be traded off against the business outcomes. Engineers working in silos without a business goal generally end up overengineering the system. 3) For leads, leverage the technical expertise of your team members. Avoid being an expert in every aspect. #engineering #architecture #business #datamodeling #backend

940

24 Comments

myHQ by ANAROCK offsite- after 4 years: Team size grown 4X, Spread across 8 cities- We dearly needed it (it was only a question of when can we afford it). The team had promised a stellar Q4 of last FY, which made us profitable and honestly made this ask- very tough to refuse. And Goa was finally happening! We wrapped the offsite last week and loved every bit of it. Whether it was a game of tug of war, some impromptu dance performances or just a fun gala night- connecting with everyone on a personal level outside work was worth every second spent. 🎊 My 4 learnings:- - Zoom /Hangout/virtual can never replace in person- would have had 100 hours of calls with the person, but in person is just different. - Play more games/activities & less sessions (Specially for hybrid/spread out teams- bonding happens only over games, activities) - Outsource liquor arrangements to the Hotel/Organizer- not worth the hassle + whatever you arrange will never be enough! 🥂 - This idiotic, yet addictive game- "Ek machli pani me gayi, chappak" (Must play with friends: 4+ group) Looking forward to a much grander offsite in 2025 as the team targets another 3-4X jump this year. Onwards and upwards! 😃🙌

453

14 Comments

Worrying on stay relevant in the edge of AI / ML ?? Follow these two thumb rule .. 𝗙𝗶𝗿𝘀𝘁, try to do job in a company which keep adapting new technology and best engineering practice. 𝗦𝗲𝗰𝗼𝗻𝗱, try to be the first 30% in your team / company. For ex, there are companies which has timely adapted new tech like cloud, containerization, microservices etc and apply best engineering practice like agile, devops etc. Work in such company and be a valuable employee there .. you will always stay relevant in your area of work and nothing to worry then. #ai #ml #airtificialintelligence #machinelearning #softwarecompany #softwareengineers #jobs #stayrelevant

26

1 Comment

There are a lot of things software engineers are exposed to, only at higher levels in their careers. Seeing many hardworking people not steering themselves to reach those levels is concerning. SDE1s have the least responsibility in general. When I was SDE1, most of my work was already well defined by senior engineers. I didn't have too many decisions to make or think about the big picture. I just had to code the small building blocks of a project. And this wasn't too complicated either. In most cases it's an extension of the existing code base where you can copy paste with some changes. If we are quitting a big tech job as an SDE 1, we have only scratched the tip of the iceberg. There are certain scales, regulations, standards (like with security, accessibility, etc.), and budgets that we can get exposed to at big tech if we stay long enough and explore niche projects within a company. As an SDE 1, most of it is opaque to us. We are not making many design decisions. We are not requesting budgets. We are not managing resource allocations or maintaining them. We are not managing any people. We are probably not optimizing things for revenue. Our code might not even be generating any revenue. We are not the first person to reach out to, when an interdependent system fails. We have probably never driven a large scale migration involving 10s of components and dependencies. We are not working much in constraints of the big picture. Even as an SDE 2, we don't get full exposure to these things. It takes an SDE 3 or above to gain more autonomy, execute larger projects, and manage things at a higher level. Some of these things are only available in big tech. Alternatively, being an Engineer at a proper hypergrowth startup can help gain such exposure (or more unique experiences not found in big tech). Still, we might not get the scale or enterprise level security and accessibility exposure at such firms. And even this exposure doesn't come to everyone. We can spend 10+ in FAANG working on some niche product or maintenance without bothering about the ecosystem. So, it's important to self learn and explore proactively. Another approach could be to become the CTO of our own personal projects to steer our upskilling in the direction we want. But that obviously won't give us the kind of exposure we get while working with large scale distributed systems at big tech. Still, if learning hits a cliff somewhere, one can try. Who knows, maybe a side project will grow to such scales and standards too. Another alternative would be to tap into the gig economy to pick projects in specific technologies or scenarios that you want to gain more exposure in.

94

5 Comments

There are two hard problems in distributed systems: 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 1. Message ordering 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery 2. Exactly-once message delivery

1

1 Comment

Should we do problem discovery every time from Zero to One? 𝐒𝐡𝐨𝐫𝐭 𝐚𝐧𝐬𝐰𝐞𝐫: It depends. 👀 𝐋𝐨𝐧𝐠 𝐚𝐧𝐬𝐰𝐞𝐫: 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝐀: User Needs are already addressed by an existing player in a market. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: Flipkart entering the groceries delivery market where BigBasket is operating with a 1-day delivery timeline. Here relevant focus area can be more on differentiated offering of Flipkart compared to BigBasket to solve the same problem (may be a shorter delivery timeline of 2 hours). 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝐁: User Needs are addressed by a lateral thinking solution (completely new) in an existing market. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: Blinkit wants to enter the groceries delivery market with a 10-minute delivery timeline. Here more emphasis is needed on discovery of user needs which can be groceries deliverable within 10 minutes. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝐂: User Needs and Market of Operation are totally new from existing state. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: Creating a tourist service for people to visit Mars. Here we need to focus on every aspect of problem discovery: user needs, market research, context of problem, etc., Thank you Rethink Systems Shravan Tickoo for introducing this in the sessions! Cohort mentors: Attharv Sardesai | Unnati Nakra | Suraj Sharma | Mayank Madaan | Raghav Mehta | Arjun Hariharan | bhishm juneja Our group: Abhishek Singh Rathore | Aastha Thakur | Ashutosh Zode | Nadisha Garg | Vidyakrishna Jois G | Anurag Kumar | Avneet Sidana | Eshita Rastogi | Mansukh Kaur

39

7 Comments

Optimization in business adds capacity. Optimized use of resources results in better output with same resources. GenAI is giving chance of optimization. So why wait, embrace the opportunity and perform better!!!

2

2 Comments

My startup validation playbook 1) Ask chatgpt to recommend 20 search queries for a topic 2) Test them all for high-traffic in KW Planner 3) Poor Google search results? You may win SEO here. 4) Launch a directory and a blog * details 👉 youtu.be/ym6l_liTwhI

18

3 Comments