Most people like to share. They feel validated and are genuinely happy to tell you why they did "that good thing" or how they got the result they got.
If they dont want to answer your questions, you also learned something: dont be that guy! hahaha
13 karma · joined October 5, 2012
Most people like to share. They feel validated and are genuinely happy to tell you why they did "that good thing" or how they got the result they got.
If they dont want to answer your questions, you also learned something: dont be that guy! hahaha
They all miss the point. Having "ownership" is caring like its yours. Making decisions that make sense, and you would do in yours. Your answer is perfect!
Ofcourse you should not have the "minimal effort police" in mind, but you also should not work your balls off for nothing.
I always think im doing a hell of a job if my team can just focus, get shit done and leave happy on the end of the day.
The best managers seems invisible and looks like they aren't doing shit.
Cheers bro, just keep improving and its gonna be ok.
You may feel like not adding much value because you may be measuring yourself by the wrong metric. If you are / was a software developer, its kinda easy to see your contribution, you just pull the git log. When you are leading, its way harder to notice. Thats the jump to the soft skills.
I like to think soft skills are called this way because they have a soft touch. You cant really define what they are, but you know when you are not having it, much like clean code.
It seems like you know where they can develop and get better. Managing them is helping them achieve it. Help them, guide them, nurture them. And mostly important, ask them where you can help.
Being the manager is not being the smarter, just the facilitator. You make thinks smooth. Managing is good when you cant see and it feels it does not exists, but, you know things will be worse if the managers are out.
Something like this: I want to make illegal to ride bikes. So i have to draft the law, maybe meet someone against and in favor, redo if needed, pass by review, submit it to the congress (or whatever), work on the "comments" made at the discussion, etc.
Each of these steps are kind of "taks" in the sense of the project, and so, trackable. All can be done through technology and can even have some kind of automatic test of acceptance. And it can be acessible to everyone.
Anyway, it is just an idea. Never thought about that very deeply, and even the example may be wrong in steps haha.
Anyway, you will have to read it all but it can narrow a little bit.
https://gist.github.com/pedrofornaza/6b71569972de0e2bfa3c775...
I did this sometime ago. Its probabbly not working 100% but may help you. :)
Its as script to run on background (cron or alike) and raise desktop notifications when articles with the keywords you put in the script.
I had several ideas for this but i just stopped developing for lack of time.
Let me know if it interests you.
Keep the good job :)
I usually choose the better framework FOR MY PROBLEM. If i need something lightweight, or reliability, performance, etc.
ZF and Symfony are too big for small projects, maybe Slim is to little to a medium/big project, etc.
I think you adopt a PHP framework for your problem, not for coding in general.
We can do a lot of things to kick ass. For kicking ass on the job, the first one for me is know what are you doing and why.
The second is participating. Know what is going on, what people is doing, make suggestions. Participate.
But, for kicking ass coding, anything can replace the experience. So, read, write, read, write.