img

I mean how ? Why ?

1) You develop a feature, covers every case where it can go wrong. Dry run 2-3 times. Then comes the day of UAT meeting. You are displaying feature in front of all stake holders and the feature breaks. 2) You are trying to solve a bug. You tried every way there is which you can think off. You are scratching your head, figuring out why ? Now you finally decide you need big guns, ask colleagues/seniors for help and you explain them the issue and you also explain them the solution which you were trying. Now magically issue is solved or you atleast understand what was wrong and why it was not working. What phenomena is this ? Does this only exist to make you look stupid ? How ? Why ? There got to be some explanation for this.

img

FunnyBones

Plivo

a year ago

img

James_bond

Stealth

a year ago

img

coderx

Student

a year ago

Sign in to a Grapevine account for the full experience.

Discover More

Curated from across

img

Confessions on

by samosa

Stealth

Having some fun with the interviewers

So basically I don't hesitate in challenging the interviewer if I feel like they don't know how to interview a senior candidate so during many interviews, this is how I have caught them off guard: 1. The interviewer was asking me technical questions and expecting to explain properly throughout. So at the end i asked him about the tech stack they use, he said Azure. I asked him why they use Azure and not AWS, to which he said "it's cheaper", i didn't let it go, i asked him for a proper technical explanation, his red face was worth seeing. 2. The interview asked me a hard DSA question, and I wasn't able to solve it properly, he didn't even give me enough hints, just expected me to solve it. So halfway I asked him, would you like to solve a DSA if I ask you right now, he said no because it's not his interview. To which I asked, are you afraid that you won't be able to solve? If you are going to reject me for not solving this question, would you resign if you aren't able to solve the question. He ended the call. 3. One interviewer was asking me absurd technical detailed questions. I asked him why are you asking such questions, he said he needs to know my thought process because he will work with me. I started asking him similar questions, he said he won't answer because it's not his interview. I said I also need to know your thought process because we'll work together, so you should also answer these questions, he had no reply. 4. The interviewer asked me about a challenging project that I had done recently. I don't like this question at all. So I said there wasn't any challenging project because I'm good at what I do so it's always easy for me. He moved on to the next question. 5. HR asked me why I resigned without an offer? I asked if it's mandatory? No reply.

img

Software Engineers on

by BearBear

Stealth

For the engineers, by the engineers.

I had this idea in mind, that many of us either want to learn something new or create our own product but we either don't have the time or consistency to learn or no time to build huge products alone. So I'm proposing this, why don't we software Engineers of all experience levels come together and build communities where if someone wants to learn SpringBoot Backend or React Frontend or whatever the stack is, they come along and start working on a product and learn along the way. To help them, experienced software Engineers come along and if they want they work on it and help the people and guide them with the best practices. In the case of experienced folks, let's say they decide on several products and we divide the teams based on the expertise and start working on them. What do we get in return? Better networking, experience and maybe a few good startups which are built by us, and they succeed at a product level. Who is this for? Anyone who wants to mentor, learn or want to build a product but they don't have people to do that. Who all are invited? Senior Engineers, Tech Leads, Engineering Managers, Product Managers, Director of Engineering, CTOs and others. Sr folks to help the community. Let's say we decide on 5 products, make a roadmap on how we want to work and within a year we release these products in the market and maybe maybe we get to work on our own company rather than from others. if not, then also good karma and networking will be done which will be helpful for this tough time ahead of us. Today's Junior engineers will be Senior engineers of tomorrow. Today's Senior engineers will be a great part of management of tomorrow. Let's build real software and change the way we learn things and do great engineering and learn a lot and earn from the products as well. Thanks 🙏🏻