Why do we make this the gate keeper to our industry when we know (except for the very specific roles) we will rarely need leet code type problems. When we do we just google them.
So silly to me.
215 karma · joined March 29, 2011
Why do we make this the gate keeper to our industry when we know (except for the very specific roles) we will rarely need leet code type problems. When we do we just google them.
So silly to me.
You have to approach these things as what do you want out of it.
Do you want to prove someone wrong, just to prove them wrong? Do you want to steer them in a better direction? Is this something you will end up owning, so want to avoid the pain? etc..
There are numerous scenarios. For me, we are one company, large or small if I am not trying to steer it towards a better path, why am I here? If thats the case, I should just take my paycheck and shut up. It's good you care, it means you value your company and/or people.
That said, let me share my exp.
When I was 18 I managed a restaurant my dad had bought. I was a kid telling people who had worked there for years what to do. One day I disagreed with a head waitress that had been there for 10s of years. I did it in front of customers. She got defensive, stormed out, and I served tables the rest of the day.
The takeaway here is, theres a time and place. I feel my role as an employee is to work slightly behind the scenes. I advise my management why I think an approach is better or worse, highlighting we CAN go the way you suggest, but how do you propose we handle X. Usually you can lead them to the way you believe the correct one.
Another point to keep in mind, you dont know everything. I think the most valuable thing I have learned is to understand the motivating factor of why something is going in this direction.
Is there a timeline? Funding constraints? Promises made? Is the person an idiot?
Again, there are so many different scenarios.
There is no black and white answer to your question. I will say though, if you make a statement, be confident you can back it up. Be sure you have thought it through, because there is nothing worse that saying someone is wrong, rallying people to your side, and being unable to deliver.
Enhance, clean, iterate. Inspire the other devs to write cleaner code by leading by example.
If you would take the first version of most production code put it in a book and write the problem it solves, I'm sure you wouldn't think it sucks. My exp developer 15years, finance industry 7.
But then again their api is so simple its almost not needed
I assume this sample is based on start ups only?