Hey gym freaks,
I would like to start going to gym. Basically, nen iyte intak mundu eppud gym ki poledhu.. but ippud baaga potta ochestundi. So could you please let me know which gym is best and its cost.
TIA
Hi Everyone,
I am going to visit showrooms from various dealers to book AX5 MT P variant in Hyderabad.
If anyone has purchased or booked it after the recent price hikes. Please help with your quotations. So, It will be helpfull to get an idea of how much I can ask for discounts.
Hey,
I am from hyderabad and planning to go for a trek and found about kalsubai.
I would like to hear what all to be taken care of
is it worth to do on August 8th?
Is it okay to do solo trekking?
Any permission required for trekking?
Hi everyone,
I'm planning to buy a Mahindra XUV 3XO AX5 MT by year end.
I've often heard that dealers offer significant discounts towards the year-end to clear inventory. I wanted to understand how this actually works from people who have recently purchased a car.
I have a few questions:
Are the year-end discounts really substantial, or is it mostly marketing?
Since the waiting period for the 3XO AX5 is around 30–45 days, when should I ideally book the car if I want to take delivery in December and still be eligible for year-end offers?
If I book in October/November and the dealer gives me a quotation, can the quotation be revised at the time of delivery if Mahindra announces better offers in December?
What is the best way to negotiate?
4a. Should I negotiate during booking?
4b.Or should I negotiate again just before taking delivery?
I'd really appreciate hearing from people who bought a Mahindra vehicle during the year-end period and how much discount or additional benefits they managed to get.
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
\## Background
\- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
\- Around 2 years of experience in product companies.
\## Current work
\- I'm working on cloud-managed networking products(switch , access points) at an MNC.
\## My work involves:
\- Linux-based networking products.
\- C based agents running on networking devices.
\- Device discovery and monitoring.
\- Production debugging.
\- Configuration management between devices and the cloud.
\- Some changes in an existing C codebase.
\- Go-based packet capture using BPF libraries.
\- Understanding Linux-based networking systems.
\## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
\## What I've realized
I think what actually interests me is lower-level work like:
\- Firmware
\- Device drivers
\- Embedded systems
\- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
\## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
\## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
\## Background
\- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
\- Around 2 years of experience in product companies.
\## Current work
\- I'm working on cloud-managed networking products(switch , access points) at an MNC.
\## My work involves:
\- Linux-based networking products.
\- C based agents running on networking devices.
\- Device discovery and monitoring.
\- Production debugging.
\- Configuration management between devices and the cloud.
\- Some changes in an existing C codebase.
\- Go-based packet capture using BPF libraries.
\- Understanding Linux-based networking systems.
\## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
\## What I've realized
I think what actually interests me is lower-level work like:
\- Firmware
\- Device drivers
\- Embedded systems
\- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
\## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
\## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
\## Background
\- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
\- Around 2 years of experience in product companies.
## Current work
\- I'm working on cloud-managed networking products(switch , access points) at an MNC.
## My work involves:
\- Linux-based networking products.
\- C based agents running on networking devices.
\- Device discovery and monitoring.
\- Production debugging.
\- Configuration management between devices and the cloud.
\- Some changes in an existing C codebase.
\- Go-based packet capture using BPF libraries.
\- Understanding Linux-based networking systems.
## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
## What I've realized
I think what actually interests me is lower-level work like:
\- Firmware
\- Device drivers
\- Embedded systems
\- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
\## Background
\- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
\- Around 2 years of experience in product companies.
\## Current work
\- I'm working on cloud-managed networking products(switch , access points) at an MNC.
\## My work involves:
\- Linux-based networking products.
\- C based agents running on networking devices.
\- Device discovery and monitoring.
\- Production debugging.
\- Configuration management between devices and the cloud.
\- Some changes in an existing C codebase.
\- Go-based packet capture using BPF libraries.
\- Understanding Linux-based networking systems.
\## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
\## What I've realized
I think what actually interests me is lower-level work like:
\- Firmware
\- Device drivers
\- Embedded systems
\- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
\## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
\## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
\## Background
\- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
\- Around 2 years of experience in product companies.
\## Current work
\- I'm working on cloud-managed networking products(switch , access points) at an MNC.
\## My work involves:
\- Linux-based networking products.
\- C based agents running on networking devices.
\- Device discovery and monitoring.
\- Production debugging.
\- Configuration management between devices and the cloud.
\- Some changes in an existing C codebase.
\- Go-based packet capture using BPF libraries.
\- Understanding Linux-based networking systems.
\## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
\## What I've realized
I think what actually interests me is lower-level work like:
\- Firmware
\- Device drivers
\- Embedded systems
\- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
\## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
\## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
Hi everyone,
I'm looking for advice from engineers who have made a similar transition.
## Background
- B.Tech in Electrical and Electronics Engineering (EEE) from NIT Calicut.
- Around 2 years of experience in product companies.
## Current work
- I'm working on cloud-managed networking products(switch , access points) at an MNC.
## My work involves:
- Linux-based networking products.
- C based agents running on networking devices.
- Device discovery and monitoring.
- Production debugging.
- Configuration management between devices and the cloud.
- Some changes in an existing C codebase.
- Go-based packet capture using BPF libraries.
- Understanding Linux-based networking systems.
## However, I'm not working on:
Firmware
RTOS
Device drivers
BSP
Bootloaders
Kernel development
## What I've realized
I think what actually interests me is lower-level work like:
- Firmware
- Device drivers
- Embedded systems
- Hardware-software interaction
I enjoy understanding how hardware actually works more than writing cloud-facing applications.
## My dilemma
I'm unsure about the best path from my current position.
Should I:
Continue in networking/systems software and try to move toward firmware gradually?
Learn firmware (STM32, FreeRTOS, peripherals, etc.) while staying at current company and then apply directly to firmware roles?
Target companies like Qualcomm, NVIDIA, AMD, Cisco, Broadcom, etc., in systems software first and then try for an internal move later?
Consider an M.Tech if I want to move closer to firmware or embedded systems?
## Questions
I'd appreciate answers from people who have actually worked in firmware or embedded systems.
Is my current networking/Linux background considered relevant for firmware or embedded systems roles?
If you were in my position, what would your roadmap be?
What skills would you prioritize over the next 12–24 months?
Am I underestimating how difficult this transition is?
If you've made a similar transition, what was your path?
I'm looking for honest opinions rather than encouragement. If you think my plan has flaws, I'd appreciate direct feedback.
TIA
I am a 2024 passed out and I need to get my transfer certificate as well as study conduct certificates. What is the standard process for it?
Matter entante, I have 2 years of experience in IT industry and having a pay of more than 15lpa.
But naak asal interest ravatledh IT antene... I thought idhi naa team and company valla ankunna... so vere dantloki switch ayya oka 8 months iytundi ankunta.... kotha company lo kuda asal nachatledh....
So, on evaluating my istalu and kastalu.... semi core industry side vellali ani decide ayya... then the option is to prepare for the GATE EC (2027).
Hope everything goes fine and good.
Background: naa btech NITW (Electrical) lo complete chesa and appud naak antha telvakunde... bavi lo kappa laaga IT side ee priority icha initial days nunchi... but from late 3rd year naak electronics ante interest pergindi than software but placements lo IT company lo place ayya... and finally now decided to move into that field which i started liking itself.
NOTHING IS LATE THAN NEVER TRYING!!!
Bye Guys... see you again in next February!
Hey guys,
Ifanyone of you got shortlisted for iisc micro electronics and vlsi branch. Please let me know what is your score and respective marks along with the paper.
It will be useful for many to get an idea how many marks/score it requires in general.
Hey, I came to hyderabad for days and feeling bored and lonely. So, I am looking for any F who are okay with a casual date.
Let's connect for a good vibe.
I am moving to hyderabad for few days, so I want to have a individual workspace for a day or two. Are there anything similar to bhive which provides daily passes in hyderabad??