Red Hat and Fedora Leftovers
-
Edge computing: From 30 tons to 30 grams
When the ENIAC computer was introduced in 1946, it was housed in a huge room—1,800 square feet—and weighed 30 tons. It had to be assembled in place, and it wasn't going to be moved. The era of electronic computers had arrived, but only for an elite few. The idea of edge computing was science fiction—unbelievable science fiction at that. My, how things have changed.
Mainframes
The IBM mainframe computers, introduced in 1952, became the standard of computing for corporations and government agencies in the 1960s and 1970s. Those of us old enough can remember, for example, getting their home water bill in the form of a punched card with the words "Do not fold, spindle or mutilate" on it. These mainframe computers moved processing to the corporate headquarters. Sales from cash registers, for example, would be sent to headquarters on punched paper tape where it could be read into the mainframes for reporting.
-
Red Hat Pushes OpenShift to the Network Edge
At the Mobile World Congress, Red Hat today extended its effort to make the Kubernetes-based Red Hat OpenShift platform a foundation for edge computing by extending alliances with NVIDIA and partnerships with Samsung, Airspan, Druid Software and OMRON.
-
Red Hat Donates Kepler Tool for Tracking Power Usage to CNCF
At the Mobile World Congress event today, Red Hat, in collaboration with IBM Research, launched an open source project to capture power usage metrics from Kubernetes clusters.
-
The NeuroFedora Blog: Next Open NeuroFedora meeting: 27 February 1300 UTC
-
Fabio Alessandro Locati: Red Hat Certified Specialist in Containers
Last week, I completed the Red Hat EX188 exam, which allowed me to become Red Hat Certified Specialist in Containers. I think that Red Hat has been able to improve the quality of its exams over time. Newer exams tend to have better explanations of the required tasks. It could also be that this feeling is partially due to my increasing familiarity with those kinds of exercises. This exam is very new; in fact, I believe it was released at the beginning of the year, and this is by far the more user-friendly Red Hat exam I’ve ever done.
-
Essential tips and tricks for your first tech job
First days at work are scary. I still recall many instances where I lay awake at night before my first day at work, having an internal meltdown over what would happen the next day. Starting a new job is uncharted territory for most people. Even if you're a veteran in the industry, there's no denying that there can be a part of you that's a bit terrified of what is to come.
Understandably, a lot is happening. There are new people to meet, new projects and technologies to understand, documentation to read, tutorials to sit through, and endless HR presentations and paperwork to fill out. This can be overwhelming and, coupled with the considerable degree of uncertainty and unknowns you're dealing with, can be quite anxiety-inducing.
Two reasons motivated me to write about this subject. The first one being that back when I was a student, most of the discussion revolved around getting a job in tech, and no one talked about what happened next. How do you excel in your new role? Now that I look back, I think I assumed that the hard part is getting the job, and whatever comes after, I could probably figure out myself.
Similarly, once I started working in the industry, most of the career-related content I came across was about how to go from one senior level to another. No one really talked about what to do in the middle. What about the interns and the junior engineers? How do they navigate their early careers?
After completing three years of full-time professional experience as a software engineer (and a couple of internships before), I reflected on my time. I put together a list of tips and tricks I've employed while settling into a new tech role. I wanted to look beyond just the first couple of months and prioritize helping achieve long-term success.