Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "robotics engineering"
-
Dev: I'm going to a engineering and robotics seminar this weekend
Manager: Stupid. Waste of time.
Dev: I also got invited to go to a 2 day tech and innovation conference
Manager: Another a stupid waste of time.
Dev: The CEO's son invited me and is paying for it, he said he thought it would be interesting to me.
Manager: ...Well as long as it's not on company time
Dev: It is on company time, I won't have time for tickets
Manager: WHAT!? YOU HAVE TO SAY NO, WE ARE BUSY!! WE CAN'T NOT HAVE YOU FOR 2 DAYS.
Dev: Duely noted you said that and you think the whole idea is stupid. Take it up with him I already RSVP'd yes.
Manager: 😡😡😡😡😡😡7 -
Today I finished my robotics project. I had in my team a total idiot (the one who used the hidden divs, some might remember from another rant). I wanted to share with you the beginning of a ranting adventure.
Me: "you can begin with a simple task. I will send you the obstacle avoidance sensors values from Arduino, and you will send the data for the Arduino motors to dodge the obstacle".
The sensors give 1 if clear, 0 if obstacle is detected.
Below is his code (which I brutally rewrote in front of him).
Now, in the final version of the robot we have something like 9 sensors of the same time to work with.
Imagine what would have happened if we kept him coding. (Guess it: 2^9 statements! :D)
I was not that evil, I tried to give him some chances to prove himself willing to improve. None of them were used rightfully.
I'm so fucking glad we finished. I'm not gonna see him anymore, even if I'd like to be a technical interviewer for hiring just to demolish him.
I'm not always that evil, I promise (?)
Ps. He didn't even have any idea on what JSON is, even if we had already seen it during FIVE YEARS of computer engineering. (And should've known anyway if he had a bit of curiosity for the stuff he "studies")10 -
What you are expected to learn in 3 years:
power electronics,
analogue signal,
digital signal processing,
VDHL development,
VLSI debelopment,
antenna design,
optical communication,
networking,
digital storage,
electromagnetic,
ARM ISA,
x86 ISA,
signal and control system,
robotics,
computer vision,
NLP, data algorithm,
Java, C++, Python,
javascript frameworks,
ASP.NET web development,
cloud computing,
computer security ,
Information coding,
ethical hacking,
statistics,
machine learning,
data mining,
data analysis,
cloud computing,
Matlab,
Android app development,
IOS app development,
Computer architecture,
Computer network,
discrete structure,
3D game development,
operating system,
introduction to DevOps,
how-to -fix- computer,
system administration,
Project of being entrepreneur,
and 24 random unrelated subjects of your choices
This is a major called "computer engineering"4 -
Software engineering is slowly being lowered to a basic skill to please corporations that literally want you to automate your job away. The only fruitful areas of software engineering that I can see being relevant in the next 10 years are those mixed with other hard sciences such as bioinformatics, robotics, bleeding edge statistics and mathematics (AI research), physics, etc. The trend I see right now is that software engineering is being integrated with business-oriented degrees or arts degrees, targeted programs towards beginners offered for free or low prices. There's going to be a higher barrier of entry for the jobs that are actually worth the stress and I'm praying I'll be able to catch the train before it leaves the station.9
-
While in Mec engineering university program I was in a robocup team (small robots playing soccer against an other team of robots using AI).
I designed the mechanical structure of the robots. After 2 years of development (while all those years our goal was to participate in the upcoming international tournament) we realized the software part of the project was mismanaged and really far behind. I couldn't accept that and learned how to code over night. Couldn't let the project I put so much time in die because of someone else.
With the help of others that came from other backgrounds than software, we made it the to tournament and the following two others after this one.
Now my job involves programming more than standard mec engineering. It also pushed me to do a masters in robotics in which I developed my coding skills even more.3 -
My first time doing a pair-programming for uni assignment.
My partner is actually smart (a Mechanical Engineering guy), except when it comes to programming :
1. Don't know how to spell FALSE
2. Don't know how to create array in Matlab
3. Poor variable naming
4. Redundant code everywhere
5. Not using tabs
6. Stealing my idea and spit it again in my face after claiming it as his idea
7. Mansplaining every line of his code like I am a stupid person who never sees a computer before.
He said he has an experience in Matlab, wants to specialize in Robotics and taking several ML classes. What did they teach anyway in class to produce a shitty programmer like him?
Thankfully despite his being an arrogant shitty guy, he still manage to get our code to works.
That's good because if not, then I will happily push his head under water while slowly watching him drown.
🤨6 -
So, my son is in the STEM program at school. They are suppose to use engineering methodologies in their learning process, according to the school. Apparently there is a new engineering process of step 1 try to write code for robot, step 2 build robot, step 3 make CAD design of how you will build the robot, step 4 write requirements for how the robot needs to function, step 5 robot doesn't work right, and step 6 lose robotics competition.
The other thing that is irritating me is they don't require kids to meet deadlines, just whenever you get it done is fine or if you need 10 tries to get it right. This is the second time the whole class has been disqualified from a competition because the teachers can't keep them on task.
I'm starting to really think public schools suck.4 -
I am a web dev but recently I have a growing interest in robotics and computer engineering. Thus I bought a raspberry pi 3, installed raspbian and then kodi (for testing purposes) on it, kodi was a bit laggy, don't know what to do with it now. Will try to it as a home server, just like a digitalocean droplet. Better suggestions?3
-
aagh fuck college subjects. over my last 4 years and 7 sems in college, i must have said this many times : fuck college subjects. But Later i realize that if not anything, they are useful in government/private exams and interviews.
But Human computer Interaction? WHAT THE FUCK IS WRONG WITH THIS SUBJECT???
This has a human in it, a comp in it, and interaction in it: sounds like a cool subject to gain some robotics/ai designing info. But its syllabus, and the info available on the net , is worse than that weird alienoid hentai porn you watched one night( I know you did).
Like, here is a para from the research paper am reading, try to figure out even if its english is correct or not:
============================
Looking back over the history of HCI publications, we can see how our community has broadened intellectually from its original roots in engineering research and, later, cognitive science. The official title of
the central conference in HCI is “Conference on Human Factors in Computing Systems” even though we usually call it “CHI”. Human factors for interaction originated in the desire to evaluate whether pilots
could make error-free use of the increasingly complex control systems of their planes under normal conditions and under conditions of stress. It was, in origin, a-theoretic and entirely pragmatic. The conference and field still reflects these roots not only in its name but also in the occasional use of simple performance metrics.
However, as Grudin (2005) documents, CHI is more dominated by a second wave brought by the cognitive revolution. HCI adopted its own amalgam of cognitive science ideas centrally captured in Card, Moran & Newell (1983), oriented around the idea that human information processing is deeply analogous to computational signal processing, and that the primary computer-human interaction task is enabling communication between the machine and the person. This cognitive-revolution-influenced approach to humans and technology is what we usually think of when we refer to the HCI field, and particularly that represented at the CHI conference. As we will argue below, this central idea has deeply informed the ways our field conceives of design and evaluation.
The value of the space opened up by these two paradigms is undeniable. Yet one consequence of the dominance of these two paradigms is the difficulty of addressing the phenomena that these paradigms mark as marginal.
=============================7 -
So I’m heading off to college soon, any tips for diving into robotics engineering or just college life in general?3