Did a very tiny migration for a client which would normally be done against our hourly rate but decided to do it for free as it would take me like 5 minutes and it was a very important thing for him and he actually offered to pay.

Fuck it, he'll be very happy, it doesn't take me much time and I know my boss would approve.

Did the migration, messaged the client and he thanked me.

Next day a cake arrives at work with my name on it and "thanks for helping us with the migration!"

Now that's how you make my fucking day!

When you realize only one "person" in your life remembered

Worst dev I've interviewed?

"Archie" ran his own consulting business for almost 20 years. Prior to his interview, Archie sent HR (to send to us) his company's website, where he had samples of code for us to review (which was not bad, this guy did know his stuff).
What I found odd was Archie was the lone wolf at his company, but everything I found about him (the about page, his bio, etc), Archie was referred to as 'Mr. Archie Brown'.
Ex. 'Mr. Archie Brown began his humble career and 'Mr. Archie Brown is active in his church and volunteers his time in many charities ...'
Odd to refer to yourself in the third person on your own site, but OK, I like putting hot sauce on my mac & cheese (no judgement here).

Then the interview..standard stuff, then..
Me: "Given your experience, this is an entry level developer position. Do you feel the work would be challenging enough for you?"
Archie: "Yes, Mr. Archie Brown would have no problem starting at bottom. You see ..."

Almost any time he would reference himself, instead of 'me' or 'I', he would say 'Mr. Archie Brown'. As the interview continued, the ego and self-importance grew and grew.
My interview partner wanted to be done by using the escape clause, "PaperTrail, I'm good, do you have any questions?"

Yes, yes I do. I was having too much fun listening to this guy ramble on about himself. I made the interview go the full hour with the majority of time 'Archie' telling us how great he is.

The icing on the cake was my partner caught his gold cuff-links and tie-pin where his initials and how he kept raising his hands and playing with his tie to show us (which I totally missed, then was like "oh yea, that was weird")

After the interview, talking with HR:
HR-Jake: "How did it go?"
John: "Terrible. One of the worst. We would have been done in 10 minutes if PaperTrail didn't keep asking questions."
Me: "Are you kidding!? I had the best time ever. I wish I could have stayed longer."
HR-Jake: "Really? This guy was so full of himself I wasn't sure to even schedule with you guys. With his experience, I thought it deserved at least a round with you two. You think we should give him a chance?"
Me: "Hell no. Never in a million years, no. I never in my whole life met anyone with such a big ego. I mean, he kept referring to himself in the third person. Who does that?"
HR-Jake: "Whew!...yea, he did that in the phone interview too. It was a red flag for us as well."

Couple of weeks later I ran into HR-Jake in the break room.
HR-Jake: "Remember Mr. Archie Brown?"
Me: "To my dying day, I will never forget Mr. Archie Brown."
HR-Jake: "I called him later that day to tell him the good news and he accused me of being a racist. If we didn't give him the job, he was getting a lawyer and sue us for discrimination."
Me: "What the frack!"
HR-Jake: "Yep, and guess what? Got a letter from his lawyer today. I don't think a case will come in front of a judge, but if you have any notes from the interview, I'll need them."
Me: "What are we going to do?"
HR-Jake: "Play the waiting game between lawyers. We're pretty sure he'll run out of money before we do."

After about 6 months, and a theft conviction (that story made the local paper), Mr. Archie Brooks dropped his case (or his lawyers did).

In my college days i was designing a bootloader for avr microcontroller , i had the idea to flash code wirelessly to avr over bluetooth and also cross compile the compiler for android device so that you can code on android, every thing went well just one thing didn't, i saw that code of certain size is executing properly , greater than that size gives me wired outputs so i have to dump hex from the avr (that is flashed the by bootloader) and compaire it with the original hex of code it got messy as you can see, most fun part of this bug is that error can be anywhere cross compiler may be fucked up , the bootloader may be fucked up , or it may be my bluetooth module , after 14 hours of staring at the hex code i figured out the mess in bootloader instruction that was changing the page address for flashing .

when it worked it was 3am in night i literally burst into tears of joy next day bought myself a cake to celebrate

Worst dev team failure I've experienced?

One of several.

Around 2012, a team of devs were tasked to convert a ASPX service to WCF that had one responsibility, returning product data (description, price, availability, etc...simple stuff)
No complex searching, just pass the ID, you get the response.

I was the original developer of the ASPX service, which API was an XML request and returned an XML response. The 'powers-that-be' decided anything XML was evil and had to be purged from the planet. If this thought bubble popped up over your head "Wait a sec...doesn't WCF transmit everything via SOAP, which is XML?", yes, but in their minds SOAP wasn't XML. That's not the worst WTF of this story.

The team, 3 developers, 2 DBAs, network administrators, several web developers, worked on the conversion for about 9 months using the Waterfall method (3~5 months was mostly in meetings and very basic prototyping) and using a test-first approach (their own flavor of TDD). The 'go live' day was to occur at 3:00AM and mandatory that nearly the entire department be on-sight (including the department VP) and available to help troubleshoot any system issues.

3:00AM - Teams start their deployments
3:05AM - Thousands and thousands of errors from all kinds of sources (web exceptions, database exceptions, server exceptions, etc), site goes down, teams roll everything back.

3:30AM - The primary developer remembered he made a last minute change to a stored procedure parameter that hadn't been pushed to production, which caused a side-affect across several layers of their stack.

4:00AM - The developer found his bug, but the manager decided it would be better if everyone went home and get a fresh look at the problem at 8:00AM (yes, he expected everyone to be back in the office at 8:00AM).

About a month later, the team scheduled another 3:00AM deployment (VP was present again), confident that introducing mocking into their testing pipeline would fix any database related errors.

3:00AM - Team starts their deployments.
3:30AM - No major errors, things seem to be going well. High fives, cheers..manager tells everyone to head home.
3:35AM - Site crashes, like white page, no response from the servers kind of crash. Resetting IIS on the servers works, but only for around 10 minutes or so.
4:00AM - Team rolls back, manager is clearly pissed at this point, "Nobody is going fucking home until we figure this out!!"
6:00AM - Diagnostics found the WCF client was causing the server to run out of resources, with a mix of clogging up server bandwidth, and a sprinkle of N+1 scaling problem. Manager lets everyone go home, but be back in the office at 8:00AM to develop a plan so this *never* happens again.

About 2 months later, a 'real' development+integration environment (previously, any+all integration tests were on the developer's machine) and the team scheduled a 6:00AM deployment, but at a much, much smaller scale with just the 3 development team members.

Why? Because the manager 'froze' changes to the ASPX service, the web team still needed various enhancements, so they bypassed the service (not using the ASPX service at all) and wrote their own SQL scripts that hit the database directly and utilized AppFabric/Velocity caching to allow the site to scale. There were only a couple client application using the ASPX service that needed to be converted, so deploying at 6:00AM gave everyone a couple of hours before users got into the office. Service deployed, worked like a champ.

A week later the VP schedules a celebration for the successful migration to WCF. Pizza, cake, the works. The 3 team members received awards (and a envelope, which probably equaled some $$$) and the entire team received a custom Benchmade pocket knife to remember this project's success. Myself and several others just stared at each other, not knowing what to say.

Later, my manager pulls several of us into a conference room
Me: "What the hell? This is one of the biggest failures I've been apart of. We got rewarded for thousands and thousands of dollars of wasted time."
<others expressed the same and expletive sediments>
Mgr: "I know..I know...but that's the story we have to stick with. If the company realizes what a fucking mess this is, we could all be fired."
Me: "What?!! All of us?!"
Mgr: "Well, shit rolls downhill. Dept-Mgr-John is ready to fire anyone he felt could make him look bad, which is why I pulled you guys in here. The other sheep out there will go along with anything he says and more than happy to throw you under the bus. Keep your head down until this blows over. Say nothing."

Story of my most useless meeting?

Too many to mention. Here's one. Years ago a new HR associate was specifically hired to better engage the workforce. About once a week, she conducted about an hour to two hour meetings which consisted of every 'touchy-feely' idea you could think of. I swear any day I was going to walk into a meeting and do the "fall back into your partner" trust exercises.

One particular meeting, 'Betty' engaged us with the topic of what keeps us motivated, and I was a little more annoyed than usual because I was behind on a system critical project and these meetings were mandatory.

User1: "Knowing I make customer satisfaction my number one priority."
User2: "The strong sense of accomplishment I feel by doing my best"
Me: "Money"
<you could almost hear Betty's gasp>
Betty: "Oh, no, money shouldn't be the motivator. Money is like icing on the cake. Tell us what keeps you happy and engaged."
<other users nod their heads in engagement>
Me: "Again, money."
User3: "I can't...ugh..I don't believe..oh..why would you say that? I think being part of such a great team is payment enough."
<more nodding of heads>
Me: "Do you work for free? I don't. None of us do. Would any of you keep doing your jobs here if you weren't getting paid?"
Betty: "That is really not the point of this meeting."
Me: "Sure it is. I'll bet if Order Taking starting providing bonuses for positive after-call surveys, employee satisfaction would go through the roof. Anyone else like that idea?"
Betty: "Your attitude isn't helping this discussion. Lets move on."
Me: "Lets not. In 20?? the Gartner group performed a study where they 'discovered' the primary motivator for employees was money. You want employees to perform better, you pay them. It is really that simple."
<I could see the looks of "Its OK to speak my mind?" and others wanting to speak up>
Betty: "Moving on. Lets go over the company core values again and discuss how they enrich our lives at work and at home."

I kept quiet for the rest of the meeting.

The poop hit the fan, and my boss pulls me into a conference room
Boss: "Betty is really pissed at you. She went directly to the VP of HR"
Me: "Good. Does this mean I don't have to attend the enrichment meetings?"
Boss: "Yea, that was her idea of punishment. Lucky bastard."

You know what? Fuck this shit. We spend most of our life locked down in a school, we are being told facts, tested and stressed for many years with the only hope to get out as soon as possible.
Failing is something that keeps you there indefinitely.
Parents keep pushing on kids to achieve the best and get good grades to have a job.
Then something happens.
You get out of school and what happens?
You start working.
A.k.a modern slavery...
Employers thinks that since you are young they are doing YOU a favor if they decided to hire you.
So you find yourself having to do the same tasks everyone is doing, perhaps you are even fully capable of managing them and get the shit done but guess what!!
You are paid the minimum.
You barely make enough to pay off your rent which keeps you locked away from Holidays abroad, from that huge cake you desperately want.
And guess what! Try to raise your voice and you'll get fired in a Matter of seconds, replaced with someone else which accepts any condition.
You dream of a house, a family and a car but you can't even eat healthy with that salary.
So you are forced to buy cheap and low quality food from the same store again and again till you had enough and spend some days with that horrible feeling...
Calling you to get a job interview feels like they are doing you a favor, they always try to give the minimum possible and expect you to work in a serious manner and respect their deadlines.
Colleagues earn a lot more even though they aren't doing anything different from you.
For the first year you won't have any holiday, let alone traveling or anything different from just staying home for 3 days straight.

Banks won't give you a loan because your job doesn't pay off
The day that your car is broken you struggle to eat the whole month.

On top of that, taxes. Because they aren't taking away enough.

I don't want to live this life, I don't want to become a modern slave and work 8-17 everyday for the rest of my life and retire with a shitty retirement pension that won't probably grant me anything again.

I had enough of this shit.
I don't want to go back to work and pretend to do what I am supposed to do with a smile on my face knowing that I am just a number and that no matter how skilled I am I can always get replaced with N number of people for a lower salary of mine.

I am tired
I dream of a life that I won't ever reach this way.

Today I looked up houses prices and felt like shit.
I will never in my entire life be able to afford something so expensive, let alone buying furnitures and what is needed or what I like.

I dream of having my place, my dog and my family but apparently I am asking too much.

How is this even fair in 2018/2019?

I... I am... Speechless.
I wonder how many people out there are in the same situation or even worse and I can't even wrap my mind around that.

This is just modern slavery.

My boss makes a shit load of money from young people that can't complain because they are threatened and will eventually be replaced...

This is my rant.

Day is better. I was given cake.

Manager: "We can't have new releases breaking older versions of the mobile app!!!!! We'll lose all our customers!!!!"

fullStackChris: "That's fine, we can do API versioning, but it will take some time to implement, I'll have to be quite careful and write some tests to implement it. Probably 2-3 weeks..."

Manager: "NO WAY, THAT TIME ESTIMATE IS WAY TOO LONG, WE DON'T HAVE TIME FOR THAT!!!"

fullStackChris: "So how do you wanna support multiple versions of the app without doing any sort of versioning?"

Manager: "...we'll think of something!"

Dev: "..."

And with 99% certainty, I expect to hear this in a week or two:

Manager: "fullStackChris, we'd like to introduce you to the highly technical concept, API versioning. It's a way to version the API so we can support multiple versions of the application our customers use! It's amazing! Please implement this immediately so we can support multiple versions of the application!"

Sigh... each day managers learn a bit more how physical reality works... you can't have your cake and eat it too.

A company I applied to asked me to make a small CakePHP project to see if i am worthy. I was fairly good with cake so i procrastinated, planning to do it the weekend before the interview.

on that weekend my girlfriend needed help with something so i neglected the company project to help her and later made a half assed one the night before my second interview.

My half assed project couldnt compete with the others so i got ghosted by that company, ended up working in a company across the street from it with twice the salary

to this day i am so glad i didnt get accepted there or id be working for half my current pay.

Procrastination can save careers

Yesterday (or the day before that depending on your timezone and day-night schedule - this Friday) my OnePlus 6T arrived. After only 2 days of time between placing the order and actually getting the phone, quite impressive!

The DHL guy asked me upon receipt - is it the OnePlus 6T? - Yes it is!! - "An amazing device it is!", he said. And honestly.. he couldn't be more right.

I might be a bit biased on this because after all I did just spend €630 on this phone. But it feels so snappy, high quality, the 8GB of RAM is just.. it blows my mind. But I'm sure that the other reviews did this sort of jazz already.

The things that set this phone apart for me though were the following.

When I get a new phone or tablet, usually the first thing I do is rooting it. This one was no different, about an hour after receipt it was successfully rooted and loaded with Magisk. Currently I'm still in the phase of "getting to know the phone", wherein fuckups are usual. This time again being no different - I removed some apps and apparently did something to it that the search engines - both Google and DuckDuckGo - didn't quite like, as both of them would crash upon application launch. Me in full panic mode of course, desperately trying to find the stock ROM (which doesn't seem to be present in its usual form) or a new set of GApps (which didn't resolve the issue). OnePlus does seem to offer its OTA updates in zip archives though. So I downloaded its latest update (same as what was on the device) and applied it.

That's when the nerdgasm happened.

The "update" was simply a matter of going into the settings, tapping this and that and applying the update. No recovery, no unrooting, no nothing. The update just went like that despite the phone being rooted and just having had TWRP flashed to it. I always wanted this sort of thing, which even the Nexus couldn't offer - having the cake and eating it too. Being able to root the device and muck around with it while still being able to update the device timely without too many hurdles. This fucking thing does it!!!

That is to say, after my initial nerdgasm I did find that it bulldozed over my su binary (effectively unrooting the thing), custom emoji I've set (iOS 12 because fuck Google's most recent emoji set) and some other things. But those are easy to install back, much more so than it would've been to download a whole Android release and dirty flash it, as it was on the Nexus.

Other than that, battery life, dash charging (edit: on that topic, it does remain cool like a cucumber despite getting 15-20W of power jammed into it, quite impressive!), snappiness, the usual jazz.. eh, as I said earlier that's the usual reviewer stuff. But this feature of being able to upgrade the phone while it's modified, that's something which seems to be severely underrated by those.

Oh and during kernel builds, I couldn't quite get the source to work - probably due to my lack of experience with builds of Android kernels - but I did find that this phone actually exposes its kernel config through /proc/config.gz as it should. None of my MediaTek devices do this, so that's something that I found really appealing. Always nice to see when a manufacturer exposes this information to give you a stock sort of config that you can be rest assured will work configuration-wise. And it allows you to see what the stock kernel is actually built with, which again is really nice. I quite like this! It really encourages further development.

My grandmother asked me to help her find an article about a recipe for a chocolate cake. The recipe she wanted was the first result on Google, so I sent her a LMGTFY link (let me Google that for you, a website that writes by itself the word or the sentence). Later on the same day, she said that her laptop was possessed by a ghost.

If I died, I would have one regret.

I once worked in a code base whose messiness would make an oil spill in the fucking pacific ocean look like spilled milk on the floor in comparison.

Naturally, it had bugs. Oh BOY did it have bugs. Most of them were taken care of well enough. Or about as well as anyone insane enough to work in that code could.

There was just this one bug, which I still (un)fondly call "my bug of 2 years". It. Just. Didn't. Make. Sense.

It was written in JavaScript. Naturally. Which by itself, is the metaphorical programming language equivalent of a pile of horse manure. But this bug. It was the guano icing on top of the horse manure cake which is JavaScript.

I LITERALLY spent 2 years trying to find a solution. I woke up at night, thinking of explanations. I had dreams about fixing the damn thing. And I never did.

On the day I left the job, I had to pass it on to a friend (who hasn't solved the fucker yet either).

I hated that bug with all my heart. But..

Now that I think back, all the books I read, all the docs that I scoured, every non working fix I coded and every failed efforts I made on it, eventually made me a better programmer.

So cherish your bugs and issues. Sometimes, they come, not to hurt you, but to help you grow (unless you use JS, those bugs just wanna fuck you).

31st December 2016, I had signed up for devRant.

It's my cake day today. Feels so good to be part of this community, have learned so much, made some of the greatest friends here.

2021 was a mind fuck. Taxing and draining. Very little growth and even less learnings.

I realised that I am in a toxic environment.

Lately, no philosophy, therapy, supplements, activity, work, etc. has been helping me to get back to my original self.

I used to spiral down with a lot of negative self talk and playing the victim card.

Just day before yesterday, I decided to listen to some affirmations on the Tube and that actually helped me bounce back.

I started socialising and stepping out to attend gigs and just be outdoors as much as I could.

My surroundings changed and so did my thought process.

Hence, I made a decision to continue affirmations and slowly change my surroundings, even if that demand domestic relocation.

Things are starting to look positive after a long, loooooong, time.

I also need more sun exposure for my vitamin D3 deficiency and steady dose of serotonin.

I feel lot clear in head and heart. My goals are clearer and I am ready to start working hard and be my original past self again.

I love you all and I really wish you all achive all your wishes and dreams, be happier and healthier in 2022 with ton of success and money.

🍰

Today I navigate the devRant oceans for the 157,680,000 second.

Who knew this place would be still pumping some of the greatest devs I've come to appreciate so many years later, it's not the vibrant place it once was, but it's still full of hidden gems.

Today is my devRant cake day! 🎂

Thanks everyone for making this community so great! This year on devRant has been so enlightening!

Inappropriate experience at work: One of our project managers got arrested one day for fraud. Apparently an employee had been in the middle of an online purchase and walked away from their desk. He happened to see the unmasked entry of the CC info (this was before websites cared about masking sensitive form inputs). I guess the temptation was too great…and he was too stupid to realize he’d get caught…and he jotted it all down. He made thousands of dollars in purchases which, naturally, eventually led back to him.

The same guy, before he got arrested, had made a joke when someone in an office team email said “Feel free to have some cake in the break room.” He replied “No need to do anything to me for the cake.” His first name was “Free”.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

Fun day, lots of relief and catharsis!

Client I was wanting to fire has apparently decided that the long term support contract I knew was bullshit from go will instead be handled by IBM India and it's my job to train them in the "application." Having worked with this team (the majority of whom have been out of university for less than a year), I can say categorically that the best of them can barely manage to copy and paste jQuery examples from SO, so best of fucking luck.

I said, "great!," since I'd been planning on quitting anyways. I even handed them an SOW stating I would train them for 2 days on the application's design and structure, and included a rider they dutifully signed that stated, "design and structure will cover what is needed to maintain the application long term in terms of its basic routing, layout and any 'pages' that we have written for this application. The client acknowledges that 3rd party (non-[us]) documentation is available for the technologies used, but not written by [us], effective support of those platforms will devolve to their respective vendors on expiry of the current support contract."

Contract in hand, and client being too dumb to realize that their severing of the maintenance agreement voids their support contract, I can safely share what's not contractually covered:

- ReactiveX
- Stream based programming
- Angular 9
- Any of the APIs
- Dotnet core
- Purescript
- Kafka
- Spark
- Scala
- Redis
- K8s
- Postgres
- Mongo
- RabbitMQ
- Cassandra
- Cake
- pretty much anything not in a commit

I'm a little giddy just thinking about the massive world of hurt they've created for themselves. Couldn't have happened to nicer assholes.

"Impossible deadline experience?"

When product owners promise delivery dates.

One day, I came back from a two weeks holiday, relaxed. I noticed a teammate missing. "Yes, he took the week off". Sure, why not.

We were working under a bastardized enterprisey version of Scrum (didn't we all at some point?). So we didn't just have a product owner, we had three and an additional "Head of PO". Because enterprises can't live without hierarchies or something. Barely an hour after I came into office, she entered the room and came straight to me. "Your coworker was almost done implementing feature X. You need to finish it immediately. No worries, though, coworker said the rest is a piece of cake".

It wasn't. There was *a lot* left to do, the JIRA task wasn't entirely clear, and the existing code for the feature was so-so (obviously WIP code). I estimated two weeks for the implementation, plus some time to clarify the requirements. When telling "Head of PO" she lost her shit. Screaming things like "this feature is due the end of this week" and "I signed this with my blood!". Well, I didn't, and I made it clear that I hadn't been consulted on this, thus I would not accept any blame in case we missed the deadline.

So I gave my best that week, getting pestered by "Head of PO" all the time. "Is it done yet?", "why does it take so long?" and "your coworker would've been done by now!". Yeah fuck you, too. Not only was I not relaxed any more, I was even more stressed than before my holiday! Thanks, you stupid bitch.

Well, her arbitrary deadline came and the feature wasn't ready. And what happened was... exactly nothing. The following week my coworker returned, who gave me an apologetic smile. "I told her the feature was nowhere finished. And even me, being familiar with the task, couldn't make it in time". We finished the feature together that week, and that was the end of it. So... "Head of PO" either didn't listen or lied to me. She then stressed me to the max right from the day I came back from my holiday. And in the end it didn't even matter.

Again, thanks you stupid bitch, for creating a toxic work environment. Should you ever read this, I'm happy I quit and I hope you miss every single deadline for the rest of your life. Screw you.

The joys of your last day at work, lots of cake and no work to do. As of Monday I will be a proper developer!

I had my last day today, after signing an severance package deal some weeks ago. It has been eight long years in this news media company as a sole web developer.

Leaving it behind feels awesome.

There was cake. There was a greeting written with a marker on the cardboard box the cake was delivered in. There were no speeches.

But my by now X coworkers seemed happy to get cake.

I am so excited to start fresh next year as a developer in a small design firm where there is a lot of care and love and nerdiness.

!rant

Does anyone have an idea about a nice goodbye message to write on cakes for my last day on my summer job?

Requirements:

- Should be short enough so I can write it with a choco pen on 20 cakes of about 10cm each.

- Should be about me leaving (I worked on a terminal application in qt c++)

- Should have something to do with programming

Couple of jobs back we got bought out by that massive shipping company with the red and yellow colors.

We used macs and some high up moron decided it was a good idea to put on domain policy restrictions on our macs, but developers can't work without admin access so if we wanted to keep said admin access, we had to sign a written agreement indicating that we were not allowed to do certain thing, like change our wallpaper or install personal music players, you know like Spotify, which at the time was what most of us used.

Now this was just a nice cherry on the cake of stupid descision that was making me rethink working there. Thanks to the high demand for skilled front ends, it was 11 am when we got this, 3pm I had comnfirmed my interview for the next day.

An hour later our manager called us all in to explain this was BS formalities. Well too fucking late, learn to communicate you dumb shit.

Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?

- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.

Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.

But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!

After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:

- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.

Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.

Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.

I was working yesterday, writing a calculus with sql.
My very great user explained to me the math in Excel. I first though to myself, piece of cake, i got it.
Then I started typing and at the end of the day i had 6 temp tables which at some point need to join with themselves. It was just hilarious. each table had at least 4 millions rows.

Then I started a new query just for validating the output of me very ugly previous queries.
And I fucking found a easier way to get the same output with 3 joins of 3 different tables and a count at the end.

When you love yourself. but hate yourself at the same time.

xD it was a very productive Friday night

Quick and probably duplicate.

One fucking more time someone comes to me and interrupts me, I swear if it's not important, or chitchat, or something easly googlable, or something you could ask literally anyone else or something that isn't even my shit to handle, I will give the unlucky bastard 30 minute lesson to not fucking interrupt me when Im trying to focus first half of fucking day to do one fucking thing.

What the fuck.
What, should I print big fucking A2 formated poster and stick next to my workstation "If you came here to interrupt me, think if you really need to"?

E:
And no, I dont know where the fuck is your excel file.
And no, I dont give a shit when Im coding that there is cake avail for workers today.
And no, for fucks sakes I dont have time for chitchat, I have deadline on me once again and Im doing something I dont have much expirience in so please leave me fucking alone.

We were 4 dudes developing this little disposable material management system for a course in college, and we had to write documentation and present on the last day of class. Second week into the course and one dude goes rouge, not taking phonecalls nor replying to messages, just goes to class and does not get together with us to make progress. Neddless to say the other three of us had to do all the work. Fast forward to last day, all of us wondering where this dude could be. He shows up 6 mins before the presentation, already late, reads like 3 pages of the doc, and decides he will be the lead presenter.

>Mfw he takes over and starts bs'ing the whole thing.
>Mfw he mentions the possibility of the system to be extrapolated to manage salami in a butchery.
>Mfw the professor seemed to have swallowed all that bs like cake.
>Mfw we get an A, including him.
>Mfw I have no face

a bet:
this birthday, i will get:
lemon glutenfree cake (if any) because mom can't have gluten and sister likes lemon cake. i hate both of those. but that's irrelevant as it always was.

if any, then gifts will be anything except cigarettes which is basically the only thing within price range they're willing to spend, that i would actually be happy about.

birthday is just an artificially glorified ordinary day. and i'm not the type to do hysterics to artificially glorify it. and it's fine. but then, why are they artificially glorifying it while unwilling to actually glorify it properly, as in, glorify it for me?

pick fucking one. artificially glorify it, in which case, FOR ME, or just don't give a fucking shit same as i don't.

but why are you artificially glorifying it for the purpose of ignoring me and glorifying everything exactly in spite of me, without even being aware that you're doing that?

like seriously, what? make your "i love not you, but my daughter" day, as an extra to her birthday. i don't give a shit, i'm happy you have a nice relationship. but doing all of the "i love my daugther day" shit on my birthday, AND PRETENDING IT WAS DONE FOR MY BIRTHDAY, FOR ME, and being sad about me being sad that all you did "for me" was in fact for yourself and for everyone else, that's the combo that gets me.

"oh why u making me so sad by being so sad that i ignored everything you like and kept telling me you like for the past X years and i just ignored it because it's not my nor your sister's preference?"

guess why, you fucktard. how about you ignore the day next time instead of making it an unconscious (that's the worst, that they don't even realize it) mockery of the day.

"oh why are you sadand shitty feeling that we made this bullshit ignorable "celebrate you" day about ignoring everything that celebrates you, and made it into the opposite instead? why are you so demanding and cruel?"

SHUT. THE. FUCK. UP.
go have a walk with your beloved daughter and please ignore me as you always do.
just leave me the fuck alone.

"We've got a new opportunity for you."
I'm a fucking rookie. I didn't know the meaning of this sentence. Suddenly, I become the "IP PBX expert" of the society.
"-Okay, it's some networking shit, I thing I'm good at networking shit. Piece of cake.
-Okay great, you have one month to learn how this thing works, because we WILL provide this kind of service."
Damn.
I spent one month learning this shit on my free time, printing RFCs and living in the fucking MATRIX to not fuck up on the very first day doing that, just in case something on the customers' network fucks with the PABX or something like that.
Oh yeah, I forgot: I'm paid 80% of the minimum wage because I am actually not qualified to do my job and I'm spending one week a month to learn how to IT (some french weirdness I think, if not, maybe it's the germans' fault. Also yes, 100% legal).
Today, they announced me that they "changed their mind".
I'm pissed.

Me: I should divide my project in small parts. It will be a piece of cake.
Also me: (on last day of submission) 76 commits in 34 minutes.
*Face Palm* 🤦‍♂️

One day I helped another teacher with setting up his backend with the currently running Nginx reverse-proxy, peace of cake right?

Then I found out the only person with ssh access was not available, OK then just reset the root password and we're ready to go.

After going through that we vim'd into authorized_keys with the web cli, added his pub key and tried to ssh, no luck. While verifying the key we found out that the web cli had not parsed the key properly and basically fucked up the file entirely.

After some back and forth and trying everything we became grumpy, different browsers didn't help either and even caps lock was inverted for some reason. Eventually I executed plan B and vim'd into the ssh daemon's settings to enable root login and activate password authentication. After all that we could finally use ssh to setup the server.

What an adventure that was 😅

Went on this 2 day business show...

Next to me a 100 inch tv... 4k quite awesome jittery video at points ? Codec or cable is wrong...

What was on the right of my stand ... To the cake.

"How to make money online"

He proceeded to state things like I now have 20mill my dream car etc ...
*Me trying not to laugh\be disgusted*

His power point ... Well a 10 year old can do better looks built in 1995

People were buying into it ! How the fuck does someone who has apparently 20mill give such a shit design to people and they listen...

I seriously wanted to go on and say... Don't listen to this fraud this, piece of shit snake oil salesmen.

But I didn't... And.. I regret it. On the bright side ... My stand had the shortest setup in the whole place bet by far the best websites!

It's not a real dev regret but it's related to it: Not being able to fix a price or a value for my skills.
It's a real regret.
Just coming out of college I have tried my hand at freelancing at found it real hard to fix a value for what work was offered because I just found it weird to fix a monetary value on something that I've done for free for my entire life ( at school and uni I mean).
To make it worse my first experience was with a grad student who wanted me to complete her project.
Now being from India, I know that we have a stereotype of doing work for a lower price.
But this girl took the cake.
She wanted me to create a custom Image classifier using tensorflow.
It had to train with live images and then detect those images in the live video feed.
It's quite simple but still training the basic network(which would be used to just detect features) would take a decent amount of time and effort.
No pre trained models was also a prerequisite for her.
After hearing all her requirements I asked her what price she was willing to pay.
She said 50$ lump sum.
Being really confused as to what to say to that I just stopped replying.
To this day I have no clue what would be a reasonable price to quote a client like that.
After that I just continued dealing with people I knew personally and am currently doing that as an internship. But entering the proper freelancing system again has become a kinda weird thing in my head now, since I have no clue as to what price to put on my skills.
Is there any advice that any of the more experienced people would give?
Also consider the fact that I'm relatively fresh out of college and have no corporate experience.
Even if you've read my rant and have no advice it's okay. I guess this is a path of self realization after all.

#Suphle Rant 9: a tsunami on authenticators

I was approaching the finish line, slowly but surely. I had a rare ecstatic day after finding a long forgotten netlify app where I'd linked docs deployment to the repository. I didn't realise it was weighing down on me, the thought of how to do that. I just corrected some deprecated settings and saw the 93% finished work online. Everything suddenly made me happier that day

With half an appendix chapter to go, I decided to review an important class I stole from my old company for clues when I need to illustrate something involved using a semblance of a real world example (in the appendix, not abstract foo-bar passable for the docs)

It turns out, I hadn't implemented a functionality for restricting access to resources to only verified accounts. It just hasn't been required in the scheme of things. No matter, should be a piece of cake. I create a new middleware and it's done before I get to 50 lines. Then I try to update the documentation but to my surprise, user verification status turns out to be a subset of authentication locking. Instead of duplicating bindings for both authentication and verification, dev might as well use one middleware that checks for both and throws exceptions where appropriate.

BUT!

These aspects of the framework aren't middleware, at all. Call it poor design but I didn't envisage a situation where the indicators (authentication, path based authorisation and a 3rd one I don't recall), would perform behaviour deviating from the default. They were directly connected to their handlers and executed after within the final middleware. So there's no way to replace that default authentication scheme with one that additionally checks for verification status.

Whew

You aren't going to believe this. It may seem like I'm not serious and will never finish. I shut my system down for that day, even unsure how those indicators now have to refactored to work as middleware, their binding and detachment, considering route collections are composed down a trie

I'm mysteriously stronger the following day, draw up designs, draft a bunch of notes, roll my sleeves, and the tsunami began. Was surprisingly able to get most of previous middleware tests passing again before bed, with the exception of reshuffled classes. So I guess we can be optimistic that those other indicators won't cause more suffering or take us additional days off course

Oh hey, I missed my devRant cake day. And I don't know when it actually was because it displays as 1/2/2019, so it could be January 2nd or February 1st. Can we have a proper date format?

Badly lahmayo eggsdee

Jokes aside, while I am a sociable person, I don’t feel the need to go and hang out with my friends - and they don’t demand I do either. I’ve been just fine with the daily interactions at school and that sort of stuff, so the balance is already biased for me. I do however hang out a lot on Discord in various communities and enjoy the social interaction I get from there as well.

As a result, the dev life takes the bigger piece of the cake, but in my case it’s not a bad thing. Which is how it should be at the end of the day - do what feels best for you.