Hacker Newsnew | past | comments | ask | show | jobs | submit | dhanush's commentslogin

Location: Bangalore, India (UTC +530)

Remote: Yes. Preferred. (I have previous remote experience)

Willing to relocate: Yes

Technologies: Python, Golang, Postgres, Redis, Kafka, AWS, Terraform, Docker

Resume: http://bit.ly/indradhanush_resume

Email: indradhanush.gupta@gmail.com

I recently finished my batch at the Recurse Center (formerly Hacker School), a twelve week self directed programmer's retreat focussed on becoming a better programmer. During my batch I wanted to learn about operating systems and distributed systems and built a toy UNIX shell in C from scratch and started implementing Raft, a distributed consensus protocol in Erlang.

Prior to this, I have worked for three years at an online payments startup where I worked across the entire backend codebase and spent a significant time working on the infrastructure team. I worked with: Python, Golang, AWS, Terraform and Docker. I enjoy designing and implementing fault tolerant systems and try to keep my programs small and concise, since I believe in the philosophy of less is more.

I have previous remote experience when I worked on my Google Summer of Code project in 2014. While I worked from my home in India, my mentor was situated half way across the world in Brazil. I was able to successfully use the project mailing list and IRC channel for all project related discussions.

Blog: https://indradhanush.github.io/blog

Github: https://github.com/indradhanush

Twitter: https://twitter.com/indradhanush92


Location: Bangalore, India (UTC +530)

Remote: Yes (I have previous remote experience)

Willing to relocate: Yes

Technologies: Python, Golang, Postgres, Redis, Kafka, AWS, Terraform, Docker

Resume: http://bit.ly/indradhanush_resume

Email: indradhanush.gupta@gmail.com

I recently finished my batch at the Recurse Center (formerly Hacker School), a twelve week self directed programmer's retreat focussed on becoming a better programmer. During my batch I wanted to learn about operating systems and distributed systems and built a toy UNIX shell in C from scratch and started implementing Raft, a distributed consensus protocol in Erlang.

Prior to this, I have worked for three years at an online payments startup where I worked across the entire backend codebase and spent a significant time working on the infrastructure team. I worked with: Python, Golang, AWS, Terraform and Docker. I enjoy designing and implementing fault tolerant systems and try to keep my programs small and concise, since I believe in the philosophy of less is more.

I have previous remote experience when I worked on my Google Summer of Code project in 2014. While I worked from my home in India, my mentor was situated half way across the world in Brazil. I was able to successfully use the project mailing list and IRC channel for all project related discussions.

Blog: https://indradhanush.github.io/blog

Github: https://github.com/indradhanush

Twitter: https://twitter.com/indradhanush92


Do you have any timezone restrictions for a remote position?


We don't have timezone restrictions.


Applied!


Hi,

The jobs page for engineering positions mentions only San Francisco as the available location but I noticed London in this post. Could you confirm this?


I'd like this confirmed as well please


Location: Bangalore, India

Remote: Yes

Willing to relocate: Yes

Technologies: Python, Golang, Postgres, Redis, Kafka, AWS, Terraform, Docker

Resume: http://bit.ly/indradhanush_resume

Email: indradhanush.gupta@gmail.com

I have 3 years of experience working in the backend and infrastructure team at an online payments startup. Currently I am attending the Recurse Center, a 12 week self directed program aimed at becoming a better programmer. The program concludes on 10th August, 2017. More about here: https://indradhanush.github.io/tags/#recurse-center

Distributed systems and network programming would be great. But open for anything interesting as well.


Hello, author here.

Thank you for pointing these out. I've corrected my assumption and put up a disclaimer on the post.


The ZeroMQ community is incredibly supportive towards newcomers and existing members alike. And ofcourse the people of the community are really smart, because you dont build a scalable and lightweight (and popular) messaging framework unless you are smart.

I have pitched in with a few (simple) commits once in a while and am looking to contribute more regularly.

Here's all the code: http://github.com/zeromq/

And a very comprehensive guide: http://zguide.zeromq.org/page:all

And, the contribution process followed is known as C4: http://rfc.zeromq.org/spec:22

You can get in touch via IRC, which is #zeromq on irc.freenode.net ; Try to linger around after asking your questions, and someone would eventually respond.

You may also send in your queries to the ZeroMQ mailing list. (http://lists.zeromq.org/mailman/listinfo/zeromq-dev)

Some of us also hang out in the #zeromq channel in the Slack group for Golang: http://gophers.slack.com/


You beat me to this!


Your battery's life is all about charge/discharge cycles. Say your battery has roughly ~1000 such cycles. Once you've exhausted the cycles, your battery is typically running on bonus power. Whatever performance you get after this is extra and cannot be relied upon.

Thus, the longer you can preserve your cycles, the longer your battery will survive.

You can also read this thread: http://www.reddit.com/r/askscience/comments/1snzg1/is_it_act...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: