> The TL;DR is that some (“best”) practices are contextual and understanding when to use them is ultimately what gives us the title of “engineers”.
So well put, just today I implemented a feature and kept asking myself if i should be extending the component (leaning more towards OOP) or just add an additional argument to said component. The latter would have stuck more with the current style but I also realized there's no obvious better way, extending made sense and I realized the importance of understanding the nuance and standing up for those design decisions is what I am here to do :)
fair and fine but all of that can be achieved whilst one is fairly compensated too. It's not a "give here and we'll give you this extra" type of situation, they offered nothing in return because they want it for free, period
I like this idea and hope it gains ground. A thing to think about is to work with ranges, in terms of showing a person how much other people earn. I can imagine the system exposing someone at the same level in a relatively small department that they shared such kind of info on your website (if user A simply says but user B earn so much) so any way to "obfuscate" the data would protect everyone.
Find out how many people are working for the startup and their backgrounds. This is super important to do either as research before or after, to find out if you are going to be working with truly A-players. Overlooking this aspect might be ok in the short run but as with many startups, people do get laid off at some point (or the idea fails to take off) so to get maximum benefit during your time, expose yourself to excellent colleagues who will grow your skillset.
Exactly the same thing I realized. Working out in the morning actually drained me of energy for the day and made me super sleepy instead. Running though, has the different effect and made me feel a whole lot more fresher and ready to tackle the day. So i guess it depends with each person what activity you do in the morning to get your body ready.
This clarifies my observation. As i was reading down the list of rules, I tried to think if some of the most enjoyable stories I can recall stuck to these guidelines strictly, doesn't appear to be the case. Maybe it's just my taste, but i then tried to recall what masterpieces this author has to his name but no big names came to mind. would be interesting to delve deep into his work then contrast his style with others.
I applied for an exchange program in the States, that's called Professional Fellows and spent a good 4 months learning US business practices and just being a bit exposed to a different way of doing things. I'm from Zimbabwe btw. Part of my stipend at the time, I saved it to buy a car which I still own to this day. 4+ years with, i'm 29 now. At 25, I was staying on my own and trying my hand at a startup after quitting a job i had been offered with a good salary.
I'd tell my 25 year old self to be more patient and play a more long game, backed with knowing that even good investments justify themselves after a few years down the line.
So well put, just today I implemented a feature and kept asking myself if i should be extending the component (leaning more towards OOP) or just add an additional argument to said component. The latter would have stuck more with the current style but I also realized there's no obvious better way, extending made sense and I realized the importance of understanding the nuance and standing up for those design decisions is what I am here to do :)
thank for putting that in less words