166 karma · joined May 4, 2011
For example, as a 5-year Clojure convert who wrote Java for 15 years before that, old-fashioned loops are less readable now, as they hide the essentials of what is really happening. For example, you might be mapping a collection from one type of value to another, or reducing it to some other form, etc. But both use loops. You have to scan all over the place in the loop construct to see what it's really doing. I'd much rather see the function that is happening than the procedure by which the function is accomplished.
That said, of course there's no moral obligation to contribute. However, as an original author of several open source projects, I take this as a helpful lesson around inviting others who don't have a moral obligation to feel welcome to contribute, and even find some way to reward them, even if I can only afford public praise at the time.
Also, are there guarantees that no two branches can be created at the exact same point in time?
Thanks for the excellent work! I can actually see some use cases for this in one of my side project. :-)
https://github.com/lantiga/clj-toml/blob/0.4.0-instaparse/sr...
What a lovely language! I may have to use it..
If I had data that Enpass was full of holes, I'd switch back instantly!
My advice to anyone in a similar situation: work on the classes of behavior that are actually problematic, namely blaming, defensiveness, contempt, and stonewalling. Then you can have a healthy argument about ideas.
If a team has problems listening to actual, clear evidence that what you did was correct, they are perhaps at fault here. Of course, if you show contempt, then the right thing for a healthy team to do would be to:
1) Address the contempt head-on, and then 2) Examine the data dispassionately.
It seems this team failed at both.
Probably a good thing to get fired from such a place, though it hurts to not be given an opportunity to move on on your own terms! This particular org appeared to be a pretty bad place to work anyway.
I once quit a job and when my boss asked why I was quitting it was the lack of retrospectives. The following week we had a retrospective, and I stuck around for a while longer.
That's how much I believe in it.
Of course, that company went from upstart to dominating its market in 5 years. Who knows if the fact that the whole company started constantly tuning its process helped? I'd like to think it did..
The rest of the places I was beaten down, much like the programmer in this story. Unlike that developer, though, as soon as I started to feel like the only skill I was valued for was raw programming I started looking for another job.
Good leadership is so hard to find!
Haven't used it to buy and sell things, though.
Also, you do not actually need to practice an hour a day to get the benefits. The above study has participants practicing on average 27 minutes per day.
And more. There really is no substitute that I've found.