Crooks Getting Smarter - I logged into an old email account of mine recently. Saw a spam message from a few years ago. The thing was really good. Official looking return address a...
Personally I had never heard of TortoiseSVN before. It is a client for Apache Subversion source code control. That's where the SVN comes from. It is taking me a while to get familiar with TortoiseSVN. The user interface is presented as an extension to the Windows shell. That is, you right click on thing in Windows Explorer and get TortoiseSVN menus.
Installation of the product is pretty easier. I just went to 64-bit Windows. So I got a 64-bit version of TortoiseSVN installed. Now I just need to figure out the URL of the team's Subversion repository and I should be off to the races.
This certification is the first on my road to becoming a certified ethical hacker. I want to join a project at work. I talked to some guys on that project. Asked them if there were any credentials that were worthwhile to achieve to get ready to work on their project. They said only the certified ethical hacker.
CompTIA will certify you. But your certification runs out after a few years unless you keep it current. There are a lot of ways to earn credit to keep your certification current. At first I thought this was just a scam to let them make more money off you. That may be true. But the techniques to stay current seem like they are worthwhile.
Here are the things you can do after you earn your certification to qualify to renew it when it expires: get another certification, attend a workshop, publish an article, publish a white paper, write blog posts, write a book, attend a webinar, attend a conference, complete a training course, complete a college course, obtain work experience. There are a few more options such as teaching or creating material for a course.
Those all seem like good ideas to stay current in general. I think I should have no problem keeping this certification current perpetually. Just need to log my progress in learning and I should be good to go.
When I first joined my long lasting project, there were over 60 people on it. We were broken down into assorted teams. But if you paid attention, you pretty much would know everyone on the whole project. Might not interact directly with each one. But you would at least know them.
After a while, the project downsized a couple times. The steady state seemed to be 40+ people. Upwards of 45 team members. I still knew just about everyone on the team. Then I branched over to a future project that is to be built. Met a lot of people. Did not spend long on the project. But there were many hands. It did not feel like a unified team. I guess maybe because it wasn't.
Now I am on a huge project. There are 250 to 300 people total. I worked once on a project this big. But I knew almost all the people on that prior huge project. This time I just know my team of 7 or 8. We are very compartmentalized. It is kind of weird. Really focused on our specific task in the system.
The jury is not out whether this localized model is better or not. I will find out. Just an observation.
So I reported to the lead DBA. He gave me a task. I hit the ground running and we figured out a problem that plagued the team for over a month. Win. My new team lead was going on a long vacation. He put me in charge of a database task. I was ready to make some progress.
Turns out I don't have the privileges to do the things I need to do in the development database. There are some other DBAs that handle that. Okay. I did some prep work for testing. Then I scheduled up a meeting with the DBAs in charge. We went nowhere fast. They apparently would run scripts on our behalf. Ok...
I had another developer write up some scripts. The DBA pulled it up onto the UNIX box and he kept getting Korn shell errors. The file was there. Ksh kept complaining that it could not find the file. I left the DBA to figure out the details. Turns out he uploaded the file in the wrong mode. The lines were terminated incorrectly. Doh.
I decided to take a look at the script files. The author put a tar file on the UNIX box. I grabbed a copy and tried to extract the files. He gave me instructions to extra via a tar -cvf. I tried a couple times. Tar kept giving me errors. This seemed like deja vu. Luckily I stepped back and read up on how tar works. Turns out that command was similar to the compression. I needed a tar -xvf. And I was off to the races.
So I started at the beginning. Enrolled in a course called Network+. It turns out that this first course prepares you for a introductory Network+ certification. The more the merrier I guess. There was no traditional textbook for this class. I purchased access to some online TestOut site. Initially I thought that was a rip off. Over $125 for access to a web site?
Turns out the $125 was actually money well spent. The site has detailed simulations for network activities. They simulate office buildings, completed with hardware and Windows operating systems. They even have some Windows Server installations you need to navigate. This is much easier that buying a bunch of hardware and setting up networks in my basement.
The cost of the subscription also gave me a voucher to take a Network Pro certification exam. This is different than the CompTIA Network+ cert. I had not heard of Network Pro before. My instructor says it is more common over in Europe. Okay. The Network Pro emphasizes hands on knowledge of choosing the best hardware and debugging real network problems.
Never heard of it. Apparently it stands for Certified Ethical Hacker. Sounds juicy. When needing training, my first stop is my local community college. I was in luck. They actually have a track that ends up getting you prepared for a CEH. Unfortunately it takes a whopping five classes to get you there.
I went to the department chair and asked what I should do. She referred me to the cyber security guy. He told me to start at the beginning with Network+. That class prepares you to pass the CompTIA Network+ Certification. It is entry level. Should be a breeze.
Nope. To start, the class I signed up for was an accelerated one. That means it only meets for half the semester. It is scheduled for two nights a week, four hours a pop. That's not the hard part. The assignments are brutal. I took some short cuts and got through most chapters for the week in a couple hours. The last one took almost 10 hours.
I heard another guy in the class. He works a full time job like me. He said he did all the work, and the last chapter took 20 hours for him. We read a couple chapters a week. Who has time for this? I can only imagine the regular paced classes are not as bad. There is only one thing to do at this point - power through the material.
There are some good things about the job. I get a captive audience when I speak on a system that I know well. People are very interested when you know what you are talking about.
Here is the downer. The customer wants project management now, not analysis. Doh! If I stay, I will be figuring out releases. Not that I cannot perform such tasks, but do I want to?
This might be my opportunity. Run for the hills and get back to my true love - software development.