4,836 karma · joined July 9, 2008
[ my public key: https://keybase.io/jreese; my proof: https://keybase.io/jreese/sigs/oMm1rGpBWQUZlYjQeGCSD25PvSnx2g6ZuaQ89HzjO2Q ]
1) build a plan and make meaningful progress on a high impact, but stalled, project
2) communicate about progress and/or roadblocks to the team, and ask for help where needed to get past said roadblocks
3) be more proactive about finding and proposing high impact work, or areas where others could bring their expertise to help benefit my work or get it done faster
Details are confidential, of course.
https://cdn.n7.gg/pip/pip-1.png
https://cdn.n7.gg/pip/pip-2.png
Not every company is awful.
- everything is some shade of white/grey/brown
- snow is incredibly reflective
- winter is cold; sensors are almost certainly affected, dirty, or covered
- pedestrians are bundled up, looking less like people
- road markings are obscured or buried
- signs are dirty
- stopping distances are increased
- speeds must be slower to compensate for lack of traction
- "traction control" only helps when accelerating; stability control and ABS only help so much in snow/ice
Oh, I hope there's a good story for this
foo = (
spark.read.parquet(...)
.filter(...)
.withColumn(...)
) $ usort diff foo.py
--- a/foo.py
+++ b/foo.py
@@ -1,2 +1 @@
-from x import a, b, d, e
-from x import c as C
+from x import a, b, c as C, d, e
https://usort.readthedocs.ioThere is no "promise" other than "initially free", which almost certainly guarantees it will soon be hosted on NYT and require their subscription to play.
The biggest reason is µsort's detection of sortable "blocks" of imports, and only sorting within those blocks to limit breaking changes, combined with use of proper parsing and CST manipulation to guarantee valid syntax after sorting.
https://usort.readthedocs.io/en/stable/guide.html#side-effec...
Another coworker and I have created an import sorter that fits well alongside Black, called µsort. It is designed from the ground up to be a safe, stable import sorter that won't move imports in ways that potentially change behavior of the codebase, and without needing developers to litter their code with "skip" directives. We use it in our daily formatting codemods on tens of thousands of source files every day, and just finished our 1.0 release in December.
Going further, if you like enforcing both formatting and import order in your CI pipeline, I also created the project µfmt, which combines both Black and µsort into a single, atomic formatting step. This ensures there's never any conflict of opinion between the two tools, and any formatting changes are presented as a single diff result.
Is there any way this can also include the battery level of my Apple Watch? I'm a sleep tracking user, so I have to find some time during the day to charge it, and I frequently find myself missing the taps when it gets to low battery.
Thank you for your work on this!
If the only expected users of your API is your own project, it's an application.
And yes, if you need to build native extensions, setuptools is still your only real option. It's not great, and results in hundreds of packages that all find their own definition of insanity. But given just how crazy the C/C++ toolchain ecosystem is, especially when you have to deal with Windows, macOS, and the diversity of Linux, no one else has been will to tackle that problem because setuptools already exists.