Hey there!
You probably already know what What’s NeXT (ha ha) is all about.
I mean, you’re subscribed if you’re reading this. Or not.
If you’re not, please click that button right there. You can subscribe for free and get an email every time we send out a new issue.
Go ahead, it won’t bite you.
Here’s what we’re going over in this issue:
Open-Sourcing our Team
Our Robot Kanban Board
Intro to our Team
What you can expect from now on
We’ll try to keep each issue concise, all while going in-depth to our team. We’re interested to see where this goes, so we thank you once again for checking it out.
Open-Sourcing our Team
Over this last year, the COVID-19 Pandemic put everyone’s lives into disarray. Everyone had to cancel their plans. Our normal way of life changed, where all these precautions became the new norm. But even through all of that, people created. And we, along with all other robotics teams, have the opportunity to create and compete.
To start off this issue, we’d like to give a huge kudos 👏 to everyone. Whether you’re a rookie team, a second year, even a tenth year. Even in a time where everything could go wrong, you continued on with your passions.
So let’s talk open-sourcing our team.
We’ve been looking at the amazing amount of rookie teams this year, across Discord, Reddit, even the FTC Forums. A lot of them seem to be doing really good, even in these uncertain conditions.
But there are those that could use a bit more help. Even teams that have been there for a few years that might need some help.
So, we decided to open source basically everything we do. Here’s how that works;
HARDWARE
For all of our hardware, when we mention something or go into something in-depth, we’ll share a link to our direct CAD file. We’ll try to share it in OnShape, so you can check it out immediately.
SOFTWARE
All of our software is publicly available on our GitHub repo;
Any new code we make will automatically be updated here, and we’ll share portions of pseudocode along with it on these issues.
Our core values include equal opportunity and full transparency, even if we’re wrong. If there’s a better solution, let us know :)
If you’re a team wanting to go open-source, reach out to us. We’d love to hear from ya.
Our Robot Kanban Board
Continuing our value of full transparency, we’re sharing some of our essential tools in our day to day workflow.
One of those tools is our Trello Kanban board.
Kanban is a lean method to manage and improve work across human systems. This approach aims to manage work by balancing demands with available capacity, and by improving the handling of system-level bottlenecks.
Here, you can see what we’re working on, what we’ve completed, and what we’re planning to do.
It’s another way we can show you all what we do, and how we plan to do it.
We plan on diversifying and making the board more interactive over time, with updates regarding everything we do.
You can check out everything we do, just hit this button;
Intro to our Team
Over the course of these issues, we’ll have different members of the team writing and sharing their perspectives and outlooks. Here’s some quick info about us;
Ritesh - Team Captain
Kiyan - Build/Design
Atharv - Build
Michael - Build
Nitin - Design/Outreach
Irving - Programming
Rajit - Programming
Ian - Programming/Outreach
Jason - Programming/Outreach
While that list seems a bit convoluted, everyone brings something new and interesting to the table.
What you can expect from now on
So finally, here’s what you can expect from new issues of What’s NeXT?
Solutions
Problems (there’s a lot of em)
Deep dives into our code and CAD
Links to resources we find helpful
Robot Analysis
Events/Scores
Random discussions we have from when we work
Things will be changing all the time, and so will what we talk about.
That’s all folks!
This has been a pretty long issue, but we had to clear some stuff up so we can get more info-based issues out there.
Once again, thanks for reading,
FTC#14786, NeXT
Its a good Day Today , when things are going this way ( Inspiring )
Nice Job! Excited to read more!