Closed eak24 closed 6 years ago
I'm Ethan! I will be providing technical assistance and advising to the AIDE team. I worked a little bit over the summer to develop an application architecture for AIDE that we'll be following (more or less). Below are some fun facts that attempt to use as much GFM as possible.
I like to dabble in any language I need to adequately architect software systems. I like to create a coding environment, using development tools and good coding practices, to incentivize high-quality code. I'm a big fan of Git and GitHub.
I have a dog named Scout: And he is the love of my life.
A good quote by Ernst F. Schumacher:
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius — and a lot of courage to move in the opposite direction.
When you come to Honduras on the AguaClara trip this winter, you might find the following flavor guide useful for some fruits I haven't seen in the US:
Fruit Name | Flavor | Type of Plant |
---|---|---|
Maracuyá | Tart with a fantastically fruity smell about the size of an apple | Tree |
Lichi | Like a large sweet grape with a hairy cover | Vine |
Tamarindo | Astringent gooey seeds in a bean pod | Tree |
Lastly, here's a short snippet of code I came across recently that counts source lines of code. Use it to count the AIDE lines of python code - or whatever type you like, just edit it slightly!
## prints recursive count of lines of python source code from current directory
## includes an ignore_list. Also prints total sloc
import os
cur_path = os.getcwd()
ignore_set = set(["count_sourcelines.py"])
loclist = []
for dir, _, files in os.walk(cur_path):
for file in files:
if file.endswith(".js") and file not in ignore_set:
totalpath = os.path.join(dir, file)
loclist.append( ( len(open(totalpath, "r").read().splitlines()),
totalpath.split(cur_path)[1]) )
for linenumbercount, filename in loclist:
print "%05d lines in %s" % (linenumbercount, filename)
print "\nTotal: %s lines (%s)" %(sum([x[0] for x in loclist]), cur_path)
Can't wait to work on AIDE with y'all!
Let's try this again next year!
Hi @AguaClara/aide So nice to meet all of you the other day! I'm sorry about the technical difficulties. Luckily, we have alternative ways to contact one another (such as through GitHub issues) that aren't quite as bandwidth demanding 😄 .
On the right, you'll notice issues can be in projects, have assignees, labels, and milestones. It's most important to assign yourself issues as you work. This is how everyone on the team can keep track of what you're working on and provide suggestions. Issues will be the main way of contacting me (or anyone else, for that matter) to get help. To reach out to me, just use a mention by typing an "at sign" followed by a username @avtrigg , for instance.
In an effort to get everyone used to using GitHub, let's try introducing ourselves through this GitHub issue! Try to use as many GitHub Flavored Markdown (GFM) things as possible using that linked cheatsheet. For fun, let's each aim to each use at least 5 GFM things (links, italics, tables, code, etc) in our answers.
Also, be sure to include a list of your coding expertise - such as particular languages you like to code in and/or particular types of work you prefer (UI/UX or databases or server-side or front-end logic, security, algorithms).
I look forward to learning more about y'all!