athensresearch / clojurefam Goto Github PK
View Code? Open in Web Editor NEWClojure Learning Program
Clojure Learning Program
Real name: Scott Starkey
Github handle: @Yekrats
Discord handle: Yekrats#1938
Team Name: Team Abrotelia
Cohort: Quoll Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @estellerostan
Discord handle: shafoo#2019
Team Name: Team Aurelius
Cohort: 1st ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Rich Hickey Checkpoint π
@nthd3gr33
This is an update on the proposed Airtable+Form approach to tracking learners' progress.
In response to #8 Linguaphile created an Airtable base prototype to keep track of all the learners' progress. Later I created this page incorporating Airtable's information as tiles and graphs (just each cohort's average progress for now).
In this latest update, I have:
Note that Airtable's API is not great for security. To call it dynamically we basically have to send the API key with the website. For that reason, I have created a dedicated gmail and Airtable account and gave it read-only access to the base. Even if the API key is exposed it won't be able to write to Airtable. Still not pleasant but I guess it should be OK in this limited case.
Remaining Questions
Improve the contribution experience for School Builders (people that contribute to ClojureFam and Education)
Revamp our project board. You could use Jeff's board in Athens as inspiration (it is π₯ after all). Or you can use a different style. That is up to you.
Feel free to add more issues. Ask @teodorlu, @nthd3gr33, or @Bardia95 if you need some ideas.
Github handle: @nthd3gr33
Discord handle (no @ please!): nthd3gr33#2205
Team Name: Team Seneca
Cohort: 4th Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Datascript π
π Projects π
Github handle: @alaq
Discord handle (no @ please!): alaq#6794
Team Name: Team Seneca
Cohort: 4th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Extra curricular resources π
Encourage Learners in ClojureFam to learn in public. Reduce friction for them to do so by having a simple place to host and display what they have learned.
Here are a couple examples:
https://github.com/alaq/learning-clojure-in-public
https://github.com/itsrainingmani/learn-clojure-in-public
Github handle: @txnka
Discord handle (no @ please!): tynka#1539
Team Name: Team Thales
Cohort: 6th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Name: Rob
Github handle: @robaguilera
Discord handle (no @ please!): robb#4589
Team Name: Team Pythagoras
Cohort: 1st ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Personal Study Material π
GitHub handle: @jsjoeio
Discord handle: jsjoeio#7954
Timezone: (Arizona/MST - no daylight savings)
Prior Programming Experience:
I learned how to code through freeCodeCamp. Since then, I've worked in the frontend doing JavaScript (React), fullstack doing React Native, GraphQL, TypeScript and Node. I've done some Python. Most recently I've been spending time learning Rust. As for functional programming, I understand some of the basic concepts.
Short Description (Optional):
Hi, I'm Joe. I'm from Arizona and currently work for Facebook as an Open Source Developer Advocate. I focus on programming languages (Rust, Reason, and soon Hack). Outside of work, I help developers learn quickly. I'm really intrigued by this model y'all have and I'm eager to join and learn Clojure!
Github handle: @noorfathima11
Discord handle: (noor A F)#2379
Team Name: Team Aurelius
Cohort: 5th Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Datascript π
π Projects π
First experiment with team progress issues and group #learninpublic!
Introducing... Team Phanes!
Phanes was the mystic primeval deity of procreation and generation of new life... hatched into this world from a Cosmic Egg π₯
@zacjones93
@theianjones
@shanberg
@ens100
@jsjoeio
@doingandlearning
@lostintangent
Github handle: @banditelol
Discord handle (no @ please!): banditelol#0582
Team Name: Team Seneca
Cohort: 4th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @baibhavbista
Discord handle: baibhavbista#1537
Team Name: Team Zeno
Cohort: 3th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Improve the general PM workflow in our ClojureFam repo.
Create a "New Issue Template" so that people can have an example to follow. You can either:
Github handle: @theianjones
Discord handle (no @ please!): ianjones#3696
Twitter: @_jonesian
Timezone: EDT
Prior Programming Experience:
My professional experience has been in Ruby on Rails and React. I graduated College with a BA in Computer Science in 2016 and have been working at egghead.io since then.
Short Description (Optional):
π I am excited about personal knowledge management. I have recently moved from Roam Research to Org Roam and have dived into emacs land. I have a digital garden where I write about what I am learning. I'm thinking there will be quite a bit more Clojure content there soon π I also have published content on egghead io mostly over GraphQL.
Github handle: @jorda0mega
Discord handle (no @ please!): jorda0mega#0542
Team Name: Team Archimedes
Cohort: 2nd ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @JosePtm2
Discord handle (no @ please!): jferreira#1277
Team Name: Team Aurelius
Cohort: 5th ClojureFam Cohort
Checkpoints
Introduce yourself to partner|team|cohort|mentor
Choose an editor
Get IDE and REPL working
GitHub Checkpoints
Subscribe to Athens repo
Subscribe to ClojureFam repo
Scan of entire athens repo
Comment on existing issue
WIP Pull Request
Successful PR Merge rocket
Getting Help
Ask a question in Clojurians Slack
Ask a question in Athens Discord
Clojure from the Ground Up Checkpoints
Chapters 1-3
Chapters 4-6
Chapters 7, 8, 10
4Clojure Checkpoints
20 problems
40 problems
60 problems
80 problems
100 problems
Clojure for the Brave and True
Chapters 3-4
Chapters 5-6
Chapters 7-8
Chapters 9-11
Chapters 12-13
Improve the experience for Learners and Mentors in ClojureFam. Create a sense of:
Many different ways to implement this, but here is one example:
Each card is a team, each column is a checkpoint. Checkpoints can be parts of the roadmap, such as 'first 20 4Clojure questions'
Draft
) and asking for comments is probably best for this type of task.Github handle: @ThiagosLima
Discord handle: thiagoslima#8684
Timezone: GMT-3
Prior Programming Experience: My experience has been in C, Python and JS (MERN) in college. Recently I have started learning functional programming. Mostly in Clojure and Elixir.
Real name: Prabhath Kiran
Github handle: @prabhath6
Discord handle: pkiran6#1730
Team Name: Team Euclid
Cohort: Quoll Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Build REST API in Clojure π
π Build web app in Clojurescript π
π Datascript π
Github handle: @joaoapel
Discord handle: joaoapel#6103
Timezone: UTC -3
Prior Programming Experience: I've done two bootcamps in data analysis and web development
Short Description (Optional): Agricultural engineer trying to make good software
Github handle: @itsrainingmani
Discord handle (no @ please!): Zeus#3345
Team Name: Team Seneca
Cohort: 4th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Extra curricular resources π
Github handle: @tomgiur
Discord handle (no @ please!): katatoniq#4509
Team Name: Team Thales
Cohort: 6th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @mnihalm
Discord handle : Nihal#4648
Team Name: Team Aurelius
Cohort: 5th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @your_name
Discord handle: your_name#1234
Timezone:
Prior Programming Experience:
Hours per week:
Short Description:
Github handle: micahredding
Discord handle (no @ please!): micahredding#8014
Team Name: Team Thales
Cohort: 6th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
There is a lot of excellent Clojure learning material out there already. We can curate that material. Less so for Datascript. We have a chance to make Learners' Datascript very relevant to Athens. Let's build this together ποΈ
Some or all (or more!) of the following: Curate existing Datascript learning material. Create Datascript koans. Improve the Datascript explorer. Create Datascript learning content (text, video, hybrid, interactive, etc)
Provide a place where people can find quick answers to questions. Reduces workload for admins and other contributors to ClojureFam.
Create a FAQs markdown file.
Feel free to look at a draft FAQs page that was started and never finished: Notion Doc - FAQs ClojureFam Very WIP
Look at other FAQ pages on Github. Can you find good examples?
Github handle: @baljeet
Discord handle: baljeet#5505
Team Name: Team Thales
Cohort: 6th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @bobdiya
Discord handle (no @ please!): bobdiya#9371
Team Name: Team Socrates
Cohort: 1st ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @gtoast
Discord handle (no @ please!): ghosttoaster|cimara
#4713
Team Name: Team Homer
Cohort: 2nd ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @jewiet
Discord handle : jewiet#0699
Team Name: Aesara
Cohort: Partner
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure for the Brave and True Checkpoints π
π Learn Datascript π
π Learn Re-frame π
π Structure and Interpretation of Computer Programs
Github handle: @juniusfree
Discord handle (no @ please!): juniusfree#6209
Team Name: Team Zeno
Cohort: 3rd ClojureFam Cohort
personal study material
Github handle: shanberg
Discord handle (no @ please!): shanberg#1349
Team Name: Team Phanes
Cohort: 7th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @yosevu
Discord handle (no @ please!): yosevu#9649
Team Name: Team Abrotelia
Cohort: 2nd ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Exercism Checkpoints π
https://exercism.io/profiles/yosevu
Core exercises (7/11)
π Getting Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π DataScript π
Why?
Because we decided to have Github as our main source of truth for the ClojureFam program
What?
Create clones of existing Notion docs
How?
Which docs?
Bonus: Create a FAQs page similar to https://github.com/docker-library/official-images#more-faqs
Where to host solutions to 4Clojure problems, exercises from books, etc.
Which option does everyone think is better? (for now; we can iterate on all of this as we go)
Github handle: @your_name
Discord handle (no @ please!): your_name#1234
Team Name: Team Amazing
Cohort: Nth ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github handle: @amirsato
Discord handle: Linguaphile#5330
Team Name: Team Aurelius
Cohort: 5th Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
π Projects π
I just finished ClojureFam last week and gathered a few thoughts to improve the program as well as some advice for current and new learners.
I posted it on the repo where I gathered all my notes: https://github.com/alaq/learning-clojure-in-public/blob/master/review.md but I am also pasting it here for reference. Hopefully we can discuss some of these points.
ClojureFam is a learning program for Clojure(script). Learners are put in groups by timezone and start learning in groups. It's great as one's progress pushes the others at the same time. The end goal of ClojureFam is to bring people up to speed with Clojure and the Athens codebase so that they can contribute.
The team behind sees a lot more happening with it. I particularly like the idea of an open-source lambda school.
So over the past 5 weeks, I have gone through the program. On top of it I committed to learning in public, as in post what I have learned or done that day (everyday) in a markdown file and host it in this very repository. Additionally I tweeted a daily (and much shorter) update with a link to the post.
Let's get one thing out of the way before I start commenting on ClojureFam itself, I would absolutely recommend the program to anyone even remotely interested in Clojure or functional programming. It's very rewarding, I loved most of it, and you bond with your cohort quite easily (after all you're in this together).
If a bootcamp prepares you for a job, ClojureFam prepares you for open source contributions. Today it does that for Athens (my team, Team Seneca already has several commits in Athens' codebase), but it can be so much more.
I attended the 6th cohort, which was mentor-less, so my comments are based off of that. I was very hesitant before enrolling because I really wanted a mentor. Besides the idea of building a PKM application the fact that ClojureFam had mentors was really what attracted me to the program. Really the question for me was why would I do ClojureFam over reading a book by myself. I can obviously think of a few reasons but you need a little something to convince you it is worth the commitment. If you do ClojureFam seriously, it is a time and energy commitment. It's also very rewarding.
I am a bootcamp graduate. Before that I was a self taught programmer/learner. Programming has been a hobby of mine for many years. I started with basic in 1999, before I had the Internet. In 2016 I started writing code for my employer, building their internal applications and even started a SaaS company. I felt like I needed a little extra push to turn this into a full time thing, so I enrolled in a bootcamp (Fullstack Academy in New York). This was probably one of my best professional decisions.
After bootcamp a lot of my classmates saw that contributing to open source would be a good way to differentiate themselves, so a lot of them ended up contributing to high profile projects such as React or Netlify CMS. I am not sure how many continued beyond their first commit. I can't blame them: landing a commit in React is a thrilling adventure, but it's a lot of work. I felt like I needed something else, maybe a project that I could get to know better. I met Ryan Dahl at BrooklynJS in 2018 and started to contribute to his latest project (PropelML) with his help. I landed a few UI commits and was starting to get a lay of the land. I wanted to regularly contribute small changes and progressively ramp up the size and quality of the contributions. Unfortunately the project was discontinued and Ryan went on to start Deno and I decided to focus on my job and inner source projects instead.
Without further ado, here are a few things I would change in ClojureFam.
The repository should become a manual and guide for the learners. It currently feels little bit disjointed.
Onboarding for New Clojurians should absolutely not live in Notion: it should be in the repository.
Ideally the repository should be the one stop shop for learners. This is coming from my experience in a bootcamp where everything was documented and easily accessible on the in-house platform. If everything is stored in the git repository it becomes something that gets iterated on by learners as people go through the program. The structure should be setup by mentors and contributors initially, but the details can
The curriculum should be stricter, since most people will know very little. The default should be to choose for them.
Starting with Clojure from the Ground Up and then redoing most of it in Clojure for the Brave and True made complete sense to me. The former was the introduction and the latter let me go more in depth and solidified my knowledge.
There are still some chapters that are not essential and can be skipped at the beginning. Concurrency should be kept, macros should go. The last few chapters of Brave Clojure could also wait until after ClojureFam.
For instance, one of the first tasks in the curriculum issue, along with setting up your editor, is to review the entire Athens codebase. I'm very glad I put this off for a couple of weeks because if you don't know [[re-frame]] you're going to be lost and it's going to be a waste of your time.
Similarly there should be a point in time when the learner can start tackling Athens' issues, and curriculum says so obviously. It seems that the learner would need at least to know about atoms to understand re-frame. And some knowledge of re-frame and datascript (and maybe some Datalog, depending on the issue) is probably needed. I see the curriculum as a tree, and different milestones unlock separate branches for the learner.
This is a logical extension of the learning tracks. It should be uniformized across learners. Ideally learners of a cohort should be learning the same thing at the same time, doing the same 4clojure problems (even together, ideally!). If someone is doing something different, it should be because they are already intermediate level and will be able to help the learners with less experience anyway.
The current tracking board in the ClojureFam repository is nice, but I am not sure everyone is actually updating their issues (unless they dropped out?) or that anyone is actually checking out other learners' issues. Honestly I had no idea if anyone was doing the program at the same time as us. The only hints have been the occasional PRs from people I knew were learners. I feel like learners would benefit greatly from seeing other learrners' progress, it would create some sort of emulation. I suggested we post updates on our issues, but even I did it only once, whereas I was able to post updates every day on twitter (maybe that was the issue). There could also be a Discord channel for learners to share their daily/weekly updates. It has just been created.
Taking the idea of tracking a step further would be to gamify the learning process. We sort of have this with the progress bar on the Github but the concept could be taken further. There may even be an open source solution out there that does this.
I can see a gamified curriculum where when you learn about atoms in Clojure from the ground up you unlock the front end track with the basics of clojurescript, reagent and re-frame.
Tracking, gamifying the system and overall being aware of what others are doing are definitely a way to foster the community.
There are other things that can be done to foster the community around Athens:
office hours could be super useful, especially for mentor-less cohorts. Learners could still rely on a more experienced developers to bounce of ideas, silly questions etc. Maybe current mentors can help in an ad-hoc fashion. It would be much less time consuming and probably more efficient overall.
The point I am making with better tracking will also help community
Ideally people would also make better use of the #learning channel, which would create connections between current and past learners
Learners should be encouraged to ask questions on pull requests (that could be almost a mandatory step). They will learn, but also start meeting contributors.
As Athens matures it will need developer documentation (for instance, how does Athens store data, how are keybindings handled) and it could be written by learners and reviewed by contributors.
There is also room for articles about the Clojure, and the codebase. For instance there is a need (when the codebase will be mature enough) for an article about the architecture of Athens. Think folder structure, glossary (what is datascript, posh, etc. how do they fit in together)
Encourage learners to find out about re-frame earlier and only after that look into the Athens codebase. Itβs pointless if you donβt know about the 6 dominoes.
If the program was a little longer there would be room for a side project. Mani and I did it, and it helped us greatly in our understanding of re-frame. It's one thing to read a tutorial and write the same exact code at the same time, it's another to attempt to do it in a quasi real life situation. A good inspiration for little side projects to tackle would be 50-projects-for-react-and-the-static-web by Colby Fayock. I built a decide wheel clone.
Let me start with saying that it's probably one of the best organized projects I have tried to contribute to. You can see that it's designed to let the core team have a birds eye view of what is in flight, future features, bug fixes while still making it understandable for newcomers. That being said, a few things may be doable to make it easier for newbies.
The issues could be easier to find. Currently there are some issues, there are some bullet points in the same issues, there are some cards in the projects.
Editor setup has been a mess for me. I started with VS Code with Calva but the vim keybinding don't work too well there (no support in the REPL for instance), then moved to Doom Emacs with CIDER. In neither of these editor did I manage to make the REPL work with the currently edited file (unless I was using use
). Now I am seriously considering trying out Cursive with the IdeaVim plugin. I'm not trying to blame anyone for my own shortcomings: the information is out there and ir's not Athens specific but I just wish the Clojure onboarding was a tiny bit better. By comparison, TypeScript on VS Code is amazing, everything works out of the box.
I decided to write an article a day about what I learned. Obviously it was more useful to me than to anyone else. It helped me reflect on and solidify my knowledge. I did engage with a few people, which was nice but most of all it is probably what kept me going the most. I HAD to post that update, and if I didn't have anything to write about, I wouldn't have been able to.
Even if you don't have time that day, find the time. Even 30 minutes, which I am sure you can find, is enough. It really helps to push the ball a little bit further everyday, it's constant progress and will prevent you from falling off the bandwagon. If you have evening plans, wake up a little early. If you can't do that take a break during lunch. Or go to bed late. I've done a combination of all of it. It's not easy but it's only 35 days, you can do it.
Do it, do 35 days, don't slack and I promise you will reach a minimum level where you'll be able to be productive enough so that it will be self sustainable. Hopefully by then you're contributing to the Athens codebase, and building your own little projects. Starting a new language is easy, especially if you know others, then it's getting really familiar with the libraries and the codebase that can be a little daunting. That's when you need to keep at it without break.
I absolutely recommend ClojureFam in its current form to anyone who is every remotely interested in Lisps and/or functional programming. It's a brand new world if you're coming from more object oriented languages.
The goal for me now is to turn my learning in public experience into a building in public one. I really believe in the Athens project and would love to get to a Clojure level that would let me make substantial contributions.
In true 20/80 fashion I will leave you with a few easily doable action points:
Github handle: @ens100
Discord handle (no @ please!): edns100#4851
Timezone: GMT
Prior Programming Experience: Little to none, started in the last month or so to learn Clojure after dabbling a little in Python.
Short Description (Optional):
Hi, I am Ed. In my day to day life I work as an accountant and in order to add a little spice I thought it would be a good idea to learn Clojure in my spare time. I am interested in Machine Learning and Big Data as well as being a little bit addicted to the various PKM apps out there. Want to learn Clojure as an introduction to the programming world.
To have a way for those who are waiting to get into either versions of the program to find a partner to study with until they enter the program. Partners could go on to be partners or group members when they enter the program.
The easiest way would be to use the two existing boards as a template to create the Learner Partner board. Each Learner could create an issue and then we place their cards into a "Searching for Partner" column.
Github @shanberg
Discord shanberg#1349
Timezone UTC-4
Prior Programming Experience 12 years of doing just a little actual programming as I could get away with as a front end designer and art director. I'm comfortable making small changes in whatever language, but frequently have to check a reference or ask a friend to tell me which reference I should actually be checking. I haven't tried to learn any language from the ground up before.
Github handle: @Kamalnrf
Discord handle: kamalnrf
Team Name: Team Thales
Cohort: 6th ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
Github (and twitter) handle: @zacjones93
Discord handle: zacjones#8126
Timezone: (EST)
Prior Programming Experience:
I started programming in college for my CS degree which I learned C++ (feels like ages ago now). More recently I've been in the frontend JavaScript world of React and Gatsby. I've had some exposure to functional programming (shout out to the mostly adequate guide) and want to explore that more through clojure.
Short Description:
Hi, I'm Zac. I live and work remotely out of Arlington, Virginia (US). I work for egghead which is an education platform that mostly teaches JavaScript and the ecosystem surrounding JS web development. I'm currently researching and applying instructional design to the courses that we help instructors create and am super intrigued by this async learning experience that y'all have created. Super excited to join in!
Github handle: @astridronja
Discord handle (no @ please!): AstridRonja#5291
Team Name: Zeno
Cohort: Nth ClojureFam Cohort
π General Checkpoints π
π GitHub Checkpoints π
π Getting Help π
π Clojure from the Ground Up Checkpoints π
π 4Clojure Checkpoints π
π Clojure for the Brave and True Checkpoints π
From Discord
My name is Jonathan. Iβm from Seattle and build dev tools for a living, but my personal passion lately has been in creating tools to enable better knowledge retention and sharing. Iβm excited to learn more and work with the awesome folks in this community π
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.