Big-Techs Bittersweet Symphony

Quick note: if you’re viewing this via email, come to the site for better viewing. Enjoy!

man waking up and stretching in bed
First thing in morning…I wonder what’s on Scriptingthewhy.com
Photo by Kampus Production, please support by following @pexel.com

Have you ever woken up, walked into the kitchen, put your hand into your toaster, flip it on, and while it was heating up thought to yourself,” This is a good idea, I mean my hand is starting to burn but I’m okay with this”? No, me neither but yet somehow, we complete this same action every day at work.

While “we the happy few” go to work and enjoy it there is a mass amount of people who do not but in either case, the result is the same, we take part in a cycle. Get up, get dressed, grab your bags, head to work, work your standard eighty hours, get your paycheck, pay your bills, complain throughout the process, and repeat.

We complete this cycle for various reasons but whatever those reasons may be, this cycle hides away a question from the forethought of our minds that we should be asking ourselves and searching for an answer. “What would I do if my employer had to let me go?”

In case you were wondering, the reaction to pulling your hand out from the toaster is the thought that you should be aspiring to do something more than your current position. This symbolism hits all too hard.

woman in bed holding smartphone in shock.
We know it’s your day off, but could you still come in and hand over your badge?
Photo by Andrea Piacquadio, please support by following @pexel.com

Heartbreaks and Layoffs

I don’t know how many of you reading this have ever experienced a layoff before, personally, I have not. I mean, I experienced being laid off in a relationship (it was her choice, not mine) but I could imagine the feeling of your heart dropping into your gut, and experience trembling throughout your very existence would be the result.

For those who don’t entirely have a good idea of what a layoff is; in short, the employer may come into a situation where they have to terminate your employment, the reasons can vary from trying to cut costs, lack of work, or funds because of reorganization, or even mergers and acquisitions.

Breaking this down in relationship terms, this is the classic “It’s not you, it’s me” situation. This differs from being fired because, well… being fired is something that happened on your end. So, again, in relationship terms, this is the classic “I’m breaking up with you because we’re just not meant to be” situation.

Breaking hearts aside, if you have been living under a rock, the company Google, is a subsidiary of Alphabet Inc that focuses on various business areas such as advertising, search, platform, and operating systems, and the list goes on, had to perform a massive layoff and people were informed via email, that they were being let go despite their longstanding with Google.

Again, haven’t been laid off before but I could imagine your world becoming microscopic after reading the email. This is heartbreaking because there are many people who spent their better years trying to acquire a spot in Google only to be treated like a mishandled Door Dash order and be left out curbside.

a team of people at a table going over data.
We should start making plans in case this company starts downsizing.
Door Dash here I come.
Photo by RF._.studio, please support by following @pexel.com

Letting Go by Numbers

You may be curious to know how many people and why is Google laying off. As of right now Google either has or seeking to let go of about 12,000 employees. And interns looking to land a job with Google have been put on freeze with a chance of having to pivot their plans because landing a job at Google isn’t looking promising anymore.

Google’s CEO Sundar Pichai informed employees this decision resulted from the realization of unrealized growth expectations. This translates to, if you have ever thrown a house party, I invited too many people and a good chunk of you have to go. So sorry folks but don’t forget to tip your bartender and close your tab on the way out.

This makes Google the latest tech giant to “trim the fat” after the rapid expansion during the COVID-19 pandemic had worn off. Pichai did take full responsibility for the decision however, this doesn’t soften the blow but at least he did address his muck up.

Yours truly even applied at Google and like most of the companies I’ve applied to, they scoffed at my achievements because I didn’t come from a university or have the certifications, they were screening for but after applying for their apprenticeship program and never hearing anything more about it, this all makes sense now.

young man sat worried.
I have spent years in school, I never gave much thought into pursing other skills.
Photo by cottonbro studio, please support by following @pexel.com

Being The Jack of Spades

This brings things back into perspective from the introduction I made earlier. Not the toaster part but that has a play in it too. What would you do if you had to part ways with your employer and either have a small chance of coming back or none?

After spending years on the conveyer belt traveling from school to college and from college to fall into a position in a company that you hope to carry you into your golden years, you find the world is changing and companies of yesterday have less of a care for their current longstanding and hope-filled potential employees due to having to rapidly change.

A thing about jobs is that they are meant to be a short-term service while having a career, on the other hand, is better but not the best since you must specialize in something. The problem with this is you have to be careful with whatever specialization you choose because it could either contribute to oversaturating the market or end up being such a small niche in the wrong area that people have no use for it.

A solution to preparing for this situation if you are ever so unlucky to come face-to-face with it is to treat your skills like a stock portfolio and be diverse as possible. Be the Jack of All Trades and master of none because in this case, it’s better than being a master of one.

I’m sure there are a few people in Google who were able to shrug off being laid off because either they have a decent amount saved in their savings plan or they have other skills they can rely on. But for a large amount of them, this is removing the blinders and a rude awakening. If you noticed, in school you’re never taught how to adapt to change.

highway near trees under cloudy sky.
Either experience the storm of change or be the storm of change.
Photo by Lucas Martins, please support by following @pexel.com

Made it this far and found this to be entertaining? Then a big thanks to you and please show your support by cracking a like, scripting a comment, or plug-in to follow.

Would like to give sincere thanks to current followers and subscribers, your support and actions mean a lot and has a play in the creation of each script.

Have you ever been laid off before?

Script a comment below about it.

Why You Should Get Yourself a Job with Legacy Programming Languages

Key Takeaways

  • “Old” languages are still relevant: FORTRAN, COBOL, and Pascal continue to play crucial roles in specific domains.
  • FORTRAN: Excels in scientific computing and high-performance computing.
  • COBOL: Remains essential in financial systems for handling large datasets and transactions.
  • Pascal: Influenced modern languages and continues to be used in education.
  • Career opportunities exist: Skilled programmers in these languages are in demand and can command competitive salaries.
  • Learning value: Studying these languages provides valuable insights into the history and foundations of computer science.
  • Evolving landscape: While newer languages are dominant, maintaining legacy systems built on older languages creates ongoing demand for programmers.
AI-generated image. “PEOPLE, PLEASE REMAIN CALM! AI CAN’T TAKE OUR JOBS IF WE LEARN HOW TO PROGRAM BETTER!”

Come one, come all! Welcome back to yet another exciting reason why you should get ahead of the AI threat. We all know AI is on the brink of taking everyone’s job. Everywhere you look you can find someone shouting out loud and not-so-proud; “THEY TOOK OUR JOBS!” Well, in today’s read (which may not help you since AI can program as well) we’re going to over the programming languages of old. Yes, that’s right, in an effort to protect our future, we first must learn about their past. What languages did they speak? Are they still being used today? Could you get a job today using these languages? Are all questions we seek to answer. Let us begin.

Are “Old” Programming Languages Still Relevant?

You might be surprised to learn that some of the oldest programming languages are still very much alive and kicking! While the tech world is constantly buzzing about the latest shiny new languages like Python and JavaScript, languages like FORTRAN, COBOL, and Pascal have a rich history and continue to play crucial roles in various industries.

A Trip Down Memory Lane

  • FORTRAN: Born in the 1950s, FORTRAN (FORmula TRANslation) was a pioneer, designed for scientific and engineering calculations. It excels in number-crunching tasks, making it indispensable in fields like weather forecasting, financial modeling, and high-performance computing. For example, its ability to handle complex mathematical computations with high precision and efficiency is why it’s still used in scientific research and engineering projects.
  • COBOL: This “Common Business Oriented Language” was specifically created for business applications. Think handling massive datasets, managing financial transactions, and powering the back-end systems of many large corporations. You might be surprised to know that millions of lines of COBOL code are still in use today! It’s the backbone of many banking systems, where reliability and extensive processing capabilities are crucial.
  • Pascal: While perhaps less prominent in industry, Pascal played a significant role in computer science education. Its structured approach to programming influenced many modern languages and helped shape how we teach programming concepts. Universities and colleges often used Pascal to introduce students to the fundamentals of programming due to its clear syntax and structured programming principles.
AI-generated image. “We don’t stand a chance if I don’t learn these programming languages. Why do I have to be the chosen one?”

Are They Still Used Today?

Well, the short answer is…yes. Absolutely!

  • FORTRAN: Remains a powerhouse in scientific computing and high-performance computing. Its ongoing relevance is due to its specialized libraries and tools that support extensive mathematical and engineering calculations. This language continues to evolve, with versions like Fortran 90 and Fortran 2008 bringing modern features to the table.
  • COBOL: Continues to underpin critical business systems, especially in finance. COBOL’s strength lies in its ability to process large volumes of transactions with accuracy and reliability. Efforts to modernize COBOL include integrating it with contemporary technologies and updating its syntax to make it more accessible to today’s programmers.
  • Pascal: While its direct use might have declined, its influence on other languages and its role in education remain significant. For instance, Object Pascal (Delphi) carries forward the legacy of Pascal in a modern object-oriented form, used in both desktop and mobile app development.

Can You Still Make Money with Them?

You can make money with any language but apparently companies are willing to pay big bucks. So, the answer is, yet again. Yes, you can!

  • Skilled FORTRAN programmers: are highly sought after in sectors like scientific research and high-performance computing, often commanding competitive salaries. Their expertise is invaluable in maintaining and developing high-precision applications for academia and industry.
  • COBOL programmers: who can maintain and modernize existing systems are in high demand, especially in the financial industry. These programmers ensure the seamless operation of critical financial transactions and data processing tasks, making them indispensable in the banking and insurance sectors.
AI-generated image. “You know the more time I spend programming a computer, the more I realize they’re right. It is time for a change.”

The Evolving Programming Landscape

While newer languages like Python and JavaScript dominate many areas today, the need to maintain and modernize legacy systems built on older languages creates a continuous demand for programmers proficient in these languages. Understanding these foundational languages also provides deeper insights into the development of programming paradigms and practices over the decades.

Should You Learn Them?

Learning older languages can provide valuable insights into the foundations of computer science. If you’re interested in scientific computing, finance, or working with legacy systems, learning FORTRAN or COBOL could open up unique career opportunities. Additionally, the structured thinking and problem-solving skills developed through Pascal can be beneficial across various programming tasks.

In Conclusion

While the tech world is constantly evolving, older programming languages like FORTRAN, COBOL, and Pascal continue to play important roles. They demonstrate the enduring power of robust, well-designed languages and remind us that the history of computing is deeply intertwined with their development and evolution. The knowledge and expertise in these languages remain valuable assets in the ever-changing tech landscape. And with all of that being said, should you learn any of these languages? Or a language in general? Yeah, I mean people should learn something new every day. Learning a programming language, if any, places you above someone who doesn’t know the language. Remember your goal is to standout in the job market, not to blend in.

Disclaimer: This script is for informational purposes only and should not be considered financial or career advice.


Love learning tech? Join our community of passionate minds! Share your knowledge, ask questions, and grow together. Like, comment, and subscribe to fuel the movement!

Don’t forget to share.

Every Second Counts. Help our website grow and reach more people in need. Donate today to make a difference!

One-Time
Monthly
Yearly

Make a one-time donation

Make a monthly donation

Make a yearly donation

Choose an amount

$5.00
$15.00
$100.00
$5.00
$15.00
$100.00
$5.00
$15.00
$100.00

Or enter a custom amount

$

Your contribution is appreciated.

Your contribution is appreciated.

Your contribution is appreciated.

DonateDonate monthlyDonate yearly

Navigating the Nervous Waters of Coding

Daily writing prompt
What makes you nervous?
AI-generated image. “This code is going well…a little too well.”

The Code Creep: Why Every Line Can Feel Like a Tightrope Walk

What makes me nervous? You might think it’s a looming deadline or a particularly gnarly algorithm. And while those definitely get the heart racing, the real source of my coding jitters? It’s the act of coding itself.

Yeah, you heard that right. I absolutely love the process, the puzzle-solving, the feeling of building something from scratch. But with every new line I type, there’s this little nagging voice in the back of my head, a digital gremlin whispering doubts. It’s the anticipation, the hope that hours of work won’t just implode into a cascade of red error messages.

Thinking back, my coding journey started a bit before the world went sideways with the pandemic. Honestly, I hit a point where I felt… stagnant. Like my potential was being deliberately capped. It’s that frustrating feeling when you realize the system isn’t exactly designed to empower you to grow beyond a certain point.

So, I decided to take matters into my own hands. The unexpected downtime of the pandemic actually became my catalyst, a chance to hunker down and learn a skill that could truly unlock new horizons. And that’s how I fell down the glorious, sometimes terrifying, rabbit hole of coding.

The Universal Developer Dread: It’s Not Just Me, Right?

Here’s the thing you might not realize: this nervous energy isn’t some quirky personal trait. Talk to any developer, and they’ll likely nod in grim agreement. We’re constantly battling error codes, those digital slaps in the face that make you question your entire existence (or at least your coding prowess). You think dealing with a disappointed parent is tough? Try facing a computer throwing a tantrum of syntax errors.

But it’s what happens after the initial barrage of errors that truly gets under our skin. It’s that eerie calm when the error messages start to dwindle, when your code actually starts to… work. That’s when the shadow of doubt really creeps in. It’s almost too good to be true.

We’ve all been there, thinking, “Okay, something’s definitely about to break spectacularly.” It’s a collective developer anxiety. So, how do we cope with this constant underlying tension? We do what we do best: we code more. We dive deeper, hoping that with each additional line, we’re solidifying our creation against the inevitable digital gremlins.

AI-generated image. “Mario may have leveled up from these…but I don’t suggest you eat them. They could inspire a “bad trip.””

Leveling Up Your Confidence: Taming the Coding Nerves

So, what’s the secret to keeping those coding nerves in check? Honestly, it boils down to building trust in your abilities. It’s about accepting that debugging and problem-solving aren’t just occasional annoyances; they’re integral parts of the process. Think of it less as a sign of failure and more as a constant opportunity to learn and refine your skills.

It’s about learning to be strategically on guard, anticipating potential pitfalls, and developing the mental resilience to tackle them head-on. Every bug squashed, every error resolved, is a small victory that builds your confidence and quiets that nervous inner voice, just a little bit more each time.

So, fellow coders, know that you’re not alone in this exhilarating, sometimes nerve-wracking journey. Embrace the challenge, trust your skills, and keep on building. The digital world awaits!

Key Takeaways:

  • Coding can be a source of anxiety: Despite the love for the craft, the constant potential for errors creates a persistent sense of nervousness for many developers.
  • The fear of things going “too well” is real: After battling numerous errors, a period of smooth coding can actually induce anxiety, as developers anticipate an impending issue.
  • Coding skills were a proactive pursuit: The author’s journey into coding was driven by a desire for growth and a feeling of being held back in previous environments.
  • Error debugging is a universal developer experience: Facing and resolving errors is a fundamental and shared aspect of being a developer.
  • Coping involves continuous coding: Developers often deal with their anxieties by immersing themselves further in their work, hoping to solidify their code.
  • Building trust in one’s skills is crucial: Overcoming coding nervousness involves developing confidence in your abilities to problem-solve and debug.
  • Problem-solving is an integral part of development: Debugging isn’t seen as a failure but as a necessary and ongoing aspect of the coding process.
  • Strategic vigilance is key: Learning to anticipate potential problems and being prepared to address them is important for managing coding anxieties.