-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core team leader application: Adhityaa Chandrasekar #3
Comments
well said "you try" :) |
That's up for debate :P |
Are you sure you're not going to port core to TrumpScript? :) |
@tulphoon ssshhhhh :P |
@adtac where do you see coala going? And this team? |
Are there any architectural or conceptual changes you want to achive? How do you want to organize the core development process? |
Hey guys, I just got a better internet connection (it's still a mobile connection, but it's at least 3G). Anyway, I just saw this - I'll draft up a reply and get back to you soon. Sorry about the delay, I can't really help it (my city got hit with a huge cyclone, so a lot of the digital infrastructure got smashed). |
@sils @sims1253 coala is taking a direction I completely believe in - aspects. Aspects are really how a user-friendly code analysis toolkit should be - I shouldn't need to care which bear to use. Hell, people don't even know what bears are when they first find out about coala. But everyone knows what kind of indentation they want - and it's a much better onboarding process if we ask them just the relevant stuff. IMO user-friendliness and performance are the two aspects (no pun intended) that coala needs to improve on. While performance is pretty decent for a code analysis application of this magnitude there are still a few milliseconds (or even seconds?) that we can knock off. There are a few open issues regarding this and I've done some research as to how we can improve (see this). We can work incrementally - one improvement at a time. Obviously there's a limit to performance - Python can only be so fast. But we can strive to achieve that ASAP. User-friendliness: coala has improved a lot since I first started. The CLI interface has been refined a lot and I think it's pretty good right now. However, as a new user, you wouldn't want to learn about each bear and its properties. There are resources that might help (docs.coala.io, bear-docs) but it's not the ideal way. coala-quickstart improve that a little IMO, but it's still not in the best shape possible. Aspects, however, are huge; and I think they'll help with this a lot - for both bear-writers and coala users. |
Bio
Well, I'm Adhityaa and I try to be funnier than Adrian. Anyway, I've worked a lot on coala's core since I started and I know how most things work and how things are done, which I think is crucial for a leader.
coala Contributions so far
I implemented caching in coala, which was a huge performance improvement (over 2.5x). I also managed the 0.8 release (this was across coala and coala-bears), compiling release notes, getting people to complete and merge their stuff. I've also worked on numerous things in coalib, implementing aspects being one of the more recent major features.
Road to the Future
I'll do my best to maintain the quality and keep increasing the pace of development to get more things done. I already have some experience with leading a major release, so I probably have a head-start in that aspect. I'm a huge fan of performant code, so that will be one area that is sure to get a lot of attention.
In short, I'm going to make coala great again, with big, beautiful, powerful features.
The text was updated successfully, but these errors were encountered: