Cached version → http://archive.today/O46rw

I am especially curious about this one. Do you have the dialogue saved?

I have been using it for years, and—judging from it's visual design—it has been around for years longer.

  df.assign(COLUMN_C=lambda x: x['COLUMN_A'] + x['COLUMN_B'])

Can you recommend any noteworthy resources for a data scientist who is interested in learning more about software engineering patterns like this?

The solutions presented typically include both a "basic" approach, a "as pythonic as possible" approach, and a brief discussion of the trade-offs between elegance and readability, etc.

Pros: Among various types of breaks one can take while WFH, showers feel particularly restorative. They also sometimes end up being surprisingly productive—diffuse thinking modes, shower thoughts, etc.

Cons: The "when" of showering was previously an automatic outcome, but now it is a conscious decision/obligation. I also find (as many people do) that showers give momentum to my morning, which is arguably more useful when just waking up than mid-day (although YMMV here).

In case you're interested, I wrote up the steps I took here → https://geoffruddock.com/geotag-lightroom-photos-with-google...

That said, it feels like there is likely some sort of Pareto efficient frontier with regards to complexity vs. usefulness. You can certainly have a poorly-designed system which is arbitrarily more complex without being anymore useful. But if you make things "as simple as possible" for any given amount of complexity, there will always be some underlying trade-off.

Brings to mind → https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...

> Additionally, the factors are expressed as positive attributes and an option either has that factor or it doesn't.

This is very intuitive for binary decisions, where the "pros" of one option are the "cons" of the other. How do you scale it to multiple options though? (e.g. if I am deciding between internet providers, speed is clearly an important factor, but I may have 3 options with low/medium/high speed respectively)

Does anyone have any advice or acquired wisdom related to onboarding remotely as an employee? Most HN threads on the topic of remote onboarding approach it from the employer's perspective (https://news.ycombinator.com/item?id=16978946), and so many of the suggestions—such as having good READMEs, etc.—are not really actionable as an individual employee being onboarded.

Last time I joined a company, I initially under-invested in building the informal relationships and social ties which prove to be valuable in the long-run. I am particularly interested in strategies to build relationships in a purely remote setting, which poses the additional challenges of awkward Zoom meetings, and lack of opportunities to build rapport in-person or engage in spontaneous interactions (grabbing lunch with someone you meet in the hallway, etc.)

Comments URL: https://news.ycombinator.com/item?id=23360424

Points: 2

# Comments: 1

> I don't see how cards would help me with mathematical ideas. You have to get them on a fundamental level, and then they're hard to forget.

I find it too easy to trick myself into believing I understand a concept on a fundamental level. But often that "understanding" slips away, and six months later when faced with an example problem out of context I struggle to solve it.

Location: Berlin, Germany

Remote: Yes

Willing to relocate: No

Technologies: Python, pandas, numpy, scikit-learn, matplotlib, seaborn, SQL

LinkedIn: https://www.linkedin.com/in/geoffruddock

Personal: https://www.geoffruddock.com

Email: geoff [at] ruddock [dot] ca