Rahul Dev Choudhari’s Post

"Am I too old to be considered for this C++ position?"   Age, let’s talk about it. It’s a sensitive topic but as a few greys are forming in my once all black beard it seems like an apt topic.    My honest thoughts…. Age is only an issue if you have allowed your skills to age.   If you have been working on legacy code for 10+ years and list C++98 as your main skill; you might want to consider a CV overhaul, some programming courses and join organisations such as ACCU if you are wanting a new job.   I’ve spoken to many developers who could retire if they wanted to and work for some of the most dynamic companies. The trick? They love what they do and have remained up-to-date with latest standards.   I don’t want to minimise age discrimination, but if you are like the developer I spoke to recently using age as a barrier for a new position, please don’t. Age should not be a barrier, it's more the skills you have so invest in yourself.   #diversityisking #recruitment #diversity #CplusPlus

Hello! As I continue to contribute to nami, I'm also on the lookout for an iOS Engineer to join the team and take the reins of what's been a dynamic role for me. In the last two and a half years, it's been more than just work—it's been an ongoing adventure of growth and learning. I've had the privilege of shaping our iOS app, allowing users to control cutting-edge consumer devices with WiFi sensing. This isn't just about coding; it's about pushing the boundaries of safety, security, and home automation. Now, while I'm still actively engaged in my role at nami, I'm keen to find the right individual to seamlessly step into this exciting journey. Whether you bring experience beyond the iOS ecosystem—maybe in Kotlin, Java, Flutter/Dart, or another language—is a great bonus, it's not a prerequisite. Equally important is your dedication to maintaining a stellar codebase. Familiarity with firmware development (C, C++, Rust) is a plus, but what matters most is your commitment to delivering top-notch code. Here's a snapshot of our iOS app tech stack: - SwiftUI and Combine with a TCA-like VM-centric architecture. - GRDB for the database, sprinkled with UserDefaults and Keychain. We're also gearing up to use Thread credentials store. - BLE, ProtoBuf, CoAP, DNS-SD, and cloud connections, with our proprietary pairing protocol adding a special touch. - The app is a composition of various SPM packages, including our in-house Pairing SDK. Feel free to ask questions, even if you're not sure about the role. We understand that the coding tasks linked below may seem challenging, but they're grounded in the reality of what we work with. If you're intrigued and have questions, reach out. We can have a chat, explore your experiences, and if things align, we might just skip the coding task. Each individual is unique, after all. Feel free to share your CV through direct chat or email ([email protected]). The link to the coding task is pasted below this message. I'm excited to find the right fit for this unique role!

Junior programmers have found themselves in a particularly difficult situation in the last year or two in IT, which used to be a profession of success and shortages, but is now facing mass layoffs. In addition to them, even female IT experts are in a more disadvantaged position. Our compilation is about their future prospects, which can be read at the link in the first comment.... ------------------------------------ #digitrendi #womenintech #juniorprogrammers #recession

Recent Android Dev Interview Experience: I recently underwent an Android development interview process that consisted of multiple rounds. The first interview was around 1.5 hrs long, starting with the usual introduction. Subsequently, the interviewer asked several key questions, some of them are:- - Why you chose Android Development - Why you left your last Company - Why Kotlin is better than Java - Explain Object Oriented Programming(OOPS) - What are CRUD Operations - What is SQL - Explain Room Database - Explain Android Lifecycle - Explain Fragments and intents After this, he asked a simple DSA question based on array and sorting He gave me 15 mins to solve it, I solved it easily. The interview ended after this, I got qualified for the next Task round. They gave me 6 hrs to complete it. I managed to complete and submit the task within the given timeframe. Next and the final round was again an online interview. Here are the questions I was asked: - What is Asynchronous programming - Why MVVM is better than other architecture patterns - What is inline function, extension function - What is the minimum Response time of Retrofit - How will you duplicate entire existing data present in Room Db - lateinit vs lazy and many more I managed some of the questions but stumbled on a few. Unfortunately, I got rejected afterward. But, on the bright side, each interviewer shared feedback on where I could improve. It's been a learning experience that will help me in the future :) Update: Remember this, if you're going for an interview: Prepare like you’ve never won. Perform like you’ve never lost. Thought by: Jim Kiwi #androiddev #freshers #androiddevelopment #interviewexperience

What are interviewer's expectation from fresh, mid-level and senior Android devs? This can be divided into 3 parts, WHAT, HOW and WHY. 🎯 For Freshers The focus is on WHAT part, that is whether candidate understand basic working of system or not. ✅ Examples: → What is Activity and it's lifecycle → What is RecyclerView and it's benefits → What is Room database 🎯 For Mid-level (2-4 YoE) The focus is on HOW part, that is whether candidate can understand and get things done or not. ✅ Examples: → How to manage multiple API requests → How to pre-populate room database → How to use Hilt with navigation 🎯 For Senior (5+ YoE) The focus is on WHY part, that is whether candidate knows in-depth of how system works internally or not. ✅ Examples: → Why StateFlow and LiveData (or vice-versa)? → Why coroutines are better than thread? → Why ViewModel survives configuration changes? Enjoyed? Like/Share the post to spread the words. ❤️ PS: This is an opinionated post. Feel free to add anything in comments. ───── If you want to Master Android development, checkout my upcoming live course with 10% discount. Link is in comment. #android #kotlin #java #androiddeveloper #androiddevelopment Let's connect because energy is contagious Rajesh Hadiya

I interviewed a candidate. He did not believe me when I said 𝐼 𝑤𝑖𝑙𝑙 ℎ𝑒𝑙𝑝 𝑦𝑜𝑢, 𝑛𝑜 𝑝𝑒𝑛𝑎𝑙𝑡𝑖𝑒𝑠. He ran out of time before completing the pair programming task, so it was an automatic fail. 𝐖𝐡𝐲 𝐝𝐢𝐝 𝐈 𝐨𝐟𝐟𝐞𝐫 𝐡𝐞𝐥𝐩? Because no tech person works in isolation. We go ask out colleagues for help when we get stuck. This is the way we move forward in a fast pace - together. 𝐈𝐧 𝐭𝐡𝐚𝐭 𝐩𝐚𝐫𝐭𝐢𝐜𝐮𝐥𝐚𝐫 𝐜𝐚𝐬𝐞 ... the candidate, however, thought it a trick. Or maybe he wanted to soldier through, to prove something to himself. I am not sure. The results, unfortunately, is the same no matter the intrinsic motivation. So, I invite you to ask for help ... and to accept it when it is freely given. No need to Thank me, just pass this knowledge forward. #interview #hint #help #tech

One of the Most Asked React Interview Questions. Create Dependent Dropdown. #freshers, #reactDevs, #javascriptdevs. import { useState } from "react"; import "./styles.css"; const countries = [ { name: "India", value: "In", states: ["Telangana", "Andra"] }, { name: "Pakisthan", value: "PK", states: ["Lahore", "Karachi"] }, { name: "Bangladesh", value: "BD", states: ["Barishal", "Chattogram"] } ]; export default function App() { const [country, setCountry] = useState(0); return ( <div className="App"> <h1>Hello CodeSandbox</h1> <select value={country} onChange={(e) => { setCountry(e.target.value); }} > {countries.map((item, index) => { return ( <option value={index} key={index}> {item.name} </option> ); })} </select> <select value={country}> {countries[country]?.states.map((item, index) => { return ( <option value={index} key={index}> {item} </option> ); })} </select> </div> ); }