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

  ╔══════════════════════════════════════╗
  ║ Hi, I’m Aru. I’ve architected        ║
  ║ production systems from ground-up    ║
  ║ and led diverse, distributed teams   ║
  ║ in past start-ups and I’m looking to ║
  ║ channel that zest into a bold        ║
  ║ company that’s solving meaningful    ║
  ║ world-changing problems. I can build ║
  ║ anything under the sun, and I thrive ║
  ║ in intensely creative positions      ║
  ║ where I have room to think outside the box.
  ║                                      ║
  ║ Location: Austin, TX                 ║
  ║ Remote: Yes                          ║
  ║ Willing to relocate: Yes             ║
  ║ Technologies: Python, Pandas,        ║
  ║ PyTorch, React, TypeScript,          ║
  ║ Django, Docker, iOS                  ║
  ║ Résumé/CV: aru.ai/.resume            ║
  ║ Email: See resume                    ║
  ║                                      ║
  ║ I’m looking for a culture that       ║
  ║ values deep work and                 ║
  ║ conscientiousness. I’m open to all   ║
  ║ companies – big or small, so please  ║
  ║ reach out if you find that I am a    ║
  ║ good fit.                            ║
  ║                                      ║
  ║ P.S. there’s an unsolved puzzle at   ║
  ║ the bottom of my site                ║
  ╚══════════════════════════════════════╝


For MacOS Chrome users: ctrl -> cmd, shift -> alt.


Last one beats me, fun puzzle though :).


I like what you did there.


this is great man!


Thank you – made my day!


If your site has less < 5,000 users a month, I can't imagine exceeding Lambda's free tier limit. You definitely want to go serverless if budget's a constraint.


I'm not going to make a new AWS account to take advantage of the free tier


AWS Lambda is (currently) part of the "Always free" tier, with up to 1 million(!) requests per month. (See: https://aws.amazon.com/free/?all-free-tier.sort-by=item.addi...)


wow thanks!

the next question is whether I should have just one lambda call that gets my external data and serves it to the clientside requester

or if I should have one lambda that does gets my external data on a timed job, caches the response in a database, and a separate lambda that reads the response

on AWS it seems the databases are the most expensive thing

guess I could also just cross that bridge when I get there, just feel like I could get spammed to a big bill even if I put in some session variables client side

this is just a static website trying to power a data visualization on semi-live data


I use this in combination with fish shell and it's been working really well. I can just switch over to `nu` when the task merits; no need to replace my current shell. I can also just run a one-off line like this.

   nu -c "ls | where size > 10b"


I see the value proposition of nushell. I'm wondering if I should also try fish.

May I ask if you switched to fish from zsh? What motivated your change?

Background: I invested some time not too long ago to read zsh docs in detail and customize my own configuration (e.g. instead of using oh-my-zsh). Since then, I've been quite happy with zsh. That said, I'm also open to switching to fish and/or nushell based on recommendations.


I didn’t switch from zsh, but from bash, to fish, primarily because bash was occasionally a bit clunky to use, and there were a lot of things that could be optimized in a modern environment. I settled on fish because it suited what I was looking for: an ergonomic shell that worked well out-of-the-box. Paired with strong community support, clean scripting syntax, and a wide ecosystem, it makes for a really enjoyable shell experience. I haven’t tried zsh, so I can’t compare the two.

I’m happy with fish, and I don’t see much benefit to switching to nu. nu is exceptionally good at one thing: working with data, but lacks features in other areas (auto-completion, scripting, etc.). With time, I can see these features being implemented, but I think they’ll be re-inventing the wheel in a lot of areas that other shells are already good at.


> what motivated your change?

didn't switch from zsh but bash, did it because wanted a bit more features at shell without additional configuration


How does it compare to fish shell (especially fish’s great autocompletion), e.g. why are you not switching completely?


nu is still in its infancy, and currently lacks critical features of other shells, which is why I haven’t switched completely.

As for the future, perhaps a bit brazen, but I’m confident that other shells will introduce the core feature of nu in the near future to stay competitive. I can see fish having a “||” operator and rewrites of a few gnu functions to achieve what nu does natively.


I resonate deeply with this.

I think this is strongly associated with effective altruism; It would be helpful to start with the very basic things you could do to improve the lives of others: volunteering at local food banks, teaching in places without suboptimal education, donating to reliable organizations, e.g., but since you have a highly valuable skill (you presumably have a high paying job), comparative advantage would suggest to apply your technical skills towards social good.

It would be a good idea to start by identifying problems in the world, at a macroscopic scale. The UN Sustainable Development goals would be a strong place to start. Dive into a problem, learn it’s intricacies, and figure why it cannot be resolved. We’re usually not limited by resources, but rather our allocation of these (I read somewhere that 30% of food grown is not eaten). If the limitation is something that can be lessened with technology (e.g not politics, insufficient resources, or other non-intervenable factors), then it simply comes down to creating a solution or to join an organization with an idea, but needs help.

If you find something, please do reach out. This is also something I’m searching for.


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

Search: