AboutI am a great developer because I think very much like a computer. I suppose, by that same token, I am a terrible human being.
Skillshtml, js, react, aurelia, xml, xslt, c, c++, java
Joined devRant on 4/12/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I'm going home!
For the past six months I've been on a contract that has kept me away from my family. On Saturday I will finally be moving back home. I'm elated to be seeing my family again, but I'm scared because I don't have a new job lined up. Wish me luck.1
What are your feelings on committing your .gitignore file to the repo? I argue that you SHOULD commit the .gitignore file because you are much less likely to accidentally commit things you don't want.
My team lead just told me that he doesn't want the .gitignore file in the repo because it's not part of the build.23
0. I love to solve puzzles. It makes me feel smart. While the act of coding isn't itself problem-solving, programming as a whole generally is.
1. Computers are easier to understand than people. A computer will always do what you tell it to do, it just may not be what you INTENDED it to do.
2. I enjoy having a skill that most people find intimidating. It lends mystique to my otherwise boring-sounding life.
We were going through Sprint Planning on Monday. We got through all of the tasks that we knew we had to get done, then we started going through the backlog to see what we could pull forward.
The guy running the meeting (who's not actually a Scrum master, but whatever) get's to a task, reads it aloud, and goes, "That doesn't ring any bells. Brian, it's in your name, it says it's from May, do you know what the status of this is?
Brian reads through it for about 20 seconds before saying, "That date says it's from 2017. I don't think we need it anymore."2
Maybe not worst, but most frustrating. One of the systems I helped maintain at my first job had a few different bugs that caused bad data in the database. The "solution" to the problem was to write SQL queries to directly fix the production data. This would take one member of our team (it rotated weekly) about an hour every day to fix because there were literally dozens of these errors.
All the devs knew that we could identify the root cause and fix it in, probably, 3-4 days tops. Management would never approve the time because it would take longer to fix the root cause than it took to fix the data.
I worked at that company for 7 years. The bug was there when I came on, and it was there when I left.2
This is the first project that I remember. There were probably others before it, but nothing really stands out before this.
My buddy and I got an Independent Study together in high school. Our goal was to write a video game. We harbored no illusions that it was going to be the best game ever or anything, it was supposed to be a project that taught us enough to move on to something else later.
Our chosen tool for this endeavor was Flash 4.0, back before Adobe bought Flash. I don't know why we thought it would be a good idea to do this. I think it was because we could let Flash handle all the graphical stuff and we could focus on the behavioral side.
I don't really remember much about how the project turned out other than we both learned a lot about what not to do.
Luckily, the teacher overseeing our Independent Study felt that the lessons learned were more important than the product, so we got high marks.
After the number of times I have mistyped "git" as "gir", I kind of want an octocat based on Gir from Invader Zim.4
Just about 2 weeks after my new DevDuck came in, my boss told me that everything the external team wrote is shit and is going to be thrown out. Instead, we're going to rewrite the whole thing inside the existing middleware in Java. Luckily for me, I am also pretty comfortable with Java, though it has been about 5 years, and I know a bunch has changed. But I'm confident I can do the work.
I guess I need a new cape for my duck. Or maybe I'll just start a duck family.1
git push origin stupid-long-feature-name
git pull origin develop
*Checks through all changes. No major conflicts. Accepts changes.*
*4 failing tests, none of them in pieces that I touched for my feature.*
*That's funny. QA was loaded from the develop branch, and everything works.*
*Actual data has dates from today. Expected data has dates from a week ago.*
Why are all these expected dates hard-coded‽
tl;dr The external development team committed 4 tests that would only ever pass on the day they were written.5
I recently got hired on as a contractor to help the company take ownership of a vendor's product.
In one of the repositories that was delivered to us, at the root level of the repo is only src/ and .gitignore
Everything else, including package.json, .npmrc, .docerignore, and everything else, is all inside the src/ directory.2