Sprint 6 Review

-
Today I met with my adviser for the sprint 6 review and demo. It was pretty uneventful. I didn't get nearly as much done as I had hoped due to the busy holiday season (even programmers have friends and family, shockingly!), but what I did get done went well and turned out fine. All but the complicated  (recent activity/unfinished tasks/blocking tasks) read-only pages are done, and all of the creation code now works, so I demoed that.

Then we discussed the project's email update capabilities, as I realized during the sprint that we'd never really talked about how that should work. If a user sets their preference to receive update emails, they get emailed when updates occur to their projects and tasks. I had originally set it up so that only the task creator and assignee would receive emails, but my adviser decided he would want emails as an instructor for every task update, even in the case of a student-led project where one student might create the task and assign it to another student. So we hashed through the possible scenarios and decided who should be emailed when and for what types of events.

We also discussed the plan for next semester, since this was the last meeting we'll be having for awhile. My adviser wants to use my system to manage other students' projects next semester, as well as managing my own project. Very meta. So I need to make any database schema changes now and hopefully not touch that next semester, as it'll be much more complicated with live data. My adviser will set up my project and run it on one of his machines, so we're targeting the week before classes start for getting that done.

So I now have a firm deadline for all the back-end stuff I want to get done. Essentially I want to have the data access layer and application layer as done as possible before going live. Hopefully I can really knock this stuff out and be all set for concentrating on the UI next semester. From experience I expect that to be pretty time consuming to get right...

Comments

Post a Comment

Popular posts from this blog

"Does it get easier?" Yes, but Also No...

-
Image
Image by Arek Socha from Pixabay It's complicated... "Does it get easier?" I see some form of this question asked a lot in beginner programming groups. I always struggle with how to answer this honestly and clearly, because the truth is not that simple. In some ways it does get easier, but in other ways it is almost always going to be difficult if you are advancing in your career . If you are a programmer and your job is easy for years on end, the most likely explanation is that you're in the kind of dead-end position that people try to avoid, not the kind of position people dream about when they think of becoming a developer. Most likely you are not getting better at being a dev, not working with new tech or solving new kinds of problems, not being given more responsibility, etc. etc. etc. I've seen some pushback from other newbie programmers on the idea that it could remain difficult past the initial learning stage. Notably I have never once seen somebody who...
Read more

How to Land Your First Dev Job: Develop Yourself, Market Yourself

-
Image
Image by magnetme from Pixabay In the coding and tech groups I'm in, I see the same question asked over and over by folks who are just learning to code, finishing up a bootcamp, degree, or other training program, or who have been looking for that first job for awhile and not having any luck: "what do I need to do to get my first dev job?" There's a whole ton of info out there on this topic, but it's scattered all over, so I thought I would gather together the best resources I've come across and share them, along with a bit of context, to try and help everybody struggling with or just plain wondering about this. There are a lot  of things you can do to improve your chances of finding a job and hopefully shorten your job search. They are broadly divided into 2 categories: developing yourself and your skills, and marketing yourself and your skills. Note that you don't need to do everything on this list, nor do you need to do it all at once. This is an "...
Read more

Git. The WHAT and WHY Edition.

-
Image
Lately I've seen a lot of new/aspiring developers talk about difficulties learning git . I was confused at first, because there are approximately a zillion git tutorials out there. But then I started really looking at what people were saying AND what all those tutorials contain. The problem is most tutorials start out with "here are a ton of git commands to memorize", and this is not where people are having problems. People are having problems with "what is git, why should I learn it, and what does it look like to use it in a real-life project?", and those questions are largely not answered in all those millions of tutorials. So at the risk of redundancy, I'm going to attempt to address these questions in Yet Another Article About Git. First, I want to make it clear that if you want to be a programmer, any kind of programmer, you need to know git. You just DO. This is the short version of the answer to "why should I learn it?".  The medium length a...
Read more