I used to work with a guy who had 2 PH.Ds, in Computer Science and Electrical Engineering and over 600 patents but I kid you not the guy could not use the coffee machine. Now it's not like this coffee machine was as easy as a Keurig, it was some $20,000 espresso machine that took a while to figure out but I tried teaching him how to use it a few dozen times and still he couldn't get it right. It got to the point where I thought he was faking it so that others would make it for him so I offered him $500 if he could figure it out. Still nope. So for the remaining 2 years we worked together I made him coffee whenever he wanted, 2-4 times a day, and he bought me lunch everyday. Before I left the company I bought him a Keurig so that when I left he'd still have coffee.

Math: the imaginary unit is i.
Electrical engineering: no, it's j.
C hacker: hands off my loop variables!

Imagine if a structural engineer whose bridge has collapsed and killed several people calls it a feature.

Imagine if that structural engineer made a mistake in the tensile strength of this or that type of bolt and shoved it under the rug as "won't fix".

Imagine that it's you who's relying on that bridge to commute every day. Would you use it, knowing that its QA might not have been very rigorous and could fail at any point in time?

Seriously, you developers have all kinds of fancy stuff like Continuous Integration, Agile development, pipelines, unit testing and some more buzzwords. So why is it that the bridges don't collapse, yet new critical security vulnerabilities caused by bad design, unfixed bugs etc appear every day?

Your actions have consequences. Maybe not for yourself but likely it will have on someone else who's relying on your software. And good QA instead of that whole stupid "move fast and break things" is imperative.

Software developers call themselves the same engineers as the structural engineer and the electrical engineer whose mistakes can kill people. I can't help but be utterly disappointed with the status quo in software development. Don't you carry the title of the engineer with pride? The pride that comes from the responsibility that your application creates?

I wish I'd taken the blue pill. I didn't want to know that software "engineering" was this bad, this insanity-inducing.

But more than anything, it surprises me that the world that relies so much on software hasn't collapsed in some incredible way yet, despite the quality of what's driving it.

*me switching from computer science to electrical engineering for masters*

ceee:

I worked at a startup. They wanted to "save" money. So they hired a relative of "Fred" named "Bubba". Bubba made a custom website. Like hand built gifs and who knows how hand crafted html. It was fine for a time. Then somebody was wondering why nobody was calling us at the company. No customers. Another relative named "George" (who was actually a business major) looked at the website. It had been hacked and replaced with Jedis fighting Sith Lords. Me and another engineer named "Zeus" said "fuck this shit" and said "we are redoing this shit".

So I logged into godaddy (I know, shitty) and installed Wordpress (kinda shitty). I proceeded to turn wordpress into a half decent page. Wiped out the shit that was there, reused images as it made sense. Created more images. Reduced images to 80% quality to take loading size from 10MB to <1MB. Then I also proceeded to do SEO work and get the website listed properly within about a month. Customers started calling all the time. I had a simple contact form that barely gets any shit on it due to captcha. The was 5 years ago. I left 3 years ago (still help them on weekends) and nobody has done shit with the website. They are still getting calls and it hasn't been hacked.

We don't talk to Bubba. He didn't know what the fuck he was doing. I wonder if he still does websites for his relatives. I honestly had no clue what I was doing, but my take on the approach was easier to maintain and even George and Zeus and the new manager "Ralph" can maintain it, kinda. Went from shitty static website to full on dynamic and interactive. Yeah, I know, "dynamic". But the manager was happy.

Sometimes you just do what you gotta do in addition to doing all the electrical and software engineering for a company.

When a Coursera course is way better than the one offered by your university…
A university student's rant...

I study Electrical and Computer Engineering and during the first semester of the second year I selected an optional course: Web Programming. It was believed among students that the course would be really easy, and it was. All the student had to do was build a very simple website using HTML, CSS and a few line of JS. A website containing three or four pages all of which had to be validated using a markup validation service.

Yeah, sure, I passed the course just like everyone else who bothered enough to spend an hour or two working on the project. Oh, I almost forgot! We had an one-hour workshop on Dreamweaver!
So, by that point, everybody was a front-end developer, right?!

That happened over three years ago, and because of that course web-development didn’t impress me…

Thankfully, the last few months I’ve became interested in Web Development, and I’ve been reading some articles, spending time on smashing magazine, making some progress on FreeCodeCamp and taking relevant courses on Coursera!
In fact, a few days ago I completed the Coursera course “HTML, CSS and Javascript for Web Developers”.
Oh boy, the things I didn’t know that I didn’t know…

<sarcasm>Did you know there was a term called “responsive design” and that there are frameworks like bootstrap?</sarcasm>
Well, I d i d n ’ t k n o w ! ! ! (even though I had taken the university’s course).

I understand that bootstrap was introduced in 2011 and I took the university course in late 2012, but by that time, bootstrap was quite popular and also there were other frameworks available before bootstrap that could have been included in the course! (even today, there is no reference in responsive design in the university’s course).
In just five weeks the coursera course managed to teach me more, in a more organized and meaningful way than my university’s course in a whole semester!

When I started the coursera course I shared it with a friend of mine. His response: “yeah, sure, but web development is pretty easy… I didn’t spend much time to complete that project three years ago!”

That course three years ago gave birth to misconceptions in students' minds that web development is easy! Yeah, sure, it can be easy to built a simple, non responsive, non interactive website! But that's not how the world works nowadays , right?!

A few months ago, in the early days of August, I attended Flock, the Fedora community conference. During a break I spent some time speaking with a Red Hat employee about student internships. He told me, and I paraphrase: “We know that students don’t have a solid background and that they haven’t learned in the university what we need them to!”

Currently I’m planning to apply for a front-end developer internship position here in Greece.
Yesterday I wrote my CV, added university courses relevant to that position and listed coursera courses under independent coursework… While writing those I made these thoughts…

What if that course 3 years ago was as good as the coursera course… all the things I’d know by now…

I bought a raspberry pi a while back, and I have no idea what to do with it. I know nothing about electrical engineering or Python (as I believe that's the language you use to program the pi). Any ideas?

This week Im firing a guy who I hired 5 weeks ago. I cant take it anymore. I setted up a nice environment for him and he keeps taking whole day sometimes two or three to do a 2 hour task. He came from electrical engineering background and never had a software dev job. As a person hes more creative type not logical based type. I dont have nor patience nor resources nor time to teach him basics that be could google but simply doesnt have the mindset to do. Sorry bill gates not everyone can learn how to code, or at least not everyone should.

Advice to other people hiring new hires: test the shit out of them before hiring, dont hire from gut. This guy was giving out a nerd vibe, but the only nerd thing that he has is nerdy puns, other than that as a software dev he know less than I did when I was 12 years old.

This is my zen. Building and designing electrical engineering stuff.

So I met this Professor in my campus recently.. This life-changing conversation followed :
Prof: What are you doing on your laptop?
Me: Sir, I am practicing some coding problems.
Prof : Coding problems? What's your branch?
Me: Electrical Engineering.
Prof: You aren't expected to code. And you aren't taught much coding in your coursework too.
Me : Sir, I take it as a passion and I did learn coding all by myself.
Prof : Rubbish. Learning coding by yourself is similar to saying that you don't require a Prof. to teach you. Just focus on your subjects and stop wasting your time.
Me :Good afternoon, sir. You're right, I did waste my time here.
*Grabs laptop and leaves,hoping he won't be taking any lectures in my next sem. *

After a long time just reading your posts, here's my first post:

Just for clarification: I'm studying electrical engineering in Germany. During your time at university, you have to work half a year as a intern to get some practical experience. So I'm in a position where I mainly have to say "yes" to work that is given to me. Also I'm working with a lot of PLC programmers, so I'm nearly the only one who programs non-PLC stuff at the department.

But now it's time for my rant (and also my most satisfying optimization ever). In the job interview for the internship, my task at the company was described as C# programmer. I only programmed C and Python before, but C# looked interesting and so I learned C# from ground up in the summer before the internship. I quite liked it and I was really happy on my first day of work. Then I was greeted with this message: "I know you are hired as C# programmer, but could you please look into this VBA program, it takes 55 seconds until it finishes its task and that's to slow". So I (midly angry because I had to do VBA and not C#) started the program and it was really horribly slow (it just created a table with certain contents from a very big imported symbol file). I then opened up the source code and immideately saw bad code. The guy who wrote it basically just clicked on the macro recording button and used the recorded mouse clicks in the source code. The code was like: Click on cell A1 -> copy cell A1 -> move to sheet XY -> click on cell A2 -> paste copied stuff and so on... I never 'programmed' in VBA before, so I used my knowledge of 'real' programming languages to do this task. After using some arrays and for-loops, which did not iterate over all the 1.000.000 unused cells after the last used one, the program took only 3 seconds after it finished the new table! Everybody was quite impressed, which led to much more VBA optimization... That was clearly not my goal haha :)

RANT TIME!

Sorry guys, I know this is devRant and probably not a place to post this but am fucking burning with fury and fatigue! I should probably develop elecRant and post it there instead.

I FUCKING HATE POWER ELECTRONICS!!

I am in my final year of electrical engineering and I can fucking say with confidence that power electronics is the most fucked up unit I have seen in my life. A whole load of useless math from simple RLC circuits just to make students' lives miserable. For those who might not know, power electronics is some unit that involves use of solid state electronics(transistors, diodes etc) for power applications(switching mostly). Basically things like inverters and converters. UPS systems are an example of their applications.
Now don't be fooled by how that sounds cool and so smart, this shit is fucked up. These circuits in the attached picture might just seem like simple RLC networks with some BJTs, but they are devils in their own right. They fucking need some advanced unnecessary calculus and Fourier analysis to even calculate the simplest output current!! Worst still, some of these motherfuckers have more than 1 mode of operation,needing one to analyze some fucking 100+ waveforms. I fucking hate this shiit! I hate it!
You might say that i am just being lazy and don't want to study. Let me tell you something, FUCK YOU TOO!!

Saw some cheapie little radio in the dollar store, bought 2 of them for reverse engineering. Powered it from my lab bench power supply as usual, and tested whether it actually works before doing anything else.. then I noticed that the tunes were actually quite catchy, so I just ended up listening.

Then I started to notice that the audio wire I was using (the one I've spent a couple of days building earlier) had intermittent audio issues where the right driver would drop out when the wire was held in certain positions. Oscilloscope probing showed that there was some sort of disconnect, with only the 50Hz noise from the power lines showing up. Opened up the connector and noticed that the ground wire had detached. An 28AWG electrical wire that was inside a jack that was meant for stress relief! Yet the copper strands must've detached one by one regardless. What do I need then, huh?! 18AWG which wouldn't even fit on the connector, only to see the strands in that eventually detach as well?! You know what, let's go fancy.. 1AWG which is meant for extremely high current applications!!

At that point I was literally shouting "FUCK!!! Why does this shit always happen to me?!! ONE FUCKING PROJECT THAT FINISHED SUCCESSFULLY, YET STILL BROKE?!!!! WHY!!!!!!"

Clearly I need some fresh air to cool down. On my way to the fast food restaurant to get some Bicky burgers. More shit, humans. One stupid driver who slowed down on me, which of all things I hate the most. GO FASTER ALREADY YOU SLOWFUCK, AND GET THE FUCK OUT OF MY SIGHT!!! Next a pedestrian with a dog.. I swear motherfucker, if that dog comes anywhere near me I'll personally turn it into fucking fricassee.

Ah and then comes the killer.. in this stupid fucking summer, all that's needed to fix any issue is a fucking stupid DESPACITO, right?! More like DeSPASTICo!! FUCK!!!!

.. Back home, rather tired. So essentially a wire that was specifically built to have high endurance broke on me. Back to Bluetooth I guess.

God knows how many morons try to brag to me on how they know hardware programming because they own an Arduino, whenever I say I study Electrical Engineering.

!rant
I can never get over this 😥

We were taught 5-6 subjects of electrical or mechanical engineering in out freshman year 😃 and our course is called "computer science and engineering".
We had ONE subject in the whole fucking year that was related to the course,called "introduction to computer"!!!!
The second semester of the freshman year had no subject remotely close to computers, but yeah we learnt about thermodynamics and beams and Trusses and motors and welding 😒.
They should have also told us what we are supposed to do with that knowledge 😒.

What's the point!!!!
Will is make us a mechanical engineer 😒?
Also have you forgotten we are here to learn about computers and not about the tension in the rope of the pulley 😒?
Also we have no subjects,in the 4 year course about actual development 😃 not even old school web development.
Fucking hate this shit

How many are into electrical engineering as a hobby? It looks like a really fun hobby I wouldn't mind picking up.

"What's your degree in?"

Electrical Engineering.

"So, you do coal stations and stuff?"

Nope. I look for powergrids to optimise with the help of Neural Networks.

It's rant time!

So, as a broke electrical engineering student, I got this job in a local company. They used JSF and my skills in java were, at the very least, small (former PHP developer). But as a self taught developer this didn't stopped me and I went full on java learning (very bad year for my EE studies).

I became the 'guy in charge' for several of their projects (yeah, they did exploited broke students, I realized this far too late). I was very proud of myself, I worked hard, showed my true value, and they became impressed.

One nice thursday night, my "handler" emailed me with a urgent request. They needed an entire jsf application done by monday and the requirements were fairly complex.

Oh boy, I had a total of 10h of sleep from thursday to monday. I didn't even slept before going to my monday class, but I delivered the system. Got an pat in the back... "you're awesome"... I was happy.

6 months later: I received an email asking to fix a bug in the system. No problem with that. Oddly, this bug was a MAJOR bug. There's no way the system worked properly for six months with it. I fixed it in no time and commited the changes.

Turns out that this was the first time the system was going to be deployed. They made me go in an insane weekend dev project, and didn't even used the system for SIX MONTHS!!! I started to work my way out the company after this, aiming to open my own software company.

I still remember some other rants from the time I worked there. But these are for later.

Nice week for you all, may the sprint go gently and the clients be kind.

It grinds my gears to no end as to how insanely BAD most Electrical engineering software is. Lets start with Tina. A circuit simulator. A few versions ago it was rather good but now it feel like its built upon more legacy crap than fucking Windows! This causes it to have memory access violations and crashes even when you look at it from an odd angle.
On topic of circuit simulation. LT-Spice! It has less errors than Tina but is impossible to use without being lobotomized first. Who the FUCK decided it was a good idea to reinvent keyboard shortcuts by movin all of them to the F-row at the top of the keyboard. Also there is no option to delete a component. YOU NEED TO USE CUT IN ORDER TO REMOVE IT!
And at last Altium Designer for Layouting and Schematics. Whose license costs 9 grand. No one outside of some companies will buy this because of the price. Altium realized this and made two watered down versions of it. Which dont really get updates anymore. (last one was in 2018) So they essentially made a cash grab from people who cant afford their actual product. There also exist other (and a lot cheaper) products than what Altium offers. The problem is that they dont work well with interoperability. Schematics drawn in one program will look distorted in another or not import at all. And since Altium is the industry standard you got yourself this nice steaming soup of impossible collaboration. Its kinda like Adobe being absolute shit at progressing their software just because they got no competition. Or rather they do but the industry wont switch cause adobe is so engraved into it.

I was gonna be an Electrical Engineer.
It was the last year of highschool, I was offered a job if I learned how to code.
I did. I loved it. Later I went for Systems Engineering instead.
3 years later I don't regret it, but I'm also starting Electrical Engineering in parallel next year.
Wish me luck, but it's ok if I die I guess.

So I'm taking embedded systems subject in my masters course. They have mixed this subject's content with electrical engineering and I'm a computer science graduate. Everything was perfect until I reached to GPIO board.
Wtf is this shit?
Why it has so many holes and what are they for?
What I'm supposed to do with it?
What is ground? Transistor?
Why I'm connecting to two pins only instead of the 4 pins of a button?

Thanks to pi4j i think i will pass the subject!

One inappropriate experience I can think of is during an internship at a multinational company that made networking and electrical components. My mandate was to do an analysis on the electrical performance of the company's products versus the competitors. It took me something close four months to measure, to compile data, do an analysis and create a report.

Then came the time to show the results to the engineering director. Let's say the news were not good, so I figured people should have their hears opened. Anyways, my supervisor and I made a presentation to abstract the main points so the information was not too difficult to process.

10 minutes into the presentation, the director of engineering just fell asleep and was snoring quite loudly. I asked my supervisor "should we wake him up?" and so we did. When he woke up, he asked us to wrap it up and pretty much gave no fucks about the results or the presentation. Nobody really cared about the results after that. Talk about wasted time lol.

Luckily I don't work at this shithole of a company today.

The default USB voltage hould have been specified to 6 instead of 5 volts.

Six (6) volts would allow for longer cables than five (5) volts do, since the spare voltage compensates for the resistance of cables. This is even more crucial for USB hubs. USB hubs are highly dependable upon these days due to laptop vendors dropping the number of USB ports down to two or even one. I am looking at you, Medion.

If several devices are connected to a USB hub, the voltage can quickly drop below 4.5 volts due to the resistance between the USB hub ports and the computer's USB port, causing some devices to restart themselves even if the computer's USB port is not over capacity. If it were over capacity, it would just regulate down its output voltage to prevent overcurrent.

Lithium-ion batteries need at least 4.3 volts arriving at the battery terminals to fully charge, and mobile devices are typically not equipped with a boost converter. Even if they were, they are rather inefficient, meaning they would produce significant heat and waste a power bank's energy. Other USB devices such as flash drives and peripherals might power off below 4.5 volts. However, 6 volts have solid 1.7 volts of margin to 4.3 volts, more than twice the margin of 0.7 volts that 5 volts have. On the way from the power supply to the end device, the voltage has to pass several barriers which weaken it, including the cable, connector endings, and the end device's internals such as the charging controller.

Sure, there are quick charging standards such as by Qualcomm and MediaTek which support elevating voltages to nine (9), twelve (12), and even twenty (20) volts. However, they require support by both the charger and mobile device. If six (6) volts were the default USB voltage, all devices would have been designed to accept this voltage, and longer cables could have been used anywhere. Obviously, all USB devices should be able to run on five volts as well.

Six volts would have been more stable, flexible, and reliable.

I've just started my new career with a job in IT operations and I love it. After my electrical engineering degree I fell into a job as a website manager for a small company, I self taught html and css and I knew from then that I had found a job that didn't feel like a job. I'm​ excited to learn everything I need to know to progress as far as I can go in this industry. In my first few weeks at this new job (where i have my own office!) I've self taught python to create automation scripts for live projects, currently up to my eyeballs trying to figure out how to change the VB code for an excel module.....Then there have been so many other projects and bugs and I love it! Any tips and advice is greatly appreciated!

Whose fucking idea was it to still consider assembly (with C being optional) as the most relevant language in electrical engineering school?
Also teaching like 74HC and Op-Amp IC's are still the most common thing in todays electronis is really grinding my gears!!! Is it still an argument that your 8 NAND gates are essentially the same price as a low cost Microcontroller?
But one can be modified within second and the other you potentially need to redesign the entire board.

So, I joined a hardware company as a software developer few months back. I'm working on a c++ code base with thousands of files and no idea what the code is supposed to do.

I got one overview of what the product is supposed to do, which contains mostly electrical engineering jargon that I have no clue about.

Now my manager wants me fix a bug in this code. I have no clue what the expected behaviour is and no documentation whatsoever, and literally no one in the entire country who understands the code.

Does anyone know good resources to learn Arduino Programming?

I have a basic understanding of C, I am looking for a series (of articles preferably) that walks you through the available libraries and the electrical engineering side of things.

Should I switch from Electrical Engineering to Comp Sci?

I am about to start my second semester at college. I took programming 101 and realized I might like coding more than engineering. All the classes I have taken are inside the Comp Sci. Courses in my university so I would not be losing time if I switch now.
Also I started messing around with Android Studio with some friends and that made me realize how easy comparison it is to make a good portfolio and have sideprojects.
Any insight would be greatly appreciated.

Job review time,
(just a random pick from the a list).
---
"Engineering Lead"
Translation: "Chief Calculator Officer"

"Anyone can design or spec a product, get it manufactured overseas and get it to market. But will it be good? Will people buy it?"
Translation: "We're looking for a miracle"

"Take on a top notch team that is going places in Electronics, R&D and advanced product development."
Translation: "Professional Excel engineer wanted"

"This company is a little-known success story that has been operating for over X years, making mission-critical electronic equipment for use by consumers, professionals, government and industry."
Translation: "Design weapons and tamagotchis."

"Working as part of the Senior Leadership team, you will have charge of the I.P. engine and product development team spinning up new ideas and throwing them out the door."
Translation: "You're success is our success. Your failure is your failure."

"The Role
- Generate New Ideas
- Push for new products
- Drive manufacturing
- Manage a cross disciplinary team that includes Electronics, Software and Mechanical
- Project Manage new projects to completion
- Interact with marketing and sales to drive results"
Translation: "We've never hired one person to be a whole team before but we think it will work."

"On your first day, we expect:
- Strong Leadership experience and skills
- Solid Engineering Fundamentals
- Experience taking new and existing products to market
- Experience with manufacturing high-tech, mission critical equipment
- Commercial Acumen
- Bachelors in Electrical or Electronic Engineering"
Translation: "We expect you know where to hide the drugs already."

"Nice to have:
- Experience with Defense or Medical Systems
- R&D background
- MBA, B. Commerce or similar"
Translation: "By clicking on this job ad your background check is already under way."

"In return:
- A loyal and oustanding team will be there to support you
- Extremely knowledgeable experts to guide you
- Incredibly smart founders to mentor you
- The opportunity to work on a real product
- Extremely generous salary package"
Translation: "Our last dev has removed the Warrant Canary. Can you pleeease put it back?!"

Serverless and death of Programming?!

_TL;DR_
I hate serverless at work, love it at home, what's your advice?
- Is this the way things be from now on, suck it up.
- This will mature soon and Code will be king again.
- Look for legacy code work on big Java monolith or something.
- Do front-end which is not yet ruined.
- Start my own stuff.

_Long Rant_

Once one mechanic told me "I become mechanic to escape electrical engineering, but with modern cars...". I'm having similar feelings about programming now.

_Serverless Won_
All of the sudden everyone is doing Serverless, so I looked into it too, accidentally joined the company that does enterprise scale Serverless mostly.
First of all, I like serverless (AWS Lambda in specific) and what it enables - it makes 100% sense and 100% business sense for 80% of time.

So all is great? Not so much... I love it as independent developer, as it enables me to quickly launch products I would have been hesitant due to effort required before. However I hate it in my work - to be continued bellow...

_I'm fake engineer_
I love programming! I love writing code. I'm not really an engineer in the sense that I don't like hustle with tools and spending days fixing obscure environment issues, I rather strive for clean environment where there's nothing between me and code. Of course world is not perfect and I had to tolerate some amounts of hustle like Java and it's application servers, JVM issues, tools, environments... JS tools (although pain is not even close to Java), then it was Docker-ization abuse everywhere, but along the way it was more or less programming at the center. Code was the king, devOps and business skills become very important to developers but still second to code. Distinction here is not that I can't or don't do engineering, its that it requires effort, while coding is just natural thing that I can do with zero motivation.

_Programming is Dead?!_
Why I hate Serverless at work? Because it's a mess - I had a glimpse of this mess with microservices, but this is way worse...

On business/social level:
- First of all developers will be operations now and it's uphill battle to push for separation on business level and also infrastructure specifics are harder to isolate. I liked previous dev-devops collaboration before - everyone doing the thing that are better at.
- Devs now have to be good at code, devOps and business in many organisations.
- Shift of power balance - Code is no longer the king among developers and I'm seeing it now. Code quality drops, junior devs have too hard of the time to learn proper coding practices while AWS/Terraform/... is the main productivity factors. E.g. same code guru on code reviews in old days - respectable performer and source of Truth, now - rambling looser who couldn't get his lambda configured properly.

On not enjoying work:
- Lets start with fact - Code, Terraform, AWS, Business mess - you have to deal with all of it and with close to equal % amount of time now, I want to code mostly, at least 50% of time.
- Everything is in the air ("cloud computing" after all) - gone are the days of starting application and seeing results. Everything holds on assumptions that will only be tested in actual environment. Zero feedback loop - I assume I get this request/SQS message/..., I assume I have configured all the things correctly in sea of Terraform configs and modules from other repos - SQS queues, environment variables... I assume I taken in consideration tens of different terraform configurations of other lambdas/things that might be affected...

It's a such a pleasure now, after the work to open my code editor and work on my personal React.js app...

!rant

I find IT to be an amazing field. There are so many parts to it that take tremendous dedication to fully understand, yet, each part works together.

Teams of people dedicated their entire life to software development, which would be impossible if teams of people did not dedicated their entire life to the development of operating systems. That would be impossible if teams of people did not dedicated their entire life to integrating hardware and software. That again would be impossible if teams of people did not dedicated their entire life to electrical engineering.

I know I missed tons of subfields that link everything together, but just the massive amount of dedication and teamwork to make something as simple as a console application work properly is amazing. I wish I could understand it all and I hope everything will always be as easily accessible my entire life as it is now.

Work hard at improving my skills in embedded software and electrical engineering for sure!

Since it caught my interest half a year ago, I've read several books and articles on the topic, but never got to get my hands on the actual thing.

This will definitely be the year where I'll go nuts and learn all I can to prepare for my next internship, which I really want to be related to embedded software!

Some user profiles I thought were worth stealing for a post:

PonySlaystation
"Full Stack Software Engineer, Electrical Engineering Student driven by OCD & Club Mate."

'club mate' read: probably white powder and ritalin. I heard he once dismembered a horse and put the bloody head in a rivals bed.

uyouthe
"Russian assassin leader, Apple fanboy. Tabs ftw"

Comrade, apple is bushwazee capitalist filth. Onlytrue comrades use windows, because the upgrade is free.

Root
"Magical processor fairy; part-time misanthropic bane of idiots. 🧚‍♀️🏹 Ergo sum miseriae"

Do you sprinkle magical processor fairy dust in each new generation of chips to increase their
clock rate?

When I have started working as engineer, coworkers addressed to me as a programmer or software developer. It was irritating since I am an electrical engineering and those days I didn't have much respect for computer science. Nowadays I know how hard is this field, since I have to define and code my soft, and I am proud if someone call me software developer or programmer

Four steps of professional development:
1. Simple and bad
2. Complicated and bad
3. Complicated and good
4. Simple and good

At CSS and frontend in general, I'm easy four, straight up. At architecture, I'm perhaps two in devops/docker/kubernetes/other crap and three at DB design. At electrical engineering and embedded stuff, I'm 1, no questions asked.

What are your rankings?

1) A widely used compressing algorithm as my very own invention.

2) Master electrical engineering

3) An universal OS Kernel as my own invention. I will declare war on Linux and Windows

1. Say something about autistic traits in front of your boss. Mention many developers benefit from those traits in their engineering work.
2. Boss rejects this audibly saying he is not in fact autistic.
3. Pretend to ignore social cues when interacting near boss. Such as interrupting conversations impolitely. Boss ignores this and doesn't mention this.
4. Later hear boss saying he might have some autistic traits that helps him in his work (he is software developer and electrical engineer, and is very good at this).
5. Profit from being an asshole or autistic? Am I ignoring cues because I just don't give a fuck anymore?

Is it weird that I'm doing Electrical and Electronic Engineering but I HATE it and love programming? I know I should find a balance between the two but I just can't seem to. The worst part is that the syllabus hasn't been updated for eons so we are learning about outdated technologies. Ooh, and you can't declare majors until like the final year, I think. I could quit but it would break my parents' hearts, and we are not rich enough to afford a self-sponsored CS course. The worst part is that I'm not even a good programmer, I'm trying so hard to balance the two that I end up not being good at any.

Any one here have a degree in Electrical Engineering or Electronics Engineering? I'm thinking about going back to school, but I'm not sure it's worth the money since I live in the US. (cries in over-expensive education costs)

I do a lot infrastructure work and some super basic programming/scripting but I think I really want to get into hardware maybe zone in on either RF or take a stab at amps/effects pedals for guitar and bass.

as an aside, I'm not trying to go back to school for job or career related reasons, I just want to noodle with stuff and maybe create my own circuitry for stuff.

Any recommendations for introductory books on electrical engineering? I'm looking for something that goes into detail on the basics: tension, current, resistance, inductance, capacitance, etc. I have very little knowledge on the subject (I know what the basic components do and that's it) and I found myself struggling a bit with the most basic concept: voltage.

I grabbed my multimeter, a few resistors and a battery and played around a bit. For some reason it doesn't really "click" why on a 5v circuit with 3 2.2k ohm resistors (I think) the voltage around each resistor was like ~1.3 volts or something, while on a circuit with 2 resistors the voltage accross each one was ~2.3 something volts (I don't remember exact values). Like, I know that voltage is a difference in potential, but I still don't get it and idk what I'm missing. Why is the difference in potential accross a resistor different if the circuit has 2 resistors in series instead of 3. It kinda makes sense in my head but at the same time it doesn't.

In short, I want to know the "why" stuff works the way it does, not just the "how".

Also, if the book covers common practices, components, and circuits that'd be very helpful. I want to learn how to build well-designed, reliable and safe circuits.

Electrician.
I went to a technical highschool and was gonna be an electrical engineer.
In fact, I'm starting Electrical Engineering next year.
But I'm not gonna be an electrician anymore.
I'm more powerful now.

tl;dr
that moment was a full semester

full
I was an Electrical Engineering major taking a Data Structures class and for the first time, I understood the title computer SCIENCE. In EE, you just blueprint all day long, but you never build anything. In CS you build and blueprint at the same time.

Which one of these is your dream university?

Also let me know which one of these is good for pursuing Ms in EE consider CMU and UIUC as well

Question for the electrically minded.

I have a laptop with a 19v input.

I have a portable UPC with 2 voltage options in the range of this, I can undervolt at 16v (the laptop battery voltage) which works with a small firmware correction to ignore a board sensor, the other option is to slightly overvolt to 19.5v which I assume the laptop could handle through its input regulation.

Can anyone confirm if a .5v variance at charger is within tolerance? It would be an overvolt of 2.5%

- Finish "Introduction to algorithms"
- Learn some genetic algorithms
- Get my hands dirty on reinforcement learning
- Learn more about data streaming application (My currently app is still using plain stupid REST to transport image). I don't know, maybe Kafka and RabbitMQ.
- Learn to implement some distributed system prototypes to get fitter at this topic. There must be more than REST for communicating between components.
- Implementing a searching module for my app with elastic search.
- Employ redis at sometime for background tasks.
- Get my handy dirty on some operating system concepts (Interprocess Communication, I am looking at you)
- Take a look at Assembly (I dont want to do much with Assembly, maybe just want to implement one or two programs to know how things work)
- Learn a bit of parallel computing with CUDA to know what the hell Tensorflow is doing with my graphic card.
- Maybe finishing my first research paper
- Pass my electrical engineering exam (I suck at EE)

Hey I’m majoring computer engineering in one of the best universities in Turkey. But we take a lot of electrical and electronical courses. Topics are like introduction to electronics ( pn junctions , bjts, mosfets etc), electrical circuits ( mesh analysis, inductors, small signal analysis etc) . And were solving real hard problems. How is these stuff gonna relate to my software developer side? I can’t see the connection and benefits of learning the page long formulas about drain currents. What do you think about them?

Am I the only one who want to learn programming and can't stop overreading about it and other connected stuff?
I feel I'm in deep darkness with my learning. I'm still writing those sample codes from books/video courses and can't motivate myself to come up with a piece of software to write myself.
It's some kind of loop which I can't break and move on.
I quit my electrical engineering studies after two years, to start IT studies, because I felt IT stuff is something I want to do rest of my life. Now, after first semester, I feel I'm in the same place I was before starting IT studies...
I'm lost devRant... Any ideas for helping me changing my life?

I would really like to get into electrical engineering and microcontrollers, but I dont have any (real) experience with circuits and stuff.
Can anyone recommend some books, starter kits, good microcontrollers or youtube channels?😄

For a while now I've wanted to make a blog about engineering and discovering different types of engineering (software development, electrical, mechanical, etc). In the blog I'd like to write about journey discovering what kind of engineering I wanted to be, how I got here, and fun projects you can do to see what different types of engineering fields are like. Long story short I want one of those projects to be my process making the blog they're actually reading it on and I have no idea where to start with web dev. Can I get pointers (puns) to resources or frameworks that would be good for beginners?

Need advice:

So this recruiter from AWS reached out to me for a SDE job. I said yes I’m interested and scheduled an interview. She didn’t show up. I politely said would you like to schedule another time 30 min after the empty session was over. She said yes. Then the day after she sends me a message saying they can’t hire students. (I’m 20 yo second year electrical engineering student but I have decent dev experience ~3-4 years) I tell her I’m not planning on continuing with my 3rd year next fall. She says no I’m hiring from the “industry only”. And I try to tell her I’ve never had an internship before and all of this work experience is all by myself and not university related….she stopped responding…..what am I supposed to do? It’s not the first time that this has happened. They see “graduating 2024” they immediately bounce. I tried hiding what year my university education starts/ends….didn’t work…