The design makes the site work the same way on both a PC and a mobile device. So it doesn't matter what device you use to view the site, it always looks the same.

When you say it is running slow, do you mean the IDE itself is slow, or running the code is slow? If it is running the code that is slow, is it running on a USB connected physical device or a virtual device?

Virtual devices run a lot slower than physical devices, so try using a physical device if you are not doing that already.

While Xamarin did get purchased by Microsoft and incorporated into Visual Studio, the pre-purchase Xamarin Studio does still exist. It may take some googling to find, but it is still out there.

Don't forget about poor Johnny;Drop Table Students; Smith

I only use LTS releases of Ubuntu. I've been burnt a few times in the past with the dev save point releases (non-LTS). I know people who are always on the latest, I stick with just the stable LTS releases.

I went through this same situation at my former job. Both groups refused to agree with the other group's format and insisted they change their application for the integration communication. There was not overall architect to define the integration message format between the applications, and each team came up with their own format that was never communicated with the other team. And I was the one testing that the integration piece worked and was caught in the middle of the in-fighting. In the end, one of the senior VPs (3 levels about the fighting groups bosses) had to get involved, and had someone not part of either group develop the message format that both groups had to immediately implement. This is what happens when you try to integrate formerly independent applications without having an application suite architect designing how the applications need to talk to each other.

It is one thing for the developer to say "I can not reproduce this issue on my system", but if they do say that, it better be followed immediately by "let's look at your system together". There are plenty of issues that work correctly in the development environment but fail in the test/staging environment. So I agree, saying that by itself is not helpful. But if the developer first tries to reproduce it in their environment and can not, that is useful to know as a starting point. It is taking the next step of looking at where the problem is occurring that that does not get done often enough.

I never did a lot under Java due to not needing it for my job (and the course I took for it didn't meet for half the scheduled time due to the instructor having family health emergencies that caused him to keep cancelling).

I did need to use C# at my former job to create some testing tools, and once I got used to the Visual Studio IDE, I liked it. I am currently learning how to do Selenium under C#.

After that, I do want to refresh my Java skills and learn Selenium under it as well. Will be good to have both on my resume. I don't know which I will actually need once I land a job, could be that I should have learned Selenium under Python :-)

I am the opposite, I need to be listening to a podcast or music to focus on what I am working on. It is personal preference, my former boss could not stand that (he was like you and only wanted silence or general background noise). Since I work on a Windows system, I use winamp (I am so glad that I saved the last installer released).

I went by "if it will take less than hour, finish it now. If it will take more than an hour, leave it for tomorrow. If unsure, leave it for tomorrow". The caveat for this was that half of my team was based in India (I work in the U.S.), so sometimes I had to finish what I was in the middle of because it would be needed by the India half of the team.

If you close new signups to the server, will you be able to still service the existing customers while you are at college? If yes, then that may be the way to go. If no, then it sounds like the only chose is to close the company completely.

"Why the heck did I code it that way?!" was a very common phrase when updating some of my older code. I can see progression in how I code just from knowing how to do it better next time.

Is your undergrad degree in software engineering? If yes, do a few years in a job for it first. Then go to grad school. The real life experience in the job puts a lot of it into perspective. Also expect your grad classes to be more theory than the undergrad classes where you really get your hands dirty. It surprised me when I did my grad degree, I expected to do more coding as a grad student, not less. At least, that was my experience.

It is even worse when your commits and another team member's commits conflict with each other. Or worse: don't work with both in place (each works alone but not together).

@rajilsaj I am using Chrome on a desktop (Windows 10). And before it is asked, I did try reducing the zoom in Chrome, it didn't make any difference. I do software testing for a living, I can't touch anything without finding some bug in it.

Did you do "/bin/rm -rf /"? :p

It is even worse when the deadline is given to you along with the assignment and you have no say on how long the assignment would actually need to be completed.

I can still see part of your desk, it isn't properly cluttered yet.

Edit on local dev PC, run the test on a different PC that you are driving via VNC. And have the program editor open on both PCs so you forget which one has the actual changed code. Had to break myself of the habit of editing on the test PC and only edit on my local dev PC so there was only one place where I was doing the changes.

Look to see who did the check-in before making the accusation on the code change. Been guilty of this in the past. Was heard saying "why the heck did I do that?!"

Design time does pay off in the end. But when you are supposed to get it reviewed, and the only person who can do the review is never available, you can still wind up doing it wrong the first time.

I could not work at my former office without headphones. My boss hated me wearing them, but loved any background noise no matter how distracting it was. I was glad he worked from home most days, but hated the days he was in the office (he sat in the cubical behind mine and would constantly talk softly to get my attention, not even loud enough to be heard over the background noise let alone when I have headphones on so I can concentrate on what I was working on).

The only part of a release that can be done on Friday is the paperwork for it. Signing all the release documentation, putting the final touches on the user manuals, etc. Nothing in code!!

I am always amazed when I see people who work with SQL much more than I do not test out their queries with SELECT first. And look at ALL the results returned, not just the first few. Yes, that last part was learned the hard way by myself when doing an UPDATE (thankfully before I did the commit).

I never got the hang of differentials and integrals. I was great at math until I hit Calculus, it turned out to be my nemesis. I got just enough of a passing grade in those classes so I could continue in the Computer Science department. I have never needed it in the 30 years since I took those courses.

So many games lost to a twitchy pointer finger. Or focus lost when moving the mouse so I can see what I am typing. Happens more often when I am tired or at the PC for too long.

Those developers better be doing some of the testing then. Usually the testers get overwhelmed, especially at the end of the project, and can use the help. Also good for a developer to see things from the testing / entire program side, not just their little unit pieces. And yes, that does fit in with how scrum works, I just see it done that way so little it aggravates me sometimes.

Back in my senior undergrad year (1991-1992), my college required that all CS majors work on a 2 semester real-life project. Yes, it was still a course, but we also had to develop something as in the real world. I feel that gave me an advantage over people from other colleges entering the job market at the same time that I did.

It didn't matter what the project was creating. It didn't matter if it worked at the end of the course or not. What mattered was the team experience in creating the software.

I understand the rant here, and can agree with it. But I also think that senior year should also prepare you for what it will be like once you land your first professional job. While the tools and programming languages have changed over the years, the basic work environment has not. Students should also be prepared for that first job.