amirathi

13 ms·

91.
by amirathi 7y ago
> they decide to build their own closed-source platform How does it matter that the donation platform is closed-source? Open market principles still apply. People will (and should) use it as long as it's easy, efficient, cheap to do
92.
by amirathi 7y ago
To summarize, - OSS contributors on GitHub can apply to become "sponsored developer" to accept donations - Developer sets monthly sponsorship tiers (amounts & benefits) - GitHub will match upto $5k in donation in Developer&#x2
93.
by amirathi 7y ago
I am a solo bootstrapped founder (like yourself) and RescueTime consistently shows 45 to 50 hours per week. I strongly believe WHAT I do in those ~50 hours is much much more important than squeezing in another 10-20 hours per week.
94.
by amirathi 7y ago
You bet. I built ReviewNB[1] specifically for Jupyter Notebook code reviews. There's also, - nbstripout[2] for stripping outputs automatically before every commit - nbdime[3] for diff'ing notebooks locally - jupytext[4] for conver
95.
by amirathi 8y ago
Access to all/some contributor's local git repository is a powerful capability but you need to think deeply about 1 or 2 core use cases. "Pull up a chair" is only a surface activity, what's the user's real inte
96.
Show HN: Treon – Testing Framework for Jupyter Notebooks(github.com)
4 points by amirathi 8y ago|0 comments
97.
by amirathi 8y ago
Nice work! Do consider slapping a simple UI and hosting it somewhere online. You'll be surprised how many organic visits it'll get a year or two from now. Bonus points if the website copy overlaps well with search keywords :)
98.
by amirathi 8y ago
> this generalist thing is utter nonsense By your own description, you sound like a generalist with ability to dive deep into the areas needed. You seem to refute the core premise of the article but your description says otherwise.
99.
by amirathi 8y ago
Converting notebooks to markdown is a fine idea (although you have to maintain both versions). I built ReviewNB ( https://www.reviewnb.com/ ) specifically to review Jupyter Notebooks on GitHub.
100.
by amirathi 8y ago
Why write emotionally charged letter instead of one backed with facts? Amazon is claiming [1][2] that Elastic has been intentionally unclear about what part of Elastic stack is open source vs proprietary. It would best serve Elastic if they
101.
by amirathi 8y ago
I built ReviewNB [1] to see visual diff for Jupyter Notebook changes & do a code review on it (by writing comments on cell changes etc.). One of the next feature for ReviewNB is a CI pipeline for Jupyter Notebooks on GitHub. The idea is
102.
by amirathi 8y ago
If you focus on increasing engineering quality, retention will follow. > there's still an astounding number of bug reports for a simple app. Why don't you reverse engineer some of these bugs and see how & when they were int
103.
Google Launches Family Link App(families.google.com)
6 points by amirathi 8y ago|1 comments
104.
by amirathi 8y ago
Very few people donate because they feel benevolent. Most Patreon type donations come because companies either want to sponsor further development or need a maintainer for the critical OSS components in their stack or both. If you are only
105.
by amirathi 8y ago
- Never aimlessly browse through large codebase. Pick a change you want to introduce, maybe a string change, a small bugfix, low hanging feature etc. Goal gives you the motivation to keep digging through things and in that process you make
106.
Show HN: ReviewNB – Jupyter Notebook Diffs for GitHub(reviewnb.com)
4 points by amirathi 8y ago|0 comments
107.
by amirathi 8y ago
> A given feature/bugfix/whatever is gonna take as long as its gonna take. If this is every developers attitude how can the team make any plans about product roadmap? How would the team decide what to take on in a week/mon
108.
by amirathi 8y ago
Earlier this year, I wrote these tips to improve estimation: https://blog.amirathi.com/2018/02/05/science-of-software-est... I will summarize it here: - It's not just about code. New developers typically
109.
by amirathi 8y ago
I disagree. At Amazon, I never saw anything free in the break room except drip coffee. Stock has soared 6 times in 6 years. At a startup, we always had free lunches every day (virtually anything you want) despite up and downs in the busines
110.
Show HN: Rubix - Python Library to do DevOps in Jupyter Notebook(github.com)
1 points by amirathi 8y ago|0 comments
111.
by amirathi 8y ago
Version control for Jupyter notebooks was one of the biggest complaint I had. Specifically, diff and merge with the JSON files (.ipynb) is ugly. I built ReviewNb[1] to solve one of those problems (diff). Note that, there is nbdime[2] which
112.
by amirathi 8y ago
Really good talk. Here's the video: https://www.youtube.com/watch?v=7jiPeIFXb6U And all JupyterCon 2018 talks if anyone is interested: https://www.youtube.com/playlist?list=PL055Epbe6d5b572IRmYAH...
113.
by amirathi 8y ago
There's a great opportunity for someone to build a team communication tool that's more forum-centric than channel-centric. Let me explain the core problem with slack (or any channel-centric chat). When I join a wide slack channel
114.
by amirathi 8y ago
Nice idea! Why not just put pricing on the site instead of asking people to email for it? I understand it's a deeply technical product and you probably just built an MVP (congrats!). But definitely think about distribution and pricing
115.
by amirathi 8y ago
Sounds like more established tech companies might be a better fit for you at this time. - They can afford the time while you ramp up on new technologies, frameworks etc. A typical startup would expect you to be productive in month 1 (if not
116.
by amirathi 8y ago
I am working on Jupyter Notebook diff tool: https://reviewnb.com It's stimulating to write diff algorithms when textual diff is coupled with images, markdown, html, and code syntax rendering. Also, it's super useful fo
117.
by amirathi 8y ago
Nice! Meeting hell is a fantastic problem to take on. In the same vein, please consider generating stats for slack and other chat app usage as well. Would be very valuable to clearly see it's impact on roles primarily hired for buildin
118.
by amirathi 8y ago
> Also remember that sometimes it's not a good fit, and that's okay One can go beyond and suggest alternatives to their own product that might be a better fit. Remember to keep customer's best interest at heart. I'm i
119.
by amirathi 8y ago
I understand the benefits of keeping front-end separate from back-end. - Separate teams working on front-end and back-end independently - Front end bundle can be served fast and cheap via CDN (only the naive serve static files with gunicorn
120.
by amirathi 8y ago
What I really need is a python web framework that has first class support for serving SPA applications (VueJS, React etc). I spent quite a bit of time setting up my Django app to serve VueJS (replacing the built-in Jinja templates). Once re

More ›