IME, as someone who leveled up from jr to eventually sr in the same org over a 10yr period, the best advice I can give is be confident in your skills and be willing to take calculated risks.
Teams are always chasing deadlines and resolving unforeseen issues as they arise. The go-getter willing to volunteer to fix a problem that isn't already on their plate gets noticed.
You won't be assigned 'save the day' type work outright as a jr, but the team will find itself in a tight spot, and you need to volunteer to go above and beyond to help fix XYZ even though it's outside your domain.
If you succeed, you have everything to gain. Fail? You're the jr, at least you gave it the old college try while chipping away at your key tasks.
> Most of them are quality wise a notch (or two) above what is shown in the article, but typically do not have as much range because of the more practical nature of their design
Then they are not doing "this".
I chose to use the word "hodgepodge" to show the recklessness of this design. Repurposing an assortment of used rechargeable lithium cells is not safe.
I really hope people don't start doing this on their own.
Although I'd expect a lot of first responders now have equipment to handle a lithium fire, will the DIY'er in their own garage?
The design of the charging circuit for lithium cells is not as straight forward as NiMH, NiCAD or lead-acid. Load balancing is required. Using a hodgepodge of old cells only makes it more dangerous.
Not at all surprised the demise of the road test was an electrical fault while some cells still had a charge while others were possibly deep-discharged.
Fortunately, these become apparent in the workplace and filter out in the first few years.
Any major with promise of wealth will have those who will resort to ill means to get ahead in the system. Again, fortunately, many are weeded out in later stages.
Quite a few negative reactions regarding the decision to go back to coaching in retirement. I think change has to start at the coaching level, as boycotting the sport will do little to change the status quo, especially in the immediate.
A few thoughts -
In my own experience in playing contact sports (lacrosse, not football), it's a trained behavior to shake off injuries, avoid trainers, and otherwise ignore your body's warnings of potential harm. This is taught by the coach [or worse, parents]. The encouragement to push yourself beyond natural limits only increases as you progress to the collegiate and professional levels.
The unfortunate effects of competition are that coaches skirt a dangerous line of balancing the star player[s] safety and winning the game, and this behavior is clear to the players lower in the depth chart who wish to become the next star.
Some of the more disturbing things openly shared were how to pass the concussion protocol, that coach will let you take off a week of practice after a hard head hit so don't go to the trainers, and to shake off any and all injuries as you will be rewarded for being tough. I, and any number of my ex-teammates, agree we experienced what are now known as "minor concussions" constantly throughout our season. Only major concussions would go reported. Being able to walk off the field typically meant you had only a minor injury, and could go back in once getting some wind.
The fact that so many are injured during practice goes to show, it's coming from the coach's inaction and not just during the heat of the game.
Under this light, I think Finley is taking a proactive approach to change by inserting himself on the front lines.
The list of 4 items is excellent. Under no circumstances should you act in an insubordinate manner until you've exercised other channels of communication. Acting before things get too far is the easiest remedy.
I'd recommend the following order of operations:
Convey concern over associated risk to your immediate manager. Verbally first during the meeting, switch to written (email, a paper trail of opposition) if no action is taken.
When documenting the paper trail, simply reference meetings which you voiced opposition. Your notepads should also be able to back up the talking point you're referencing.
Being asked to briefly switch hours or work late is often listed in your job description so stopping suddenly at 5p can be considered insubordinate. Time should be compensated in a time off or paid OT arrangement promptly. If your verbal requests go without action, again, switch to email.
Simply documenting the events as they occur makes it easy for when you need to go above your immediate supervisor ( more senior manager, corporate hq, department of labor) for help.
Key is to be polite in all interactions. Innocent mistakes happen. Managers are under deadlines too. Paper trial should be maintained regardless of action or inaction.
> In my opinion (and I welcome disagreement and debate) engineers have an obligation to say 'no' to wiring unethical code.
And, IMO, yours is absolutely the correct one.
As engineers, we are in a unique position to understand the intricacies and associated risk to any one of our functional requirements we satisfy. True, we are under marching orders from a PM who may (or may not) have provided adequate backstory to understand the goals of the company, but it's our duty to express any concern of risk it may present to the company or society.
When verbal warnings don't work, go ahead and put it in writing.
In the US, part of my engineering curriculum included courses on engineering ethics case studies to drive this point home.
I've written exactly 2 of these letters in my 10yr professional career. On both, the PM sharply changed course, demonstrating their knowledge of failure of the ethical litmus. Putting written responsibility upon them to act encouraged further discussion and ultimately a better resolution for all.
I meant what I said. I believe a lot of researchers (in academia) would do it in their spare time, after hours, weekends, etc, even if it wasn't also their means for income. Their hobby and curiosities happen to align with a job that pays living wage.
Money in the bank is not the end goal for everyone. You can work a job to get paid so that one day you don't have to work anymore. Or, you can work a job that pays sufficiently and you'll happily do until your last days of life.
Lastly, most research is on the brink of discovering something. Whether or not there is a life changing impact (or application whatsoever) as a result of that discovery is another argument all together.
My introduction to markup was the Geocities era HTML. I was in 3rd grade or so at the time.
Got access to my dad's Casio digital camera and took pictures of my friends and teachers and then swapped heads and bodies using Kidpix.
In computer lab, I'd set the start page on the few computers with internet to my Geocities page. It was a huge hit and the computer teacher didn't know whether to applaud or punish me for the work.
I got cut off from the 'internet computers' indefinately and played Organ trail everyday instead of doing the typing assignments since I was already proficient.
I think a large part of my comfort with code came from getting rid of the 'curly brace phobia'. I've attributed my comfort reading code regardless of language at an early age to this exposure to HTML markup.
I pace. I do laps around the lab, between buildings and to the nearby beach when my mind gets jammed.
Used to think watching the waves would settle my mind. Being at the beach just makes me want to go surf.
Ive have had quite a few software design problems solve themselves during my 15min commute to work in the morning as well. I never listen to talk radio (NPR) as a result.
Argument against Globalstar is that it is not a true polar to polar real-time solution like Iridium.
Iridium is the only constellation where you will always find a bird overhead anywhere on the globe (with a ground station relay)
Realistically, Iridium has occasional (~5min) signal gaps likely due to the aging constellation (based on my own use cases developing with a roof mounted antenna)
Heavily impacted engineering program at one of the top University of California campuses.
It spoke for the grading structure of the homework and did not apply to all courses.
Exams and projects were graded much more rigorously and there was a similar drop out/fail rate as you describe.
Not all engineering courses required homework for a grade. Often homework was only worth 5%, exams and projects the remainder. However, weekly problem sets easily consumed 10-15hrs per course, 3-4 courses per quarter.
Professors left it to the student to prove their understanding of coursework through exams. I often suspected due to the high rate of plagerism on homework (copying peers or access to solution guides).
Edit: don't get me wrong, I never had free time as a student. Every free moment outside of class was consumed by studying, working, eating or sleeping. I occasionally skipped lectures to buy free time.
It all came down to risk assessment which is a valuable skill to be learned for industry.
Time management I learned in school has paid off tremendously in my career and is something I seek more than a minimum GPA threshold in my interns and Jr. Eng's.
Plenty of engineering students at top universities have jobs (not just internships).
Time management is key.
As someone who hires their own interns and Jr eningeers, it's shocking how few applicants have ANY prior work experience.
I had a 15-20hr/wk internship, and worked retail on weekends.
However, I often turned in homework that only outlined the knowns, unknowns, drew a diagram, listed equations that were applicable, and that was it. 50% credit for 30min of work.
Teams are always chasing deadlines and resolving unforeseen issues as they arise. The go-getter willing to volunteer to fix a problem that isn't already on their plate gets noticed.
You won't be assigned 'save the day' type work outright as a jr, but the team will find itself in a tight spot, and you need to volunteer to go above and beyond to help fix XYZ even though it's outside your domain.
If you succeed, you have everything to gain. Fail? You're the jr, at least you gave it the old college try while chipping away at your key tasks.