My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Alex Gupta and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
My name is Ankit. I am a senior in computer science at Worcester State University.
This blog is related to the software testing, I will be posting every week.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.
In the blog written by Alex Naraghi on What I Didn’t Understand as a Junior Programmer, he states, “There is no excuse for not understanding the lines you have written, or you are debugging. There is no shortcut, even if it feels like there is.” It is much better to spend time mastering the entire system and understanding a project’s architecture. Spend the time to use good programming principles and design pattern. However, it’s interesting that what was warned in the article was what I did during the past summer.
I was tasked to develop prototypes for some basic mobile applications for the company. They wanted an application that can search their publications, and retrieve the info. I had some experience in Java and also Android Development, but let’s be frank, after not touch Android for a year, I only had a cursory understanding of what was going on. IDE changed, APIs deprecated, and with that a whole slew of new issue will pop up once coding starts. I was also tasked with learning Swift for IOS development, in which I had no experience in. They gave me some code some other intern wrote in the past, (which was written in Swift 1). Being an intern with not much to lose, of course I confidently said, “Yeah, I can do all of this.”
In the end, I pulled it off. 2 weeks were spent writing an Android application that can search, filter by categories, and use the microphone for speech to text search. The last one my boss was most impressed with, although it was basically a very few lines I read browsing stackoverflow. Swift was the same, 2 weeks of watching Youtube videos and browsing stack, I jury rigged an updated IOS app that allowed searching. My boss praised me, commenting that I gave an intern a month and he made me two apps. It didn’t matter the two apps were designed pretty terribly and running on janky code, but as my boss says as I cautiously brought this up, “hey it works.”
“Now, I believe that even if you fix a bug through fiddling around, it is more than likely you haven’t solved it.” The IOS app, I can only somewhat understand what I did and there were probably numerous issues with it. For that project, it was only a quick and dirty prototype. However, in the future, if I’m working on a huge code base, there is no way I can just fiddle my way around while not understanding the system without serious repercussion on future maintenance. The statement I hear often is, “as long as it works, nothing else matters”. A belief that I often read and now seen permeating through middle and upper level management. Alex Naraghi’s post just reaffirms my belief that in the world of programming, that the statement couldn’t further be from the truth.
Understanding the code and fixing problems as a programmer:
http://blog.alexnaraghi.com/what-i-didnt-understand-as-a-junior-programmer
Further interesting articles I read this week:
Al-Jazeera stealing codes from a web development company:
https://www.scrollytelling.io/al-jazeera.html
Learning Angular2 is excruciating (and JavaScript in general):
https://hackernoon.com/why-learning-angular-2-was-excruciating-d50dc28acc8a#.nb7772a3b
Chrome setting marking all HTTP to be unsecured in the future:
https://www.troyhunt.com/heres-how-broken-todays-web-will-feel-in-chromes-secure-by-default-future/
Knowledge Debt:
http://amir.rachum.com/blog/2016/09/15/knowledge-debt/
From the blog CS@Worcester – Site Title by nealw5 and used with permission of the author. All other rights reserved by the author.