Sprint 10 Retrospective

-
This sprint went remarkably well. Being a hermit all weekend helped me to get as much done as I wanted to (and is probably the only way I could have gotten as much done as I wanted to in earlier sprints, but that really, really doesn’t work as a long-term thing unless one wishes to leave sanity behind). There was one item I started on and then realized I needed clarification from my advisor before I could complete it, but I got everything else done. I also didn’t do quite as much studying as I had intended; honestly I really, really don’t want to have to do this wretched studying, so I procrastinated.

Anyway here are the items I did get done:
  • Create outline for presentation.
  • Gather study materials for oral exam.
  • Fix task creation error where error message is sometimes shown though the task was created.
  • Fix blocking tasks page.
  • Fix task editing bug where the task creator can’t edit the title/desc.
  • Study for the oral exam. (sort of, as discussed above)
  • Move the task list on the project page to the top, above the project info.
  • Make subtasks indented on the task page. (although this looks funny so I did ask my professor about it and will change this a bit)
  • Make the subtask and dependent task lists further apart on the task page.
  • Put a link on the task page going back to the project page.
  • Make the default task priority “normal”.
  • ”Task edited” page should return to the task page or at least have the banner and a link to the task page.
The item I did not complete was ”Task created” page should return to the project page or at least have the banner and a link to the project page. because it already returns to the task that was just created; it doesn’t display a vanilla page the way a successfully edited task had done. Anyway I wanted to be sure that was what my advisor meant, so I discussed that with him at the review.

Overall things went really well, and everything seems on track to be ready to go on Friday when I present my project and will do a demo.

Comments

Post a Comment

Popular posts from this blog

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

"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