What is he misguided about, and what is the complexity he is simplifying. I ask out of genuine intrigue. Reading the post it comes across as someone who appeared to need to make a change in his life, unsure of what to change. He took a chance on a new role and has found himself happier for it.
OP is mistaking positive feelings (short term, extrinsic) with wellbeing (long term, intrinsic). Their excitement probably allows them to neglect any underlying problems. When the excitement wears off, issues that haven't been addressed are likely to reappear. All of this is purely speculation of course, based on my reading of the post.
Wouldn't "a rewarding career" qualify as long-term, intrinsic wellbeing? Cynics may believe no such thing exists, but I don't think it's a universal view.
Of course, there's always risk that the job changes and becomes worse. In a Series D company, we know that could happen at any time.
> Wouldn't "a rewarding career" qualify as long-term, intrinsic wellbeing?
Depends on what one understand by “rewarding”. If it's compensation, title, status, achievements, etc., these are extrinsic factors. Regardless, I don't see any evidence for a rewarding career in the OP.
I've generally heard "rewarding" in this context used to mean "satisfying and/or meaningful" – e.g, a teacher who loves their job and is able to see their students learn and grow happily would be said to have a rewarding job.
For OP, it sounds like an intrinsically rewarding job would be one that involves autonomy, decision-making, a sense of impact - which it sounds like they now have.
> Do not open your web browser unless you have a specific search query in mind.
I'd counter this one. I've too often caught myself watching something, talking to friends or reading a books and being captured by the need to just quickly google that thing triggered by what I am doing at the moment. Most of the time you don't really need to know that information, your curiosity gets the better of you. Instead, maybe just make a quick note and stay in touch with that you're doing instead. Otherwise your life just becomes an endless list of interruptions prompted by needing to know that "one thing".
occasionally when im having strong willpower i will force myself to not google whatever random fact i need to know. it’s almost physically painful at first, but then after a couple days my brain starts feeling much better
I like what you've done here. I've personally gone down the route of using SQLAlchemy to build queries. The primary reason is that SQLAlchemy lets me build up reuseable SQL elements, to encapsulate business logic, like metrics and custom dimensions in Python. In particular SQLAlchemy's hybrid expressions, that allow you to tie an SQL expression to a ORM model are super useful for doing this sort of thing. There's also first class support for CTEs, window functions and other advanced SQL features. For me there's just something "dirty" about using raw SQL in code, or even templating it, even with security concerns like injection attacks put aside.
I second the recommendation for dbt. Especially if you're following an ELT architecture where you load your data into a data warehouse and then want to transform it. However dbt is more useful for transforming existing data, or aggregating data in batches. It's not a tool for generating SQL expressions on-the-fly like your library would allow you to do.
