Me: "Ahh yes finally done making this big module that does X, took me 2 weeks but its done!"
Coworker: "You know there's a plugin that does X right?"
Me: "Just go..."
Coworker: "Ohh and it also does Y which makes X easier if you have to do Z"
Me: "GET OUT OF HERE I NEED TO CRY"

Worst meeting I’ve been in?

Transitioning from an old system, the CEO said “We will transition on June 30th of next year or … heads … will … roll.”

Everyone knew what ‘heads will roll’ meant.

I wasn’t particularly worried because 90% of my work would be completed by December, the rest would be completed by the users (data transfers, etc.). Realistically, no reason we couldn’t transition by April or May.

June 15th comes around – CEO calls a meeting (managers, VPs, kind of a big deal) because we’re nowhere close to turning on the new system. Needless to say, I was a bit nervous, but my part had been done since November. I worked late nights, weekends, early mornings…I killed myself making sure the system was 100% ready.
CEO starts asking the different managers about what is taking so long…
Mgr-1: ”Well, we aren’t easily able to map our old customer records into the new system. The new system is too hard to use and taking a long time.”
Mgr-2: “We can’t reconcile until the customer records are in the database.”
Mgr-3: “We can’t proof the purchase orders until the customer accounts are reconciled.”
The ‘waiting on him/her’ excuse went around the room.
At this point, couple of the VPs look over at me …I felt like I just turned white …oh crap…I’m going to get fired because all these –bleep-holes just threw me under the bus.
CEO listens…nods…looks at my boss..
CEO: “OK, move the due date out 6 more months. Have your team help out in any way they can. I want this new system working correctly no matter how long it takes. If we need to move the date again, we just do.”

Part of me was relieved, other part was looking for a flame thrower. I worked myself to the bone, risked my marriage (in hindsight, I was not a nice person to her during that time), probably had an ulcer, and these sorry excuse for human beings dragged their asses for months and there was zero accountability.

That meeting was over 15 years ago and it bothered me so much I still remember the CEO was wearing a green button up shirt, khaki pants, and drinking coffee from a Break Time coffee cup.

Upside? Over the next couple of years, every one of those managers either quit or got fired.

It's enough. I have to quit my job.

December last year I've started working for a company doing finance. Since it was a serious-sounding field, I tought I'd be better off than with my previous employer. Which was kinda the family-agency where you can do pretty much anything you want without any real concequences, nor structures. I liked it, but the professionalism was missing.

Turns out, they do operate more professionally, but the intern mood and commitment is awful. They all pretty much bash on eachother. And the root cause of this and why it will stay like this is simply the Project Lead.

The plan was that I was positioned as glue between Design/UX and Backend to then make the best Frontend for the situation. Since that is somewhat new and has the most potential to get better. Beside, this is what the customer sees everyday.

After just two months, an retrospective and a hell lot of communication with co-workers, I've decided that there is no other way other than to leave.

I had a weekly productivity of 60h+ (work and private, sometimes up to 80h). I had no problems with that, I was happy to work, but since working in this company, my weekly productivity dropped to 25~30h. Not only can I not work for a whole proper work-week, this time still includes private projects. So in hindsight, I efficiently work less than 20h for my actual job.

The Product lead just wants feature on top of feature, our customers don't want to pay concepts, but also won't give us exact specifications on what they want.
Refactoring is forbidden since we get to many issues/bugs on a daily basis so we won't get time.
An re-design is forbidden because that would mean that all Screens have to be re-designed.
The product should be responsive, but none of the components feel finished on Desktop - don't talk about mobile, it doesn't exist.
The Designer next to me has to make 200+ Screens for Desktop and Mobile JUST so we can change the primary colors for an potential new customer, nothing more. Remember that we don't have responsiveness? Guess what, that should be purposely included on the Designs (and it looks awful).
I may hate PHP, but I can still work with it. But not here, this is worse then any ecommerce. I have to fix legacy backend code that has no test coverage. But I haven't touched php for 4 years, letalone wrote sql (I hate it). There should be no reason whatsoever to let me do this kind of work, as FRONTEND ARCHITECT.

After an (short) analysis of the Frontend, I conclude that it is required to be rewritten to 90%. There have been no performance checks for the Client/UI, therefor not only the components behave badly, but the whole system is slow as FUCK! Back in my days I wrote jQuery, but even that shit was faster than the architecuture of this React Multi-instance app. Nothing is shared, most of the AppState correlate to other instances.

The Backend. Oh boy. Not only do we use an shitty outated open-source project with tons of XSS possibillities as base, no we clone that shit and COPY OUR SOURCES ON TOP. But since these people also don't want to write SQL, they tought using Symfony as base on top of the base would be an good idea.
Generally speaking (and done right), this is true. but not then there will be no time and not properly checked. As I said I'm working on Legacy code. And the more I look into it, the more Bugs I find. Nothing too bad, but it's still a bad sign why the webservices are buggy in general. And therefor, the buggyness has to travel into the frontend.

And now the last goodies:
- Composer itself is commited to the repo (the fucking .phar!)
- Deployments never work and every release is done manually
- We commit an "_TRASH" folder
- There is an secret ongoing refactoring in the root of the Project called "_REFACTORING" (right, no branches)
- I cannot test locally, nor have just the Frontend locally connected to the Staging webservices
- I am required to upload my sources I write to an in-house server that get's shared with the other coworkers
- This is the only Linux server here and all of the permissions are fucked up
- We don't have versions, nor builds, we use the current Date as build number, but nothing simple to read, nonono. It's has to be an german Date, with only numbers and has always to end with "00"
- They take security "super serious" but disable the abillity to unlock your device with your fingerprint sensor ON PURPOSE

My brain hurts, maybe I'll post more on this shit fucking cuntfuck company. Sorry to be rude, but this triggers me sooo much!

Recently been lurking more and apart from the new plagues the community is going through at the moment, I swear this app goes through literal anime arcs with random entities that rise up and cause problems, kinda hilarious in hindsight. I will say it's been nice seeing y'all's names and rants again. I know I also see everything in the discord but that's got a different vibe. It doesn't help I just fucking hate discord.

It's also been a weird experience looking at my old rants. I literally found this app as I was getting my start in development and it's crazy to see the progress and put everything into perspective. Holy shit was I CRINGE. Regardless pretty nice.

I spent over a decade of my life working with Ada. I've spent almost the same amount of time working with C# and VisualBasic. And I've spent almost six years now with F#. I consider all of these great languages for various reasons, each with their respective problems. As these are mostly mature languages some of the problems were only knowable in hindsight. But Ada was always sort of my baby. I don't really mind extra typing, as at least what I do, reading happens much more than writing, and tab completion has most things only being 3-4 key presses irl. But I'm no zealot, and have been fully aware of deficiencies in the language, just like any language would have. I've had similar feelings of all languages I've worked with, and the .NET/C#/VB/F# guys are excellent with taking suggestions and feedback.

This is not the case with Ada, and this will be my story, since I've no longer decided anonymity is necessary.

First few years learning the language I did what anyone does: you write shit that already exists just to learn. Kept refining it over time, sometimes needing to do entire rewrites. Eventually a few of these wound up being good. Not novel, just good stuff that already existed. Outperforming the leading Ada company in benchmarks kind of good. At the time I was really gung-ho about the language. Would have loved to make Ada development a career. Eventually build up enough of this, as well as a working, but very bad performing compiler, and decide to try to apply for a job at this company. I wasn't worried about the quality of the compiler, as anyone who's seriously worked with Ada knows, the language is remarkably complex with some bizarre rules in dark corners, so a compiler which passes the standards test indicates a very intimate knowledge of the language few can attest to.

I get told they didn't think I would be a good fit for the job, and that they didn't think I should be doing development.

A few months of rapid cycling between hatred and self loathing passes, and then a suicide attempt. I've got past problems which contributed more so than the actual job denial.

So I get better and start working even harder on my shit. Get the performance of my stuff up even better. Don't bother even trying to fix up the compiler, and start researching about text parsing. Do tons of small programs to test things, and wind up learning a lot. I'm starting to notice a lot of languages really surpassing Ada in _quality of life_, with things package managers and repositories for those, as well as social media presence and exhaustive tutorials from the community.

At the time I didn't really get programming language specific package managers (I do now), but I still brought this up to the community. Don't do that. They don't like new ideas. Odd for a language which at the time was so innovative. But social media presence did eventually happen with a Twitter account that is most definitely run by a specific Ada company masquerading as a general Ada advocate. It did occasionally draw interest to neat things from the community, so that's cool.

Since I've been using both VisualStudio and an IDE this Ada company provides, I saw a very jarring quality difference over the years. I'm not gonna say VS is perfect, it's not. But this piece of shit made VS look like a polished streamlined bug free race car designed by expert UX people. It. Was. Bad. Very little features, with little added over the years. Fast forwarding several years, I can find about ten bugs in five minutes each update, and I can't find bugs in the video games I play, so I'm no bug finder. It's just that bad. This from a company providing software for "highly reliable systems"...

So I decide to take a crack at writing an editor extension for VS Code, which I had never even used. It actually went well, and as of this writing it has over 24k downloads, and I've received some great comments from some people over on Twitter about how detailed the highlighting is. Plenty of bespoke advertising the entire time in development, of course.

Never a single word from the community about me.

Around this time I had also started a YouTube channel to provide educational content about the language, since there's very little, except large textbooks which aren't right for everyone. Now keep in mind I had written a compiler which at least was passing the language standards test, so I definitely know the language very well. This is a standard the programmers at these companies will admit very few people understand. YouTube channel met with hate from the community, and overwhelming thanks from newcomers. Never a shout out from the "community" Twitter account. The hate went as far as things like how nothing I say should be listened to because I'm a degenerate Irishman, to things like how the world would have been a better place if I was successful in killing myself (I don't talk much about my mental illness, but it shows up).

I'm strictly a .NET developer now. All code ported.

Lately I have been overthinking a lot. I am stressing myself out on every single decision believing that decisions I make today will define my tomorrow.

In hindsight, all the major and positive impact that have happened in my life were the decisions I took on the fly without much underlying research. The executional part did have me struggle a little but almost all of the best things happened to me were unplanned.

Funnily this has been my philosophy since years but guess what, I failed to follow it this time.

My overthinking and over planning caused me to mess up a little leading to a lot of unwanted anxieties.

Now let's reflect a little on the past, when my first relationship ended.. wait.. even earlier..

When I was in 5th standard, I was crazy bullied at school but I was happy go lucky and things turned out in my favour throughout till date.

I used to do what I loved and enjoyed. I literally never worried or thought about future. Not even once, things just fell in place for me miraculously.

When my first relationship ended, I was shattered. The darkest time of my life and me being all alone, I came out strong.

I used to live happy. I used to do stuff that I loved. I used to not care about what people thought. No socials for me. I used to follow random dark or counter culture stuff and be a little rebel that I am.

I remember, she and I used to go for fuck tons of events, hangout at waterfront of the city, spend time together and just be ourselves.

I never used to compete, compare, or conflict with anyone.

devRant was (and still is) a digital home for me. Wonderful phase of life.

Then shit went south. I joined Reddit. A girl told me about a pen pal app. Met another girl there.

Joined Telegram again to be in touch with her. She wasn't interested but I stayed on Telegram.

I could pick up any girl in minutes and do so effortlessly.

Slowly the twin extrovert in me came out. I started building and maintaining insanely awesome network.

Started spending more time on Reddit and Telegram.

Joined a bunch of professional communities. Career sky rocketd.

I was still happy and living a gala life at this stage.

Slowly, I realised I was underpaid (via professional communities). That unsettled me.

I frantically started hunting for jobs. 2020 and COVID-19 hit. Being indoors sucked more.

Became more aggressive on job hunt, money, building skills, work work work...

Met a hoe who fucked my emotions and ethics even further.

Got a high paying job. WLB went negative.

I started losing myself. I forgot my hobbies. I don't know what happiness is. I don't remember when I last smiled. I started planning my finances. Overthinking and stressing about shit troubled me into sleepless nights followed by early morning calls made things worse to my health.

I lost the clarity of my life. I FUCKING LOST ME.

I want myself back and I am gonna work for it. That happy little rebel Floyd who never gave a fuck about other's opinion on him or his beliefs. That dude who was shy to talk to girls. The guy who'd follow his passion and not society of high paying jobs or shit.

I almost got my finances and taxation sorted. Now I'll work to get my office timings in place. If not then I'll switch and find a job in UK/EU with a good WLB. And at the same time I'll pursue my hobbies.

Enough of rat race shit. Money has always been an outcome of my hard work and high work ethics. I want to live a life and I am willing to trade of extremely high paying/stressful FAANG jobs for a small company keeping me happy.

I'll be the happy Floyd that I was once was.

Because, the heart wants what the heart wants :)

First week in the job and I was told to update an intranet page. Opened it in notepad, made the change and saved it.

Turned out it was a SharePoint site and saving it in notepad broke all the links and turned it into a static page. Even worse, it was the homepage of the intranet.

I blame lack of training and, in hindsight, how awful SharePoint is.

Anyway, at least we successfully tested the backup process...

I'm not sure where I'm going with this, but I'm fucking sick of my experience with the world.

I have a feeling that all that 1984 conspiracy type of ideas that I previously considered bullshit and fear mongering are real.

(Just to be clear, I'm not including most conspiracy theories which are very ignorant like flat earth, fake moon landing, or antivax, the people that spread those theories can die a horrible death IMHO).

Corporation consolidation is a fact and appears to become irreversible.

Because of technology, I can stay in the comfort of my house, safe from crime and be entertained without needing to have direct contact with humans.
People might say "that's your fault for not leaving the house". True but that is just how the world is.

The outside world in the cities I lived in is not a welcoming place.
Hell if you fucking find a bench it's a goddamn miracle, and if you do and sit for a long time, the police stares at you like you are up to something.

People don't talk to you because "don't talk to strangers".
It can be rare to find water or a bathroom that isn't a complete shithole.

So no wonder I rather stay at home, the outside world is hostile.

So yeah, go to a mall or something. And consume, consume, consume, because the outdoors suck.

Many pioneers thought technology was to improve the quality of life.

But no, it's just more isolation, less direct contact with people, less giving a fuck about other people.

And that's how feel about people of today. The least amount of fuck giving about others possible.

You would you would connect to more people faster, but no, the result is just millions of people browsing through the same "entertainment", shitty aggregated content.

Yes, consolidation affects internet too. Everything goes through fucking google, youtube, or whatever other fucking top 10 company.

Just like the class disparity, 1% of the things online get 99% of the exposure.

So if you're a small time anything, basically fuck you, because you're not something enormous.

Like, I wished I was a game developer, but there's thousands of brilliant indie games that get released every year, and they barely make what they're worth.
So why should I fucking try? So I can get ruined financially and I don't have a place to live in?

Software itself is so complex that is impossible to scrutinize decently.
We all laugh at congressmen asking the zuck silly questions.

Out of touch, true, but in hindsight, it is true to some extent that software is hard to regulate. Every software I on earth doesn't meet some standard one way or another.

Or maybe it's just too many of us right now.
When people scroll their search results to get access to the things they should be interested in, the only practical interface right now is being showing one link at a time.
But there's millions and millions of results.

One redeeming aspect of life is that one day I won't be alive anymore to observe the disgusting world we live in.

This could be just pure rambling and I can't prove any of the things I'm saying, I could just have been making the wrong friendships. So take this with a grain of salt.

I literally just had this conversation.

H: Me
C: Colleague

C: "Hey Hindsight, I'm having issues with our web print driver, it's not opening the browser after printing"
H: "Have you checked Interactive Mode in the installer so it opens the browser?"
C: "Yes"
H: "Are you sure you have the right domain name in your configuration file? It should be <thing.example.com>"
C: "Ah, it's just example.com. Should I just change it in the config?"
H: "No you need to regenerate the config from our server tool, because the server data needs to match your client config data"
C: "Ok, my config says <example.com>"
H: "Yes, just regenerate the config with <thing.example.com> instead for the domain"
C: "Ok I'll do that. What was the correct domain again?"
H: thinking "Holy shit can you really be that dumb!" but saying "<thing.example.com>"

Being smart but not applying yourself is the same as being stupid.
I've been having a rough semester , as I sat around and played video games for the first few weeks.
Ever since I stopped gaming I started doing more code stuff, and getting things done.
In hindsight, I probably shouldve stopped gaming when the semester started.
What are your guys experience with this? What stratergies do you use for time management?

Literally painful dev learning experience: Do your damn stretches and invest in a good chair.

Spent a couple of months of WFH working eight hours a day in an awful chair and started getting back pain out of the blue. Part of my first paycheck after that went into a decent office chair, in hindsight I should've spent more on it but goddamn what a relief it was not having to spend an entire day in the tiny, back-breaking piece of shit my landlord calls a desk chair.

Hello DevRant community! It’s been a while, almost 5 years to be exact. The last time I posted here, I was a newbie, grappling with the challenges of a new job in a completely new country. Oh, how time flies!

Fast forward to today, and it’s been quite the journey. The codebase that once seemed like an indecipherable maze is now my playground. The bugs that used to keep me up at night are now my morning coffee puzzles. And the team, oh the team! We’ve moved from awkward nods to inside jokes and shared victories.

But let’s talk about the real hero here - the coffee machine. The unsung hero that has fueled late-night coding sessions and early morning stand-ups. It’s seen more heated debates than the PR comments section. If only it could talk, it would probably write its own rant about the indecisiveness of developers choosing between cappuccino and latte.

And then there are the unforgettable ‘learning opportunities’ - moments like accidentally shutting down the production server or dropping the customer database. Yes, they were panic-inducing crises of apocalyptic proportions at that time, but in hindsight, they were valuable lessons. Lessons about the importance of thorough testing, proper version control, reliable backup systems, and most importantly, owning up to our mistakes.

So here’s to the victories and failures, the bugs and fixes, the refactorings and 'wontfix’s. Here’s to the incredible journey of growth and learning. And most importantly, here’s to this amazing community that’s always been there with advice, sympathy, humor, and support.

Can’t wait to see what the next 5 years bring! 🥂

When i was younger, lesser experienced and more naive than now; i got away with a lot of things. By lot of things i mean security flaws in my applications and overall architecture. I realise now i could've so easily been pawned.

Not that i claim to be totally secure even now, or would ever. It is a process, slow and painful one - Learning.

What i wish to point out is the role of favorable probability (non believers would call it luck). Security is so much about it. You get away with so many things for so long. And bang one day the roll of dice is unfavorable. On such rare occasions, just look back and wonder - damn i should've been breached long ago.

You have master the art of thinking when you overcome biases.

Which one is your favourite?

A few I like are:
- Survivorship bias
- Hindsight bias
- Familiarity/Mere exposure effect
- Dunning Kruger (well ofc.)
- Confirmation bias
- Self serving (for that ungrateful bitch)
- Sunk cost fallacy

In one of my first programming classes, I remember asking my instructor why "System.out.println()" has the periods between System, out and println. All I got back was a "thats just how it is". This really pissed me off and I ignored that instructor for the rest of the semester. Passed the class but since I didn't bother to self study either, wasted a lot of time resources. Hindsight, should have looked it up myself.

when you click “Pronounce” button on Google Translate the second time, it pronounces things slower. What a genius feature. Clicking it the second time because you didn’t quite catch it the first time seems so obvious in hindsight.

This week we had a live production issue that our staff were catching/fixing on the fly. We're a relatively small software team without any direct external customers, so this is not too unusual.

Unfortunately, the person in charge of dealing with these issues didn't resolve it during the work week, so we were stuck with it over the weekend. Said responsible employee left at 2:30 on Friday without figuring out how we'd deal with the problem without any staff in the office to intercept problem cases. Better yet, he drove all the way back, and was there from 3:30 to 4 and promptly left again without telling the rest of the team what was going on with the production issue. We asked how it happened, what it was, etc, but didn't focus on his fix (in hindsight, a mistake).

Since it's his job, I assumed that he would let us know what was up before he left on Friday. It turns out that he never addressed the production issue at all and just decided to leave.

A junior developer and I spent two hours contacting management (who, at this time are already at home with their families) to get clearance to either shut the system off or fix it. No one wants to give it and no one that's high enough up to approve the decision is available.

In the end, we asked the weekend mechanical support team (some friends of mine) to monitor the issue and they kindly accepted.

All of this could have been avoided if my coworker had either told us his plan earlier (so we could ask about the lack of coverage), gotten approval to shut it down for the weekend, or covered his own ass before he left for the day.

Ugggh. I get that we all make mistakes, but I really hope this guy shapes up soon.

In hindsight, this was entirely predictable

More masturbation with numbers.

If you take some product p,
and do

√p**(1/p)

and it's factors

a**(1/p)

and

b**(1/p)

you might find something interesting.

Take for example

a=21977
b=43331
p=a*b=952285387

(√p)**(1/p) = 1.0000000108551363

a**(1/p) = 1.0000000104986928
b**(1/p) = 1.0000000112115799

More often then not, a, b, or both, will share one or two of the most significant digits in the mantissa, as the root of p.

It doesn't always work, but it seems to be true more often than you might expect.

This is probably obvious in hindsight but I still think it's cool.

In some instances if you then do, say
sqrt(log(p, 1.000000010)), it comes pretty close to the original factors, but thats really hit or miss.

So annoying when you get 80% of the way through a project then figure out a more elegant way of solving it, but can't change it now because of time constraints

Learning rust with a very tight deadline. Not something I'd recommend since you will be likely to spend more time trying to get your project to compile than getting on with your project.
In my case the project was a compiler(in hindsight I'd have picked ocaml or scala instead).

When your family v. 1.0 is very busy trying to enforce their outdated perspective regarding finding a compatible female of the human race for the purpose of tightly coupling by mutual contract and with hindsight of multiplication of inherited DNA sequence and genomes...

You ever pick Google Cloud and realise you should’ve gone for AWS? Curse hindsight.

First or second week of my first job (internship) and my manager mentions that upper management has decided that a couple of engineers are being reassigned to the new technical writing team, myself included, effective tomorrow with no prior warning, before dragging us into a tech-writing standup.

A couple of hours later my manager apologizes to me for forgetting to tell me about this and asked how I felt about this. I basically answered "not well, this isn't what I signed up for", and credit to him, he pulled enough strings to get me out of that team and back to my actual job. In hindsight I suspect that it was more due to the fact that this internship was a three-way contract with the university and that if I complained they might get their intern supply cut off.

I dunno if any of my choices have been "bad". Humans are great at explaining things to themselves to feel better. Narratives is our strength and we love them.

In hindsight everything seems to be a correct choice and kinda makes sense. For everything else is just a lesson to learn from.

So I figure since I straight up don't care about the Ada community anymore, and my programming focus is languages and language tooling, I'd rant a bit about some stupid things the language did. Necessary disclaimer though, I still really like the language, I just take issue with defense of things that are straight up bad. Just admit at the time it was good, but in hindsight it wasn't. That's okay.

For the many of you unfamiliar, Ada is a high security / mission critical focused language designed in the 80's. So you'd expect it to be pretty damn resilient.

Inheritance is implemented through "tagged records" rather than contained in classes, but dispatching basically works as you'd expect. Only problem is, there's no sealing of these types. So you, always, have to design everything with the assumption that someone can inherit from your type and manipulate it. There's also limited accessibility modifiers and it's not granular, so if you inherit from the type you have access to _everything_ as if they were all protected/friend.

Switch/case statements are only checked that all valid values are handled. Read that carefully. All _valid_ values are handled. You don't need a "default" (what Ada calls "when others" ). Unchecked conversions, view overlays, deserialization, and more can introduce invalid values. The default case is meant to handle this, but Ada just goes "nah you're good bro, you handled everything you said would be passed to me".

Like I alluded to earlier, there's limited accessibility modifiers. It uses sections, which is fine, but not my preference. But it also only has three options and it's bizarre. One is publicly in the specification, just like "public" normally. One is in the "private" part of the specification, but this is actually just "protected/friend". And one is in the implementation, which is the actual" private". Now Ada doesn't use classes, so the accessibility blocks are in the package (namespace). So guess what? Everything in your type has exactly the same visibility! Better hope people don't modify things you wanted to keep hidden.

That brings me to another bad decision. There is no "read-only" protection. Granted this is only a compiler check and can be bypassed, but it still helps prevent a lot of errors. There is const and it works well, better than in most languages I feel. But if you want a field within a record to not be changeable? Yeah too bad.

And if you think properties could fix this? Yeah no. Transparent functions that do validation on superficial fields? Nah.

The community loves to praise the language for being highly resilient and "for serious engineers", but oh my god. These are awful decisions.

Now again there's a lot of reasons why I still like the language, but holy shit does it scare me when I see things like an auto maker switching over to it.

The leading Ada compiler is literally the buggiest compiler I've ever used in my life. The leading Ada IDE is literally the buggiest IDE I've ever used in my life. And they are written in Ada.

Side note: good resilient systems are a byproduct of knowledge, diligence, and discipline, not the tool you used.

[Week 44 rant] Worst CS teacher experience:

In Uni (aka college), CS teacher would show introductory C code during the lecture, then proceed to run it... And compilation errors. And then spend the next 45 mins trying to fix it. Usually they would get it working in the last 5 mins of the one hour lecture.

This would go on every single lecture for the next 10-12 weeks.

Most of it was basic stuff like hello world through to sorting algorithms etc.

At the time it was pretty silly and 3/4 of the class stopped attending the lectures...

----------------

In hindsight maybe it was all intentional and training us for what real dev life would be like?

Hindsight has taught me that I should have taken the job that had me take a coding quiz

Doing the Full Stack Nanodegree from Udacity
Using Google's oAuth Sign in in my Flask App, I realized that no matter what browser I use, I was unable to logout, Google always threw an error my way. I figured something must be wrong with my code..
Searched on Google, couldn't find anything relevant, gave up on first 4 results(not pages, yeah I'm that lazy!)
Spent 3 hours Debugging at different points, removing all the abstraction I've put in using various libraries (Bad move)
Finally it dawned on to me to check Udacity forum as well. It's a frickin cache/cookie thing. Tried the app in an incognito window, worked like a charm. Reverted code back with all the libraries, worked like a charm again!

FUCK YOU GOOGLE! In your attempts to track users, you're even making our work difficult!

(in hindsight, I should probably be better at asking/looking for help)

In hindsight, sending WoL to an untested machine while 30 kilometers away was not a very smart idea.

The machine is up, but does not respond to pings and is unreachable.

It's been a good month where honestly I had nothing to rant about. Pretty much doing my own project setting up ELK.

But last few days I had to return to the reality called teammates....

It where it ok... I mentored one of them, then did the code review yesterday

And that's when the shit hit the fan.

I told them to do X but then they did Y instead thinking that they were smart.

In hindsight they seem to have no idea wtf they were doing, inexperienced and couldn't even use console.log and JSON.stringify to debug object states...

Which course now reminded what's wrong with this team, you got people jumping around stacks and projects so they're all mediocre on all of them. Rather than having specific people being good at one of them (aka more experienced than a noob).

And if course this morning, manager asked me to look into something on a program I haven't support in a while (there are a free people that are more experienced and know the current state better). And he said this is quick and urgent... And actually when he said that I'm like uh.... don't think so....

And last thing is we had to rerun a report in production so needed the shipper ten to do it. Asked them look yesterday, users were waiting.

Today... Still not done. And well I actually can run the report myself locally.. takes 5mins but in production they need to reload the data but that should take at most 20mins... Either way... Nothing was done.

Oh and I just remembered I raised a request to it SA group to have some not script installed... That not done either.

And this is why relying on others it at least these people is a bad idea..... Unless your are capable of firing them...

If you really like math or theory, I think a degree or a few is the way to go. Plus, you can get a head start in your career that way. However, I think I would have not gone to college in hindsight and self-studied since I am regretting the career field now.

Didn't know how to do backend development. The organisation I was working for then needed a simple backend. Learnt some PHP and developed the entire backend in less than 8 hours

PS In hindsight, the code was grotesque, but at least it worked!

i present to you:

'made fuzzysearch more precisely'

while being technically true this tipsy commit is a bit strange in hindsight.

In hindsight, what questions you wish you had asked your current/most recent employer before joining the company?

I applied to this company and I can't find any information on them. What they stand for, their mission statements... I'm kinda sketched out. Should I continue applying to this company?

In hindsight they're "Still operating largely in stealth mode" so maybe I shouldn't be surprised, also there seems to be no way to tell what their paygrade is and I don't want to step into something that may not be for me.