Python is Love

I feel truly sorry for the software engineers who develop code in anything else. Writing code in almost any other language introduces various **interface** problems. There is some algorithm, some set of actions a programmer wishes the computer would do. However, frequently, the programmer has to adapt their ideas to accommodate annoying language requirements, so instead of thinking about the actual procedure one has to waste time figuring out stupid bullshit. Not with Python though. I'm noticing again and again, especially when writing beautiful PEP8 compliant Zen Python code that as I work on improving the 'readability', I simultaneously improve the quality of the algorithm itself. Python is Love.

Comments (2)

23 years on the Earth

I got some theories about numbers. The one I feel strongly about is that 26 and 28 are two frequently confused numbers. I've been observing people mess those two my whole life. But maybe it's just some bias. ANYWAY. 23 feels like a lot! Going from 22 to 23 feels like the biggest jump so far. I don't think 23 go 24 or 24 to 25 will as much. Pretty haply with the current projectory. Could be better, but could be much worse.

Comments (0)

Feb 12

Maintanence: Got a temporary fix for THE problem. Side hustle: Soon will be revealed. All financial memevestors and wall street people - bEwArE! Cliche question/Food for thought: What does it take to be a good leader? I believe that EQ is a real thing. Essentially, I define it as an ability to accurately understand complex human interactions and respond properly to them. You have to understand the language of your colleagues (they should be on equal grounds with you). Keep in mind, however, that no matter how much you try to equalize the relationship, there is almost always going to be a sense of authority. This sucks, so do what you can to minimize it - empower, trust and delegate responsibility. The devil is in the details, of course, that's where EQ comes in handy. Let me know what you think in the comments below. Like and Subscribe.

Comments (2)

Feb 6

Alright alright alright. Hello, World! Work updates: I've been working on 3 (new) things these couple of months, and all of them are approaching the finish line! (First out of many, so like alpha versions): 1. Optimizing client onboarding process - This went really well, already tested the pipeline. Hot. 2. Inventory Throttling - This feature is my baby and it's really close to deployment. Money. 3. Revenue Projections - Picked up this project from another data scientist couple of weeks ago, and already nearly ready to deploy! Quick and Dirty. The last project is an excellent example of the difference between a good and a bad data scientist. The previous data scientist who was working on revenue projections worked on it for months. Countless Data Science meeting and countless documentations later, there didn't seem to be much clarity on the team. He is a really nice person with a math PhD background, and after talking to him about his ideas in person I realized that they made sense. What was missing though is his ability to get to the point, give tangible examples, and generally - communicate. I'm sure he knew more math and ML than me, but in a way, it didn't matter. What took him months took me 2 weeks and that's the moral of the story - difference between a good and a bad data scientist is literally exponential. And just to be clear, it doesn't take a PhD to be a good data scientist. Bonus: something awesome is coming. API related *wink wink* Something awesome: SEC - watch out!

Comments (1)