jacobdi

5 ms·

1.
by jacobdi 4y ago
My team has been trying to modernize pandas from a different tact. Regardless of struggle with the syntax, it seems Pandas is very sticky, and we don't predict much migration to other data science languages. Instead of refining the syn
2.
by jacobdi 5y ago
I think this is spot on. I agree that Excel users want to stick with Excel, but they do run into major issues that are solved by code. Namely: their data size is too large, Excel is too slow, and they struggle to get repeatability from thei
3.
by jacobdi 5y ago
Spreadsheets versus programmers is a war that can be much more peaceful. In my work, I have found that, especially in data science, the spreadsheet user and the programmers are often trying to accomplish similar tasks, but the “language bar
4.
Read_HTML in Pandas in 2 minutes [video](youtube.com)
2 points by jacobdi 5y ago|0 comments
5.
My dog did my software demo(youtube.com)
1 points by jacobdi 5y ago|0 comments
6.
Low Code Python Is Available in Jupyter(medium.com)
1 points by jacobdi 5y ago|0 comments
7.
by jacobdi 5y ago
I have been working on this problem for a little while. I don't think the issue is that Excel is inherently worse for data wrangling -- it just isn't scalable or easily traceable. My solution is a spreadsheet extension for Jupyter
8.
by jacobdi 5y ago
Yes, 365 has definitely elevated Excel's collaboration. But in my experience, it has speed issues that can cause more problems than it solves.
9.
by jacobdi 5y ago
I used to work for a company making a bet against live collaboration in spreadsheets. I now see the error in my ways. A spreadsheet party in Excel would just be a nightclub that one person can enter at a time.