TechAtHome: A 30 Days Study Jam

30Days Study Jam will be held in Streams. Goals: 1. Maintain a sense of community 2. Encourage collective learning 3. Leverage the strike period Start or join a stream, Join the train!

May 14, 2022, 7:00 – 9:00 PM



Key Themes

Career DevelopmentFlutterMachine LearningUI / UXWeb

About this event

Sequel to the furthering of the #ASUU Strike and the list of events we have for this session, we are bringing you a #TechAtHome experience

The #TechAtHome program will be practical - as are our previous programs - but it will be solely dependent on you. The program takes the form of a 30 Days Study Jam and will be available in Streams coordinated by Stream Leaders.

A Stream can be a Programming Language, a JavaScript Framework, a concept under a particular stack, Mastering a tool, etc. Participants will tweet their daily work using provided hashtags to create awareness and keep conversations going.

At specific timestamps, there will be a Google Meets call for each stream, where stream leaders and appointed speakers can do checkups, answer questions, give a demo, etc.

To become a stream leader, you simply have to:

πŸ‘‰πŸ» Select a concept to stream on that you know people would be interested in

πŸ‘‰πŸ» Get a minimum of 2 people to assist you in managing that stream should in case you were absent

πŸ‘‰πŸ» Pitch the stream details to any of the Core Team members

πŸ‘‰πŸ» Set a 30-day path with resources to guide you and whoever joins your stream

To become a stream member you simply have to:

πŸ‘‰πŸ» Decide which stream(s) to follow

πŸ‘‰πŸ» Follow the path by using provided resources

πŸ‘‰πŸ» Tweet along with your fellow streamers


Streams will span for 30 Days. The streams will focus on specific concepts, not broad ones, because of the 30-day timeframe.

Good examples of streams include:

1. Let's Learn Laravel (a Framework)

2. How to Use Docker (a Tool) for Deployment (a purpose)

3. Pentesting with Burpsuite

4. Typescript in Thirty Days (a language)

5. Coding Interview Preparation

Bad Examples include:

1. Backend Web Development (too broad)

2. Machine Learning Engineering (too broad)

3. DevOps (too broad)


πŸ‘‰πŸ» These are not yet available streams, so you have to pitch them again if you want to lead a stream

πŸ‘‰πŸ» You can follow one or more streams, although it is advisable to follow one or two, to help you learn better.

πŸ‘‰πŸ» Nobody is responsible for anybody's learning outcome, so nobody will force you to be consistent with your daily learning

πŸ‘‰πŸ» If there's a stream that people would like to join and it doesn't exist, feel free to bring it to our notice whether or not you plan to lead the stream.

πŸ‘‰πŸ» Each stream will have a Google Meets link attached to it for Saturday meetings, as well as the Stream Leader's name.

πŸ‘‰πŸ» You don't have to be an expert to lead a stream. You can be learning that concept from scratch too. However, you need to be good enough to stay consistent and answer questions if you can

πŸ‘‰πŸ» You can pitch a stream publicly or privately

Tweet Hashtags:




  • Peculiar Abolade

    GDSC Lead

  • Bello Taiwo

    GDSC Co-lead

  • Ashaluwala Kazeem


    Technical Lead- Mobile Development

  • Emmanuel Olaosebikan

    Technical Lead - Frontend Development

  • David Enikuomehin

    Technical co-lead - Frontend Development

  • Tolulope Adekunte

    Technical lead - Backend Development

  • Ademeji Michael

    Technical co-lead - Backend development

  • Kalu Samuel

    Technical lead - Data Science & Machine Learning

  • Akinleye Ayomide

    Technical co-lead - Data Science& Machine Learning

  • Paul Babatuyi


    Technical co-lead - Cybersecurity

  • Michael Modu

    Technical lead - Devops

  • Israel Agbaje

    Technical lead - Design

  • Tosin Ayoola

    Technical co-lead - Design

  • Nwachukwu Philip

    Publicity Lead

  • Anuoluwapo Ogunrinde

    Event Lead

Contact Us