I'm not actually dead (Sprint 8 retrospective, sorta kinda)

-
So clearly I fell off the sprint-wagon. Things got a bit away from me at the start of the semester, and so I just haven't been doing the formal sprint stuff. I've been working on bugs and configuring Tomcat, plus getting the first draft of my paper written. But I need to get organized again in order to finish what needs finishing before I present my project May 3 (only 3 weeks away, ack!), so I'm going to restart with sprinting and all that for the little time I have left. 

So for sprint 8, I did finish all but one task, Fix weird errors when project only has one user (instructor is the only student). For two other tasks, I'm not sure how long it took to finish them because I didn't write it down (the beginning of my slide into not being scrummy): Update the application to handle errors nicely and Change code to use connection pooling. I finished the rest normally: Add columns/tables to database to support task dependency/subtask relationships (1), Add columns to user table to support lockout after failed login attempts (1), Add checks for authorized access to all CRUD operations (2), Wrap create statements and the fetching of the ID in one database transaction to prevent incorrect results (if necessary) (0, 'cause it was in fact unnecessary), Check all error-related redirects to make sure they work properly (1), Add try/catch blocks for parseInt calls and handle errors appropriately (1). Also I had one unplanned task: Remove unused data access and application layer methods (1).

The actual sprint went fine, it was just the time after that when I stopped updating and doing sprint planning and all that. So for the next 3 weeks, I'm all about the scrum again!

As far as stuff I did during the non-sprinting time, I discovered that Tomcat actually has a built-in lockout realm, so I won't be using those columns in the database after all. I implemented that, fixed some bugs, started trying to get jQuery working, finished the first draft of my paper, moved some stuff from the server.xml file into context.xml, and probably a few other things I'm forgetting. So I did actually get stuff done, it just wasn't at all documented. Alas.

I'm not going to do a sprint 8 review, 'cause that meeting was so long ago I can't even remember it.

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