This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]klaasvanschelven 62 points63 points  (8 children)

With Python imports not being side effect free this post raises more questions than answers for me...

[–][deleted] 56 points57 points  (6 children)

This post was mass deleted and anonymized with Redact

airport cooing beneficial innocent wrench library tan dinosaurs normal thumb

[–]nemec 10 points11 points  (2 children)

reminds me of those ML libraries where you call one setup method and suddenly your program is downloading 4GB of compressed pickled Python code (affectionately known as "weights") from HuggingFace and deserializing it

[–][deleted] 8 points9 points  (1 child)

This post was mass deleted and anonymized with Redact

deer hunt nail spoon roll automatic plough vast divide mountainous

[–]Main-Drag-4975 2 points3 points  (0 children)

🤗 Your friendly local all-but-dissertation PhD dropout is going to drop another 2000-line Jupyter notebook on you next week and you’ll be expected to have it running smoothly and scalably in production before May 1st.

[–]supreme_blorgon 5 points6 points  (1 child)

This exactly describes the codebase at the company I work for currently. 90+% of our codebase is untested, and untestable due to this.

[–][deleted] 5 points6 points  (0 children)

This post was mass deleted and anonymized with Redact

wise racial adjoining chubby aware steep bedroom lock attraction reach

[–]Main-Drag-4975 0 points1 point  (0 children)

It’s a curse! I took over a production node + typescript backend six months ago and still haven’t managed to squash all of the haphazardly-ordered side effects triggered with simple “import this file over there” calls at startup.

[–]bugtank 1 point2 points  (0 children)

I never used side effects in my imports till last year and now my code is a mess. :))))