Replies: 11 comments 3 replies
-
I don't have OSD700 in Winter, but I'd love to join this ride.
Definitely work in this area.
This is exactly what I want to do after taking OSD600, so I'll research this as well. |
Beta Was this translation helpful? Give feedback.
-
Gonna be in DPS911. So far I'm interested in:
Besides that, maybe:
I'm generally interested in small UX changes that will make using the app less of a pain. Since I learned some design stuff before, I might have something to offer in this area. I'm also all for adding cool things. Assembling, sorting things into clear categories, "cleaning up" one might say. I have no clue on what to do with docker, servers/clouds, mobile. Personally hate react, so that's a clear no. I'm open to choose a niche which I would specialize in as a general idea. I just want to play to my strenghts and be useful to the project. Perhaps docker doesn't sound that bad if I get to know it? Also, if at any point anything is developed in Go - count me in. |
Beta Was this translation helpful? Give feedback.
-
I might not be as active this time compared to last year with my co-op but it's nice to see that there's a few areas that I can contribute in, whether I'm actually coding in or providing mentor support to whoever takes on the issues I'm about to mention: Search: I worked alot with the search related content and did lots of reviews on the 2 advanced search PRs still up. UI ain't my thing but anything logic related to the search will be fine with me. Auth: I didn't get to explore key signing as much as I wanted to with the work on the microservices, so this is definitely something to keep watch over. How this will get integrated with the staging and production servers is a whole other story. Serverless technology and Cloud integration: I have some experience with Azure, although it looks like AWS might be the move. I'm keen to get some more knowledge on this area, such that I might eventually pursue a career in this area. It's very fascinating. Redis corruption: The one thing that confused me the most working on 2.0 last year. I have a comment on the original post here for anyone that wants to pursue this solution. Ideally, whoever ends up working on the parser service can tackle this since it's sorta related with each other as well as anyone who worked with Redis. User Service: @chrispinkney been bugging me last year with reviews on this bad boi and he put a lot of work into this, so I have a general idea of how it works including how it's connected with the auth service. If we transition to Supabase, I can help out here wherever is needed. 3.0 doesn't have many big stuff aside from the parser service, user service, auth, cloud based work, and the react native cross-platform work. I actually have worked with making mobile apps using ionic so that along with my love for React should mean that I'd be interested in working there too. That being said, the only issue that truly matters is getting that TELESCOPE PODCAST UP. |
Beta Was this translation helpful? Give feedback.
-
Here's my idea for V3. Our site does not take full advantage of server-side-rendering. Go to Telescope with Javasript disabled , only the banner shows because posts fetching is done on the client. This is not very SEO friendly, and slow. React 18 has the new React server component to render components on the server, but, Nextjs's support for it is still Alpha. Plus, to use RSC, we should not have We could use Moving forward, we should improve how Telescope displays blogs:
If we do this, Telescope will be more supper SEO friendly, without Javascript, the home page shows cached first 30 posts, single post view is pre-rendered. It's also fast. Not sure if we should do this for Telescope, some people might prefer seeing everything on the first page and don't have to click on a post to read more. |
Beta Was this translation helpful? Give feedback.
-
I wanted to add some notes about data mining posts for GitHub data. One of the big things I hear students talking about is that they have a hard time finding open source projects to work on. To me, this is hard to understand, given that there are literally millions of options. What I think they mean is that they want to find a project that they could work on (i.e., one where they already have the right skills). The truth is, at this stage of one's tech career, you don't have all the skills you need: you're going to have to include some research and learning on any project (even ones you start yourself!). While we can't magically overcome lack of self-confidence, we can provide some data and options. We know that former students have done this successfully (at least I know this). Every one of our students is capable of this, because all those that have gone before were capable of it too. It would be good to provide some proof of this. Buried in the old posts are hundreds, if not thousands, of pull request links. Once we have a PR URL, we can use it to get all kinds of data from the GitHub API. Here's a sample response: Sample PR response from GitHub API
There is a ton of data here. We could extract a lot of interesting details:
There's a lot more we can get from the GitHub API, and it would be interesting to slowly add all that. Once we have that data, we can aggregate it to find out:
This data could be shown in a cool list that is constantly updating, and it would help our students see that a) this is possible; b) there are ways to get involved based on the past. |
Beta Was this translation helpful? Give feedback.
-
I was part of the team that shipped Telescope 1.0 (Gatsby era) and I would love love love to see
I imagine this as another frontend that would work alongside our Nextjs frontend and both would be interacting with the same backend services. So it would make sense to take care of the backend technical debt before moving forward with this. Years later and I haven't gotten around to asking about the shape of our Redis and Users service. In particular, are we dealing with SQL or NoSQL tables? I don't know the details because I have this weird phobia of the backend that I'm trying to overcome. We have a Users service that's currently hooked up to Firebase and I believe it's a NoSQL database.
I work with AWS technology and I also hold the AWS Certified Developer - Associate certificate so I can help with this. At the minimum, I will have time to consult the team on best practices in the cloud and what AWS technology/services are available for our use case. I haven't worked immensely on Telescope since we shipped Telescope 1.0 and many things have changed since then so the more information I have on hand about the current state of Telescope and where we want to take it, the better I can make recommendations on our path to the cloud. |
Beta Was this translation helpful? Give feedback.
-
I sure missed out the discussion. I'll be joining DPS911 and I am more keen on:
Since I worked on an issue that related to Parser service and the backend, I'd love to dive deeper into this topic.
I wouldn't want to miss out on the chance of learning Docker. I've been using it without much understanding Besides, if possible I'd love to explore more capabilities of React serving different use cases including React Native for mobile. My goal for this term is to try to thoroughly review at least a few PRs, I wasn't an active reviewer in the last term. There's one thing I'd like to add is an overview of |
Beta Was this translation helpful? Give feedback.
-
I am taking OSD700. Things I am interested to learn/practice are:
I have worked with React Native a few years ago and would like to revisit it here:
Always wanted to learn how to work with the cloud so this would be great:
I also wanted to learn Kubernetes
One of the things I saw that was cool was creating a podcast! I have worked with a few technologies regarding livestreaming video/audio/chat and might be able to help with this! |
Beta Was this translation helpful? Give feedback.
-
I am taking OSD700 :D
Recently, I am kind of curious about mobile development, so I would like to try working on something related to React Native apps for Android as well. Just experiment and see how it works.
Hopefully, we will be able to improve Telescope together 🦾🦾 |
Beta Was this translation helpful? Give feedback.
-
I am taking OSD700 this semester, and this is what interested me in this term:
I want to have a better sense in Docker, so this is the opportunity for me to learn and have more experiment about this.
I always want to go deeper with React, and more importantly, having more experiment in the real project would help me gain more experience. |
Beta Was this translation helpful? Give feedback.
-
Hi @humphd, I want to work on this one. Where should I start? |
Beta Was this translation helpful? Give feedback.
-
Next term we embark on another round of OSD700/DPS911. The new crew is going to be inheriting a fairly large and mature code base, with quite a few things that still need to get done. There are also things I'd like to add.
Lots of issues are filed already, but I'd like to discuss some ideas for the 3.0 release, and beyond. I'm interested to hear from current and former team members about what they'd like to see us do in the new year.
Technical Debt
Here's my "top 10" of TODO items we need to get done:
src/backend
and run everything from microservices. Among other things, this will require us to get the Parser service working.New Directions
Here's my list of cool things we should consider doing:
What about you?
I'm interested to hear from our amazing community. What do you think we should be doing next? What are your priorities for Telescope in 2022? Please add your thoughts below.
Beta Was this translation helpful? Give feedback.
All reactions