deshpand

Growing up in a somewhat remote part of India, I would tune to BBC, Radio Australia to listen to test cricket commentary, on short wave. I have fond memories and owe a lot of my personal growth to SW.

Thanks for the clarification on this particular point. I was not aware of it.

I don't know all the history, but Magnus comes off as above the game.

“I am playing at least one more day here in New York and, if I do well, another day after that,” Really? And I saw another quote that said "f*k you"

Whatever his frustrations are with the governing body, the above are unacceptable behavior. I don't understand why they need to bend over backwards and modify the rules and mollify him.

He has also accused another player of cheating, after he lost, then he settles out of court. And he doesn't want to participate in the world championship, but chooses to make comments about the quality of games.

Of late, I have been googling a lot of SAS and may have contributed to its rise in ranking! Not coding in SAS but moving SAS to Python. Speaking of enterprise Java, there's a ton of enterprise SAS and it's moving to Python.

Not sure why you were downvoted. Fitness, equipment (racket and strings) are the reason if not the height. For height, above a certain level, say 6 ft 2 inch, it starts becoming a liability in movement. Tennis used to have a lot of variety in the past. Big serve and volleyers on grass, long baseline rallies on clay, slice backhands, flat strokes. Now it's monotonous.. the surface doesn't matter. The game with the most payoff is to stand back at the baseline and hammer the ball.

On a somewhat related topic, fitness has taken over many sports. In field hockey, dribbling used to be a skill. India was unbeaten for decades in Olympics, winning 8-9 gold medals. The introduction of artificial turf ushered in the era of strength and fitness, and the Western nations mostly took over.

I used to wear cotton long pants (thermals) all year, under the suit pant. Not letting the suit pant touch the skin made it easier to wear it for a very long time (multiple months) before dry-cleaning.

Don't miss those days of mandatory suit-wear.

I didn't mean to exaggerate. I think part of the improvement was the luxury of refactoring which should generally reduce the bloat. And, as someone else said, part of the issue is C++/Java, not static typing. When I move from Java to Python, I also get the luxury of organizing code into fewer/meaningful source files. I find this more readable, than having to switch to different files constantly.

I have not had a chance to learn or use a language like Go. But production use of Python, including building large code bases is real. We do resort to numba, cython or using Python API to compiled code.

I'm now involved in converting large codebases from SAS to Python. I don't think I will have the luxury of choosing another language like Go, for a number of reasons.

A ~100k LOC project in a statically typed system with type hierarchies, interfaces, contracts and boiler plate will boil down to ~10k LOC in a dynamically typed language like Python. A 10k LOC project will be more readable than a 100k LOC project.

Source: I have spent years coding in C++/Java, then Python. I have migrated Java projects into Python

Another advice is to have a thick skin and ignore the jerks, like for instance someone downvoting your note that was written with a good intention, sharing something learnt the hard way.

For longevity, I will provide one advice to younger people.. get away from the mouse as much as you can and use the keyboard. My working style is editing code in vim, dark screen, 2 buffers when necessary, go to the colon prompt to run the unit test or the script/driver and do this all day. No mouse needed until I need to check email or browse the web. There were times in my career when I was overusing the mouse and my wrist hurt. I have no issues now, 30+ years into programming.

No matter what your editor/language/framework choices, try to minimize using the mouse

Can you please elaborate why? I worked in Manhattan for many years, lived a few as well, and moved out in 2009.

I think it's helpful to keep in mind that Python is general purpose and used in many domains in addition to data analysis (no matter which side of the walrus operator you are on)

A little over a year ago, there was an incident with a lot of sites being down and Cloudflare/Lumen being involved (per Hacker News chatter, I only ready about the incident here). I bought a few shares of each, at around 39 and 11. While NET is down significantly from the peak, they have both worked out OK so far (LUMN has been paying $0.25 per quarter dividend). LUMN has been paying down debt and has good cashflow. They are contrasting and yet in a similar space.

In the end, it's not about an OPEN SOURCE tool being perfect but whether it is helping you solving a problem. If it did not help you and YOU don't consider it production ready, then that's fine. But you seem to argue that Dask should put this disclaimer out there. That would imply that many other open source tools including Spark would have to do it.

Dask has solved specific problems for us and we are grateful about it. I remain open minded about other choices and listed them with the understanding I have about them.

Switching to pandas when you can is going with the philosophy of keeping things simple. I like the flexibility of going back and forth between these as and when I choose.