Sprint 5 Review

-

Yesterday I met with my professor for a demo of the pieces I had working; he was satisfied with it. Then we discussed my plans for the next sprint and through to the beginning of next semester. During the next sprint, I intend to get the entire application running again at the very least. I'm also hoping to start on the list of new features (discussed below) that I'd like to explore; my adviser was open to me doing any/all of them, although as he put it they're really for my own personal development/education rather than requirements from him. Of course the entire project is pretty much an exercise in personal development, since I already know how to make working software, but anyway.

My goal with the project is to make an application that's as professional as possible, so I want to include some of the bells and whistles you'd normally expect from a commercial application. This includes things like resetting a forgotten password, locking an account after too many failed login attempts in a certain amount of time (which idea was sparked by this awesome article), having requirements for password strength, etc. I'd also like to make some more database performance/correctness improvements. So hopefully I can do one or two of these items; I haven't yet estimated them or prioritized them, since I brainstormed them over the weekend.

So that's the plan for the next sprint, which will be the last that will end with a demo for my prof since the demo will in fact be during finals week. I'll keep working though. No rest for the wicked and all that.  I will also have 2 weeks off around Christmas/New Year's, and I intend to spend quite a lot of that time working on my project.

I'm hoping to get all the background stuff (security, database performance, etc.) done before the spring semester starts, so in the spring I can concentrate on the UI and on adding a few more pieces of functionality for the end user (basically new data access/servlet/JSP chunks), and of course getting the paper written. And cramming for the oral exam component of my masters presentation, I suppose.

So that's the plan for awhile.

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