Skip to content

Totally Surprised at How Easy it is to Setup Development Environment in Linux

So yeah, this is amazingly easy. I had been holding back from doing this because I figured it would be such a hassle. Then the other day I figured I really needed at least to see if I could put SVN on my laptop. That turned out nice and easy, then I thought to myself tonight, “why not add Jenkins as well”, and boom it’s on and it’s running with no problems at all. I think the next one will be to add a bug tracker, but not tonight. Anyone have a good solution for a bug tracker that will run on my laptop which is basically an LAMP installation, with Subversion, and Jenkins? I really want something that integrates with SVN really well (like when I post a fix in the SVN that the issue status is updated)?

One More Week Without Lessons Learned … Sorry

Hi to anyone who actually visits this site. I’ve got what I think will be a good Lessons Learned in development. The thing is that it’s not ready. I’m trying my best to improve the quality of my Lessons Learned posts, and I really don’t want to post just anything. I want to post something I can be proud of, and in this case the article isn’t quite there yet, and rather post just anything I would rather put it off one more week to see if I can get it up to snuff.

So sorry for another week without Lessons Learned (not that I expect many people read this site anyway), I’m going to aim for next week for what I’m working on.

 

–Jason

Very Likely No Lessons Learned this Week.

Sorry guys, as much as I’ve wanted to keep it regular it seems I’ve failed this week. This is because I am currently conducting training for one of our customers and just haven’t had the time to find a topic this week.

If you have any topics that I should cover in Lessons Learned, then leave them in the comments below.

 

–Jason

Lessons Learned: Talk and Discuss with Your Peers.

LessonsLearned

You are not an island, you do not know everything there is about development. You need to bounce ideas off others who may have other views. You should talk with your peers.

(Continued)

Lessons Learned: Communication is Key!

LessonsLearned

As developers communication is very important. If you are working in a development team, naturally you have to communicate with your team members. Above that we also have to be able to communicate with our management, which can be a minefield at times, as I know so well. Even if you are working for yourself on a project that will make you millions, you still need to communicate with your target demographic (I think that’s the right word). Needless to say communication is key. That being said let’s talk a little bit about communication and what we, as developers, can do better.

(Continued)

Trying To Do the Right Thing When Working on Your Own Project.

Honestly I think that when working on my own projects, I find it extremely hard to actually follow the development process correctly. I just want to throw code at it and move on. I know that this is a bad habit, and I’m doing my best to break it, but man it’s hard.

It is my desire to use my private projects to learn to follow the development process better. The problem for me is that I really hate all the paperwork (feature list, UML diagrams) that it just makes me lose interest. Most of the time if given the chance to draw UML diagrams for my project, or play Minecraft, I will choose to play Minecraft. I wonder if other developers have this problem too, and how they move past it?

 

–Jason

We’re Getting an Introduction into SCRUM!

So I was happy to hear that my department head has scheduled a short introduction class into SCRUM. This is the closest thing we’ve had to further training in the company for a while now. If anyone has any suggestions on some books to read about SCRUM and AGILE then drop them in the comments.

–Jason

Lessons Learned: Ask Good Questions When Looking for Support.

LessonsLearned

When looking for support asking questions is not enough. You must ask good questions to get the answers you want in a timely manner.

(Continued)

Lessons Learned: Dealing with UML Diagram Updates.

Hey a new Lessons Learned. I’m going to try to post something like this every week. This week I’m going to discuss about UML diagrams.

(Continued)

Lessons Learned: Dealing With Large Arrays, Unit Testing, Paper and Pen

I’ve been looking at trying to post here more, and one thing I thought I could discuss what I’ve learned for the week. So here are some Lessons Learned for this week:

(Continued)