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
-
My first dev job was a paid internship at Oak Ridge National Laboratory. But I wasn't in the computing division with the supercomputer and the 30-foot 18-screen wall display. In a way, I was doing something more exciting. I was in the Hollifield Radioactive Ion Beam Facility.
That meant that I was working next to a radioactive ray gun that they fired at different targets to try and make new kinds of particles. To refine the beam components, there was a tower with the world's highest voltage Van de Graf generator at 25,000 kilovolts. I got training on how to put on a radiation suit, and was told that if I got locked in the wrong room and red lights began to flash, I had about five seconds to run to the far wall and push the E-stop, before I got irradiated and died slowly over the next five weeks.
But, I was reassured, that never happened. Radiation leaks are rare too (that's why we wore dosimeters). More likely, there would be a leak in the generator tower. To explain why that's bad, that tower wasn't filled with normal air. 25,000 kilovolts would punch through that like nothing, arc against the walls, and we'd lose the electric charge. No, instead, the tower was filled to a few atmospheres of pressure with sulfur hexafluoride gas. You know how helium makes your voice go up? This stuff makes your voice go down. It's heavier than air, and it kills you by displacing and starving your lungs of oxygen.
So, while I was happily coding away on PHP, CSS and the Bash shell, making a log book for all the ion gun settings and targets the scientists used in their experiments, I was keeping an ear out for the oxygen alarm. I had a blast!2 -
I try as hard as possible not to be judgemental towards incompetent colleagues, motivating myself with the knowledge that we were all incompetent at some point, and that people need a chance to learn, and that sometimes too much pressure will lead you to believe that they're bad. Or sometimes, people just aren't good at the stuff you want them to be good, and you just need to discover that niche where they will be very useful.
Mostly that goes well.
I've had the incompetent late bloomer who was a family man who started too late to dev, and wasn't really serious. A bit of harsh talk, some soul searching over a few beers, made him into a really valuable asset. Not the brightest rock, but reliable, steady-paced developer who earned his stay.
Then there was the girl who wasn't really good at coding, but saved our team from disaster many times by keeping things into account, and realizing what must be developed or tested at every step.
However, there are exceptions. I've worked with people who have been nothing but a menace, through their incompetence AND attitudes.
The most noteworthy example was an intern that we sought out, by talking to professors to point us to their best students. So we got that intern on board. He seemed strange at first. Kind of perfectionist. Talked serious, with an air of royalty, and always dressed sharply. He really gave the impression that one must be worthy to receive his blessing. The weirdest part was his handshake. It was as if he was touching an iron hand heated to 3000 degrees. It was over before you even knew it. Leaves you kinda offended. Especially when he always took a wet wipe after that and wiped his hands. Am I really that gross?
But that's fiiiine. I mean we're all different and weird in our own ways, right? So he's a germophobe, so fucking what? We just gotta find a way to work together, right?
WRONG.
As soon as he started (and remember, he's a paid intern, who barely knows how to code, and has zero industrial experience), he started questioning my architecture solutions, code implementations, etc. I don't mind discussion and criticism, which is why I welcomed his input. But it seemed like he wasn't willing to accept any arguments, so I started looking for excuses not to talk to him.
Meanwhile, the most productive team member we had, to whom you could just give and describe an idea, with architecture and stuff, well, and you'd see it implemented the next week, with only the most well placed questions asked, started going into fights with this intern for the same reasons I was avoiding him.
.....
And here's the kicker.
Get this:
This intern comes to me (I was the team lead), while that guy is not in the office, and with a straight face, dead serious, starts telling me that that guy was making stupid decisions and being a bad team member because he doesn't ... I quote him almost verbatim... "follow my indications". He said that I had to do something because he refused to work with him together.
I was stunned.
This good for nothing imagined superhuman, who was completely useless and an amazing annoyance to pretty much everyone in the team, came to me, telling me that the most capable and productive developer in the team is bad, because he doesn't follow his orders, and that I had to pick between the 2.
I couldn't believe what I had heard.
I had so much emotion in me right then. I was angry, but at the same time I could barely abstain from laughing.
I just told him calmly that he was wrong, and that I wouldn't mind if he never came back. I didn't see him for 5 years after that.
Anyway, later that week our team went for a dinner + beer, and the stories from all the team members started pouring in. They didn't want to talk him down either, but now that he was gone, it was a weight off, and everybody could tell their story.
What a fucking asshole.
So 5 years after I stumbled on him as he was entering a church. Still an arrogant bitch. Barely exchanged 10 polite words and I continued on my way as he was disinfecting his hands from my filthy handshake.4 -
There are three things in my workflow that I don't like:
1. Feature requests appearing out of thin air.
It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!
2. Not being asked about estimates.
Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).
3. Being the last part of the product development process.
Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.
This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?
I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.6 -
Electric cars are not better for the environment. All petrol cars combined are only responsible for 7.9% of CO2 emissions. If your electric car is charged from a grid that is powered by a coal-burning power station, it contributes nothing to dealing with climate change. It only provides you with the false sense of security, and you can look cool telling your friends that “you know, I drive a Tesla, I’m environmentally conscious, your gas car is bad”.
Electric cars are lame. When I’m out of fuel, I can refuel fully in minutes. With electric car, I’ll have to wait at least five hours. Let’s be realistic, superchargers aren’t common, and will never be.
Gasoline is 46.4 MJ/kg, or 34.2 MJ/l. Li-Ion is 0.36–0.875. Let’s be generous and say it’s 0.9. To match 1 kg of petrol, I would need 51 kilos of batteries.
Average gas tank is 18 gallons, or 68 litres. To match that, my battery must have a weight of 2.5 metric tonnes. Bear in mind, empty battery and full battery has the same weight. Also, bear in mind, batteries perform worse in the winter.
As per energy density and practicality, things don’t get much better than petrol. Liquid hydrogen has higher energy density, but to store it, gas tank has to have very, very thick walls, to withstand the pressure. And, hydrogen is a bitch. It’s extremely dangerous. You can’t smell it until it’s too late. Hydrogen-air mixture will explode if you look at it the wrong way.
All that “electric cars good for climate” hype is merely Elon maintaining his stock bubble.23 -
Go to meetups and talk to people. Give presentations at meetups if you can. Get involved in community projects. Love coding. Use your downtime to study new stuff.
When talking to potential employers be positive and enthusiastic about your technology.
EDIT: Oh, a few more. Don't seem desperate for a job. Without saying anything, potential employers should feel like you have other offers and they're being evaluated by you. Ask questions about their company if you get an interview.
Try to give off an air of being in control and having a number of choices in your carreer (even if you're living off ramen every day).
The pressure should be on companies to hurry up and snap you up before another company does.
Be honest but a little spin won't hurt. -
I now have further proof that Android 9's fancy Battery Management is shit:
The compass on my new (flagship) smartphone uses the air pressure sensor and the air pressure at sea level to display your current elevation. The air pressure at sea level is fetched from the weather app. And of course, the weather app has its battery policies set to auto-managed.
Can you guess what happened? "Weather app could not be found" and an elevation of -17m
Because no one thought the battery manager could decide that the weather app should not be launched by other apps. Has no one thought this through? Good thing I figured out what was happening pretty quickly.2 -
So as a personal project for work I decided to start data logging facility variables, it's something that we might need to pickup at some point in the future so decided to take the initiative since I'm the new guy.
I setup some basic current loop sensors are things like gas line pressures for bulk nitrogen and compressed air but decided to go with a more advanced system for logging the temperature and humidity in the labs. These sensors come with 'software' it's a web site you host internally. Cool so I just need to build a simple web server to run these PoE sensors. No big deal right, it's just an IIS service. Months after ordering Server 2019 though SSC I get 4 activation codes 2 MAK and 2 KMS. I won the lottery now i just have to download the server 2019 retail ISO and... Won't take the keys. Back to purchasing, "oh I can download that for you, what key is yours". Um... I dunno you sent me 4 Can I just get the link, "well you have to have a login". Ok what building are you in I'll drive over with a USB key (hoping there on the same campus), "the download keeps stopping, I'll contact the IT service in your building". a week later I get an install ISO and still no one knows that key is mine. Local IT service suggests it's probably a MAK key since I originally got a quote for a retail copy and we don't run a KMS server on the network I'm using for testing. We'll doesn't windows reject all 4 keys then proceed to register with a non-existent KMS server on the network I'm using for testing. Great so now this server that is supposed to connected to a private network for the sensors and use the second NIC for an internet connection has to be connected to the old network that I'm using for testing because that's where the KMS server seems to be. Ok no big deal the old network has internet except the powers that be want to migrate everything to the new more secure network but I still need to be connected to the KMS server because they sent me the wrong key. So I'm up to three network cards and some of my basic sensors are running on yet another network and I want to migrate the management software to this hardware to have all my data logging in one system. I had to label the Ethernet ports so I could hand over the hardware for certification and security scans.
So at this point I have my system running with a couple sensors setup with static IP's because I haven't had time to setup the DNS for the private network the sensors run on. Local IT goes to install McAfee and can't because it isn't compatible with anything after 1809 or later, I get a message back that " we only support up to 1709" I point out that it's server 2019, "Oh yeah, let me ask about that" a bunch of back and forth ensues and finally Local IT get's a version of McAfee that will install, runs security scan again i get a message back. " There are two high risk issues on your server", my blood pressure is getting high as well. The risks there looking at McAfee versions are out of date and windows Defender is disabled (because of McAfee).
There's a low risk issue as well, something relating to the DNS service I didn't fully setup. I tell local IT just disable it for now, then think we'll heck I'll remote in and do it. Nope can't remote into my server, oh they renamed it well that's lot going to stay that way but whatever oh here's the IP they assigned it, nope cant remote in no privileges. Ok so I run up three flights of stairs to local IT before they leave for the day log into my server yup RDP is enabled, odd but whatever let's delete the DNS role for now, nope you don't have admin privileges. Now I'm really getting displeased, I can;t have admin privileges on the network you want me to use to support the service on a system you can't support and I'm supposed to believe you can migrate the life safety systems you want us to move. I'm using my system to prove that the 2FA system works, at this rate I'm going to have 2FA access to a completely worthless broken system in a few years. good thing I rebuilt the whole server in a VM I'm planning to deploy before I get the official one back. I'm skipping a lot of the ridiculous back and forth conversations because the more I think about it the more irritated I get.1 -
Breezers Pressure Washing: Professional Roof Cleaning Services in Gulf Breeze, FL
Your roof is more than just a protective barrier against the elements—it’s a key feature of your home’s curb appeal and long-term value. Over time, however, roofs can accumulate dirt, algae, moss, and other organic growths, which can compromise the appearance and integrity of your roofing materials. That’s where roof cleaning services come into play.
At Breezers Pressure Washing, we specialize in providing safe and effective roof cleaning services in Gulf Breeze, FL, and surrounding areas. Our experienced team is dedicated to ensuring that your roof remains in top condition, protecting your home and boosting its curb appeal.
Why Roof Cleaning is Essential
A well-maintained roof not only enhances the beauty of your home but also protects it from damage and helps preserve its value. Here are some reasons why roof cleaning is crucial:
1. Improves Curb Appeal
A clean roof significantly enhances the appearance of your home. Over time, roofs can develop stains, algae, mold, and moss growth, which can make your home look older and neglected. Roof cleaning removes these unsightly marks, restoring the beauty of your roof and giving your home a fresh, well-maintained look.
2. Prevents Structural Damage
Algae, moss, and mold can slowly erode the roofing materials, causing them to deteriorate over time. Moss, in particular, can lift shingles, allowing water to seep beneath them and potentially causing leaks and water damage. Roof cleaning removes these harmful growths before they can cause long-term damage, ensuring your roof stays intact and functional.
3. Extends the Lifespan of Your Roof
By regularly cleaning your roof, you help preserve the integrity of the roofing materials. Removing contaminants like moss, algae, and debris reduces the risk of rot and decay, extending the lifespan of your roof and preventing the need for premature repairs or replacements.
4. Increases Energy Efficiency
Dirty roofs can absorb more heat, making your home hotter in the summer and increasing your air conditioning costs. A clean roof, on the other hand, reflects sunlight, keeping your home cooler and potentially lowering your energy bills. By cleaning your roof, you help improve your home’s overall energy efficiency.
5. Prevents Health Hazards
Mold, algae, and other organic growths on your roof can spread spores that may enter your home and cause respiratory issues, particularly for those with allergies or asthma. Regular roof cleaning reduces the risk of these health hazards by removing the source of contamination.
Why Choose Breezers Pressure Washing for Roof Cleaning?
When it comes to roof cleaning in Gulf Breeze, FL, Breezers Pressure Washing is the trusted choice for homeowners. Here’s why:
1. Soft Washing for Safe Cleaning
At Breezers Pressure Washing, we use soft washing techniques for roof cleaning. Soft washing is a low-pressure cleaning method that uses specialized cleaning solutions to break down algae, moss, mold, and dirt. Unlike traditional high-pressure washing, soft washing is gentle on your roofing materials and effectively cleans without causing any damage to shingles or tiles.
2. Experienced Professionals
Our team is composed of experienced professionals who are fully trained in roof cleaning. We understand the unique needs of different types of roofs, including asphalt shingles, tile, metal, and more. We tailor our approach to ensure safe and effective cleaning for every type of roofing material.
3. Eco-Friendly Cleaning Solutions
We are committed to protecting the environment, which is why we use eco-friendly cleaning solutions that are safe for your home, landscaping, and the local ecosystem. Our cleaning products are powerful yet gentle, ensuring your roof gets a thorough cleaning without harming the environment.
4. Comprehensive Roof Cleaning
At Breezers Pressure Washing, we offer a full range of roof cleaning services, including:
Moss and Algae Removal: We use soft washing to remove moss, algae, and lichen that can damage your roof and affect its appearance.
Stain Removal: We target and remove stubborn stains, such as those caused by dirt, tree sap, or bird droppings, restoring the clean look of your roof.
Debris Removal: We remove debris like leaves, twigs, and branches that can trap moisture and contribute to the growth of moss or algae.
5. Affordable, Transparent Pricing
We offer competitive pricing for all our roof cleaning services. At Breezers Pressure Washing, we believe in providing honest, upfront pricing with no hidden fees. Before we begin any work, we’ll provide a free estimate so you know exactly what to expect.
3
Top Tags
Weekly Rant
View