What are some innovative final year project ideas for an IT/CS student?
Hi,Thanks for A2A!I think, I'm not the right person to answer this .. currently in second year :p but I'll try to answer!If you want to do something innovative try doing some research projects.Choose current evolving branches of Computer Science like Artificial Intelligence, Machine Learning, Cloud Computing and Security, Data Mining, Image Processing, Gesture Controlled Robotics etc . There are lot of research work going on, on AI and ML. Check research papers you'll get some idea.Here are some ML projects!Learning to Recognize Objects in Images.The Learning KeyboardSong genre classification via training on segment chromas and MFCCsIdentification and Compensation for Corrupt Sensor Data in Robotic GraspingExtracting Vocal Sources From Master Audio RecordingsDeep Learning for Wireless Interference Segmentation and PredictionAuthor Identification on TwitterAI ProjectsAutomatic Theorem ProvingProblem Solving by Means of Macro-operators Problem Solving by Constraint SatisfactionA method for collision handling for industrial robotsControlling a Robot Hand in Simulation and RealityLaser feedback control for robotics in aircraft assemblyReal Time Speech Driven Face AnimationThe State of the Art in Distributed Mobile RoboticsIf you want more project ideas refer my Project list : vicky002/1000_ProjectsCurrently, It has more than 400 Projects topics.. we'll keep on adding there and if you like the project click on the star button :p Well if you want some more details on these project topics you can ping me anytime!I hope it helps!Thank You :)
What is the scariest code you have ever seen?
I didn’t actually see this code, but my wife did, many years ago…The national air traffic control system in the U.S. at that time had been programmed many years earlier in a language called JOVIAL. It ran on prototype IBM 360 computers at the 20 regional air traffic control centers that regulated all air traffic in the U.S. The hardware was failing due to age and my wife was on a team writing a proposal for a replacement system, so she had lots of opportunity to learn how the code worked.Two things were particularly scary about the system. First, the code was full of “clever tricks”. One in particular impressed me (not in a good way). These prototype IBM computers, it turns out, had gaps in their physical address space: memory addresses where there was no actual memory. If you tried to access addresses in those gaps, a hardware exception was raised, transferring control to an exception handler address. Well, several loops were actually written to take advantage of this. How? Just before starting a loop to process an array of data, the code stored a new exception handler address, positioned the data array in memory so that it ended just before a gap, and then ran the loop with no termination test. When the loop ran off the end of the array, it wouldn’t process garbage like you’d expect; it would raise the exception and execution would continue with the exception handler, which in this case was the code that the programmer intended to be run after the loop exited. Why was this done? To eliminate the need for a termination test, allowing these loops to run faster! After all, every little bit of execution speed helped.The other scary thing about the code was that the source code and the executing object code were only vaguely related to one another. It turns out that over the years, many bugs were fixed in the code. (No surprise there.) However, these bugs were fixed not in any way that you or I would find sane. The maintenance engineers did not edit the source code, rebuild the system, and then issue a patch that reflected the new source code. Instead, they examined the machine code running on the system, did all their debugging there, and designed a patch based directly on the machine code. The source code wasn’t updated with even so much as a comment.Considering that this was the software that kept airplanes from flying into each other in the skies above the U.S., scary stuff indeed!