Ashishkumar Pandey

Hi folks, more about pointers in C which are undeniably powerful, but they can also be tricky for even seasoned developers. 🤯 Avoid common pitfalls and write safer, more robust code with these tips: 1️⃣ Understand Scope & Lifetime: 🤔    - A pointer's value is only valid as long as the memory it points to exists. Keep track of object lifetimes to prevent dangling pointers (pointing to  freed memory!) leading to crashes. 2️⃣ Null Pointers Are Your Friends: ✅    - Always initialize pointers to `NULL` when not pointing to a specific location. Check for `NULL` before dereferencing to avoid segmentation faults.  "Null checks are your safety net!"  3️⃣ Beware of Dangling Pointers: 💀   - When memory is freed, the pointer becomes invalid. Reusing it can lead to unpredictable behavior. Double-check deallocation and pointer usage. 4️⃣ Pass by Reference with Care: ⚠️   - Be mindful when passing pointers as arguments. Modifying a passed pointer might unintentionally change original data. Use const qualifiers for  safety. 5️⃣ Deep Dive into Documentation: 📚   - C libraries often have complex pointer interactions. Consult documentation thoroughly to understand how memory management works for specific  functions and structures. What's your biggest pointers challenge? Share in the comments! Let's learn from each other's experiences. 👇 #CProgramming #SoftwareDevelopment #MemoryManagement #Pointers

60

4 Comments

51 hard learnt lessons from a career as a Software Engineer 1. Vim > Emac 2. Learn to say no 3. Be honest, early 4. Javascript is fun 5. Disagree and commit 6. People love estimates 7. TypeScript is awesome 8. Always ally with product 9. Keep It Simple Stupid (KISS) 10. Add context to Pull Requests 11. Always expect to pivot, always 12. You don’t need advanced Math 13. Present solutions, not problems 14. Become comfortable with failure 15. Good people make bad decisions 16. Be familiar with the art of DevOps 17. You won’t always work on fun stuff 18. Make technical tests match the job 19. Stop giving unstructured interviews 20. Don’t worry about your 10 year plan 21. Never compromise your mental health 22. Lots of lines of code != Good Engineer 23. Nearly everyone works on legacy code 24. Never let a mentor touch your keyboard 25. Interview for logical thinking and attitude 26. Fundamentals > Language and Framework 27. Don’t be fooled by free pizza and ping-ping 28. This too shall pass...it’s hard now, it will pass 29. Get involved with other areas of the business 30. A technical leaders role is to guide not decide 31. The zone is real, you will get trapped for hours 32. Do not measure success by number of commits 33. Enjoy the learning curve of being a junior engineer 34. Celebrate world programmer day, why the heck not 35. Fast-paced environment = Expect to be overworked 36. Do not give multiple choice timed tests in interviews 37. You do not need a degree to be a Software Engineer 38. Let go of the ego. Trust people with the hard tickets. 39. Cheating is encouraged (Stack Overflow, Chat GPT..) 40. If you need to talk, reach out to someone, me, anyone 41. You are more, much more, than the sum of your career 42. Move towards brilliance and away from brilliant assholes 43. Be obsessed with the data, success metrics everywhere 44. If it can be done via Slack or Email, don’t book a meeting 45. If you want your team to be vulnerable, be vulnerable first 46. Create sacred work/life boundaries early and stick to them 47. If it’s not written down, it’s not worth the paper its written on 48. Avoid fillers like ‘but’, ‘however’, try to listen without responding 49. People first work cultures will not look to trick you in interviews 50. If you are the smartest person in the room, get out of that room 51. If your start-up CEO is not obsessed with fund-raising be worried Always remember the most important rule above: vim > emac.

296

61 Comments

51 hard learnt lessons from a career as a Software Engineer 1. Vim > Emac 2. Learn to say no 3. Be honest, early 4. Javascript is fun 5. Disagree and commit 6. People love estimates 7. TypeScript is awesome 8. Always ally with product 9. Keep It Simple Stupid (KISS) 10. Add context to Pull Requests 11. Always expect to pivot, always 12. You don’t need advanced Math 13. Present solutions, not problems 14. Become comfortable with failure 15. Good people make bad decisions 16. Be familiar with the art of DevOps 17. You won’t always work on fun stuff 18. Make technical tests match the job 19. Stop giving unstructured interviews 20. Don’t worry about your 10 year plan 21. Never compromise your mental health 22. Lots of lines of code != Good Engineer 23. Nearly everyone works on legacy code 24. Never let a mentor touch your keyboard 25. Interview for logical thinking and attitude 26. Fundamentals > Language and Framework 27. Don’t be fooled by free pizza and ping-ping 28. This too shall pass...it’s hard now, it will pass 29. Get involved with other areas of the business 30. A technical leaders role is to guide not decide 31. The zone is real, you will get trapped for hours 32. Do not measure success by number of commits 33. Enjoy the learning curve of being a junior engineer 34. Celebrate world programmer day, why the heck not 35. Fast-paced environment = Expect to be overworked 36. Do not give multiple choice timed tests in interviews 37. You do not need a degree to be a Software Engineer 38. Let go of the ego. Trust people with the hard tickets. 39. Cheating is encouraged (Stack Overflow, Chat GPT..) 40. If you need to talk, reach out to someone, me, anyone 41. You are more, much more, than the sum of your career 42. Move towards brilliance and away from brilliant assholes 43. Be obsessed with the data, success metrics everywhere 44. If it can be done via Slack or Email, don’t book a meeting 45. If you want your team to be vulnerable, be vulnerable first 46. Create sacred work/life boundaries early and stick to them 47. If it’s not written down, it’s not worth the paper its written on 48. Avoid fillers like ‘but’, ‘however’, try to listen without responding 49. People first work cultures will not look to trick you in interviews 50. If you are the smartest person in the room, get out of that room 51. If your start-up CEO is not obsessed with fund-raising be worried

55

9 Comments

When you are working on k8s NodeSelector and NodeAffinity You might wonder, If I can perform exact label matching using nodeSelector, why would I need nodeAffinity? This question came up in my k8s CKA community. While nodeSelector and nodeAffinity overlap in functionality for simple exact matches, nodeAffinity has more flexibility. For example, if you want to ensure the pod is scheduled on nodes with the zone labels us-east-1a or us-east-1b you cannot use nodeSelector. Technically, you can specify multiple labels with the same key but different values, and the pod gets created without any errors. For example, nodeSelector: topology.kubernetes/zone: us-east-1a topology.kubernetes/zone: us-east-1b topology.kubernetes/zone: us-east-1c But the first two will be ovveridden by the API server and only the last key-value pair (us-east-1c) will be used for scheduling. The last specified value for that key takes precedence. For multiple matches, you need to use nodeAffinity with the 𝗼𝗽𝗲𝗿𝗮𝘁𝗼𝗿: 𝗜𝗻 to allow matching multiple zones. Do you have any tips or insights to share? Drop them in the comments! ---- 𝗡𝗼𝘁𝗲:If you are looking for organized learning, in my CKA course, I explain concepts like these with illustrations to make them easy to understand. 𝗖𝗼𝘂𝗿𝘀𝗲: https://lnkd.in/grJYMpBA #kubernetes

191

12 Comments

JCenter is shutting down on this 15th August. Here’s what you need to do before your app breaks. JCenter, a repository hosting service by JFrog, is finally shutting down on 15 August, 2024. → After the shutdown, all request to JCenter will be redirected to Maven Central. ✅ If you’re using any library dependency that’s served from JCenter and not available on Maven Central, here are the steps to migrate. 1. First, comment out jcenter() as repository in your build files. 2. Try to run the project, if it works, all good. If not, follow next step. 3. If you’re using the library in Android app, you’ll need .aar file of that library. Grab it either from local Gradle cache or from online repo. 4. Add this .aar file in your project directory (such as in /libs directory) 5. Use this local file in your module level build files. PS: There are other ways as well. If you need any help, DM me and I’ll help you migrate. #android #kotlin #java Let’s connect because energy is contagious Rajesh Hadiya

371

27 Comments

*Bracing myself for the response I might get for asking this* Software Engineers: Would you ever consider working on an EQUITY ONLY basis (ie no salary, just owning a portion of the business, the value of which would increase as it progresses and scales)? Assuming: - The product is really interesting and so is the work - The product is in the "tech for good" space and would be a really positive contribution to parts of society - Seed funding is confirmed to be coming with several backers keen & they will able to offer a salary in the near future - The product is super early stage, you would be writing the software from the ground up, but the concept, design and business model once funding is received are all solid I know that there will be many who would never consider this under any circumstances and I totally get why, but just curious to hear if any of you would if it was for a product you believed in enough? And would you look at it on a full-time basis or a part-time basis? It's something I got asked about and so I thought I would throw it out to Linkedin to see what you all think rather than assuming that I know the answer on your behalf. #startup #founder #softwareengineer

39

309 Comments

FOUND - A 3.5 inch floppy disk connected to an unknown organization named the Stargate Research Society. A PO Box is provided. While the disk capacity is 1.44 MB, all that was contained within were a few pages from a pamphlet and a single executable file, ElsewhereSearcher.exe. The booklet titles itself a meditative inquiry on the Mystery & Nature of human consciousness, as revealed by Blood Incantation. If you subscribe to ancient mysteries of the universe, it’s quite the page turner. When I inspected the properties of the software file, it only included the following description: “An app developed by the SRS for studying the effects of sound frequency structures upon human organisms.” After much deliberation, I decided to open the app only to find it would only run on ancient technology: Windows 95. I dusted off an old desktop and hesitantly double-clicked the app open. The app seems to be some sort of night sky viewer and after providing access to my orientation and camera, I was, indeed, able to explore the stars. At the time, the app seemed no more than a constellation viewer, albeit a very old one. However, I was persistent and checked back every few hours to see if anything was revealed by the rotation of the celestial sphere based on my location (New Orleans.) At around 6am local time, sunrise, I pointed the app near Orion’s belt (over 800 light years away) and heard, yes heard, what I can only describe as an otherworldly signal. Even more disturbing, if the app is to be believed, that signal seems to be drawing nearer to us, though I have yet to work out the calculations of when it might arrive. I’ve been watching the app non-stop for another signal and have only taken a short break to write this post. In an attempt to bring more of you to the cause, I have ported the app to https://lnkd.in/g5TU2fkS. Please let me know that I’m not crazy by listening for the same signal and perhaps you’ll hear other things as well. I’ve included a note of where the sound was originating from me. What will we find by looking through this doorway?

21

10 Comments

🕒 Looking for a reliable, open-source time tracker? Meet Kimai 💡! It's a powerful, free tool that handles freelance and business projects with ease. 🚀 Kimai's impressive features include: ✅ JSON API, invoicing, data exports ✅ Multi-timer & punch-in punch-out mode ✅ Tagging, multi-user, multi-timezones, multi-language (30+ translations!) ✅ Authentication via SAML/LDAP/Database, two-factor authentication (2FA) ✅ Customizable role and team permissions ✅ Responsive design, user/customer/project specific rates ✅ Advanced search & filtering, money and time budgets ✅ Advanced reporting, plugin support ...and so much more! 🔧 System requirements: PHP 8.1.3, MariaDB/MySQL, webserver & subdomain, PHP extensions 🚀 Either set up natively with Git and Composer, or use Docker containers. Host it on your local machine, shared hosting, Synology, or hosted environments. If you'd rather not host yourself, check out the Cloud version! 🔄 Updating and maintaining Kimai is a breeze, with regular release versions and easy-to-follow upgrade steps 📚. 👉🏼 [Documentation](https://lnkd.in/g8xuNwVg), [blog](https://lnkd.in/gSyf9hpk), and [plugins](https://lnkd.in/g3_caFCF) are all available. #OpenSource #TimeTracking #Kimai #Productivity #TechCommunity

6

🔧 Ever found yourself in a situation where tracking time spent on projects or tasks became a challenge? Meet Kimai, an open-source, professional-grade timetracker that can help you manage your time more efficiently! 🌟 Key Features: ✅ JSON API ✅ Invoicing ✅ Data exports ✅ Multi-timer & punch-in/punch-out mode ✅ Tagging ✅ Multi-user, multi-timezone, multi-language (30+ translations!) ✅ SAML/LDAP/Database authentication ✅ Two-factor authentication (2FA) ✅ Customizable role & team permissions ✅ Responsive design ✅ User/customer/project specific rates ✅ Advanced search & filtering ✅ Money & time budgets ✅ Advanced reporting ✅ Plugin support ...and so much more! 📚 I've personally found Kimai to be an invaluable tool in organizing my projects and tracking time. With its robust feature set and ease of use, it has made time management a breeze! 💬 I'd love to hear your thoughts and experiences with time-tracking tools. Let's start a conversation and learn from each other. Don't forget to include the hashtags #Kimai #TimeTracking when sharing your thoughts!

6

Okay, strap in; in the space of the last 4 days, it's the second time we are going viral. Email from the CEO at ProductHunt Rajiv Ayyangar, thinking its fake 😮: Can you reshare and help us break their servers? 🙏☺️ https://lnkd.in/d_xP3rzP Link to our demo: https://lnkd.in/d--8Yzkd Come see what we do at wordware.ai

118

11 Comments

Building RevConsole: We did not scrap a single module from our code base because: When we embarked on building RevConsole, my ex-boss gave me one of the greatest, game-changing pieces of advice from one engineer to another: “If you build in isolation, you might need a second start.” As engineers, it's tempting to jump straight into coding, creating repos, and scaffolding the essentials. But thanks to this invaluable advice, we didn’t fall into that trap. Instead, we embraced a process of validation—starting with idea threads, engaging in countless conversations, and brainstorming with people across the industry. To this day, we haven’t scrapped a single module from our codebase. Our greatest fear was that we weren’t salespeople. While we were confident in our ability to build the product, we had a healthy skepticism about the domain. That’s where customer conversations and feedback from industry leaders became our guiding light. Their insights allowed us to design features with confidence—things like multi-year discounts, discount approvals, seamless integration with other systems, and reviewing terms. Looking back, this process of collaboration and constant feedback was key to our journey. It taught us that building in the open, with real-world input, is the best way to avoid needing a second start. #saas #quote #cpq #salesforce #hubspot #signing #b2b #q2c

125

10 Comments

Sniff x Goooooooogle 🌿 🔥 Everytime i used to see Google Cloud Usage graph, i get mixed feeling. Happy it's growing 🌿 , sad that it's gonna cost alot this month 🤣 🥲 At peak we exhausted $15k in Less than 24 Hours 😵‍💫 Bill Graph 📈 Heart Rate 📈 Well now Sniff is now Google Ecosystem Partner! 🥳 What that means? - Enough credit to experiment for years 😮‍💨 - More refined results 🙌 - More resource to fine tune 🦻 - Drastic drop in service fee 🦾 - More Sniff Membership Giveaway (Maybe) - More room to play around - Some other perks 1 down, 29 applications result pending! visit dosniff.com to know more! #sniff #GenAI #AI #hiring #client #freelancer #SniffAI

78

5 Comments

5 questions in 4 minutes: 1. What does a senior software engineer do? 2. How do you motivate your team? 3. Individual Contributor or Engineering Manager? 4. How do you stand out in Big Tech? 5. Is ChatGPT affecting the job market? Hemant Pandey, senior software engineer at Meta, shares his thoughts. Let me know your thoughts in the comments. Cheers!

1,107

12 Comments

Here is a startup idea: Build an LLM which could take randomly malformed json objects generated by these models.. and convert them to a valid json.. Damn right I'd invest in you!

41

19 Comments

That moment when you include different, but hidden, markup for mobile / desktop with different LCP candidates on each. Your desktop LCP candidate is not present on SSR content, only mobile candidate is (css hidden) which makes the Desktop not part of the critical rendering path and gets buried under loads of React hydration events, GTM, data fetching for component and site wide stuff. You get up to 11s LCP on desktop (depending on connectivity and processing power). There's a bug on this page which we are fixing. It's one of those things that are not obvious at first glance. The image is found around 9s and fully loaded and processed around 11.5s.

11

Building a platform that has LinkedIn integration… If Microsoft’s docs were written on paper I would burn them. For some reason getting the integrations and permissions correct has been one of the biggest headaches in this project. Redis? No problem. Stripe for subscriptions and auth flow using 0Auth? Easy. Setting up S3 buckets for photo storage and adding packages to change all photos being saved to webp? Took like an hour. Posting to LinkedIn using their API? Well first you gotta weed through all the irrelevant and old docs they keep around to confuse you. Make sure your app has the correct permissions from the beginning - if you miss something there it’s a whole thing to change it. You’ll need different ones than you think… and if you’re lucky enough to find the hidden errors logged somewhere - they won’t help much. Just not a fun integration for me. #linkedin #softwaredeveloper #aiplatforms

3

2 Comments

The Curious Case of the Spring Boot Scheduler We've all been there. You develop a simple scheduled task in Spring Boot, blissfully unaware of the mayhem to come. The annotation is clean and straightforward - @Scheduled with a cron to run daily. What could go wrong? Well, when deploying to Kubernetes, we encountered an unexpected surprise. Our application ran on multiple pods, and each pod happily triggered the task simultaneously every day. Suddenly we had duplicated work across all pods! This was a head-scratcher. Our naive scheduler logic assumed a single application instance. But in the cloud, we must plan for scale from the start. After some trial and error, we refactored the scheduler into a separate utility app. This singleton instance called our API on a schedule to trigger the work. No more duplicate tasks! It was an "a-ha" moment on distributed systems. We cannot think in local boxes as we expand to the cloud. Assumptions get turned upside down. Have you run into similar scheduler dilemmas? I'd love to hear any tricks you've learned when scaling scheduled jobs. The shift to cloud has so many subtle gotchas, but together we can pool our knowledge. Happy Scheduling! #SpringBootScheduler #KubernetesDeployment #DistributedSystems #CloudScaling #ScheduledJobs

28

2 Comments

So my https://meshtastic.org node is up! But I don't have anyone in entire Bengaluru to send a message to! Pushing some of the friends to setup theirs! If you are wondering what Meshtastic is, it's an off the grid long range (LoRa) communication system capable of very long ranges (current record is 254 km!). Though what range you get will depend on your setup. Multiple nodes in an area creates a mesh though which messages can hop over. There are some low power boards which can be coupled with a solar panel to power it forever!

58

2 Comments

A developer’s most precious time is uninterrupted hours of deep work. So, engineering managers should put thought into when they schedule their standups. Ask your developers: when are your blocks of uninterrupted coding time? When do you want them to be? From my experience you want to give developers at least one chunk of 2+ hours before lunch. This seems obvious but if you have a standup at 9:30, you’re not gonna get one. You’ll disturb people right as they enter flow state. Then, they will be watching the clock as their stomach starts telling them it’s time for lunch. What has worked for me is: - with more junior devs, 8 or 8:30 at the latest. It’s most important to make sure they are not blocked or working on the exact same thing as yesterday. - with more experienced devs, early afternoon. Give them their whole morning meeting-less. 4+ hours of deep work in the morning. Another session after the afternoon standup.

24