"Oh no this platform is serverless"

I hate this "serverless" term.

How does a cloud platform run serverless?

HOW?!

"yeah but like we don't have to run updates and manage the underlying stuff and can thus deploy stuff serverless"

NO.

THERE ARE ACTUAL SERVERS RUNNING IN ORDER TO RUN THIS PLATFORM.

YOU CANT RUN THIS FUCKING PLATFORM WITHOUT ACTUAL SERVERS.

HOW WOULD IT RUN THEN, ON FUCKING STARDUST?!

IT. IS. NOT. SERVERLESS. AS. LONG. AS. SERVERS. ARE. INVOLVED. AT. SOME. LEVEL.

Considerations when looking for a tech video course:

5%: Does it have good ratings
5%: Is it priced reasonably
90%: Does the narrator have a smooth soothing voice with an intonation which keeps me dreamy & enchanted, yet with an energized articulation, like a cup of Jasmin tea with clover honey on a dreary Sunday afternoon.

The content may be very good, but if I have to sit through 30 hours of material, you better tickle my ears the right way.

Dev: "Ah, I finally fixed that code I was working on the other day and got it pushed to staging!"

Almond: "Ah, great! What was the issue in the end?"

Dev: "It was an odd one - it wasn't actually my code that was the issue, there was a bunch of other code getting in the way."

Almond: "How do you mean?"

Dev: "It kept complaining about something called a "unit test" failing - so after a while I found the right unit tests, deleted them, and now it works great!"

Almond: "..."

Hahaha and an entire industry hates one person or company

I'm I the only one who wake's up feeling guilty if a day goes by without coding?

What does the year 2030 have in store for us?😂

My daughter will be a software developer (I believe)... she counts from 0 sometimes. :D

New desk happy

Really loving the instant legacy code being added to our new project by devs who think they are too good to follow our peer review process, yum... today I found out that there are two different implementations of an API endpoint that does the same thing running in prod, in two different places, because the guy who wrote the second one wasn't aware that the first one existed and didn't let a second developer look at it before he pushed it to master.

Thought about @Floydian while reading this 😂😂

Long rant ahead. Should take about 2-3 minutes to read. So feel free to refill your cup of coffee and take a seat :)

It turns out that the battery in my new Nexus 6P is almost dead. Well not that I didn't expect that, the seller even explicitly put that in the product page. But it got me thinking.. why? Lithium batteries are often good for some 10k charges, meaning that they could last almost 30 years when charged every day! They'd outlive an entire generation of people!

Then I took a look at the USB-C wall charger that Huawei delivered with this thing. A 5V 3A brick. When I saw that, I immediately realized.. aah, that's why this battery crapped out after a mere 2 years.

See, while batteries are often advertised as capable of several amps (like 7A with my LiitoKala 18650 batteries that I often use in projects), that's only the current that they can safely take or deliver without blowing up. The manufacturer doesn't make this current rating with longevity in mind. It's the absolute maximum in current that a given battery can safely handle.

The longevity on the other hand directly depends on the demand that's placed on the battery. 500mA which is standard USB 2.0 rating or 1A which is standard USB 3.0 rating, no sweat. The battery will live for at least a decade of daily charges and discharges like that no problem.

But when you start shoving 3A continuous into a battery, that's when it will suffer. Imagine that your current workload is 500mA and suddenly you get shoved 6 times that work upon you. How long would you last?

Oh and not only the current is a problem, I suspect that it also overvolts the battery to maintain a constant current all the way till the end. When I charged my lithium cells with my lab bench power supply, the battery would only take a few milliamps when it got close to the supply voltage. Quick bit of knowledge: lithium cells are charged at constant current first, then when the current drops below that, it continues at constant voltage - usually 4.2 or 4.35V depending on the battery. So you'd set your lab bench power supply at 4.2V 500mA. But in that constant voltage mode, as the battery's voltage and the supply's voltage equalize, the current drops because the voltage difference becomes lower. Remember, voltage is what causes current to flow. Overvolting at the supply to stay in constant current mode all the way till the end speeds this process up but can be dangerous and requires constant monitoring of the battery voltage.

So, why does Huawei and a bunch of other manufacturers make these 3A power chargers? Well first it's because consumer demands ever more, regardless of the fact that they can just charge at 500mA for the night (8h of sleep) and charge a 4000mAh battery from 0 to 100% no problem. Secondly it's because sometimes you need that little bit of extra juice fast, like when you forgot to plug the damn thing in and you've got only 30 minutes in the morning to pour some charge into it.

But people use those damn fucking things even when they go to bed, making that 3A torture a fucking standard process!! And then they complain that their batteries go to shit?!

Hopefully this now made you realize that the fast charger shouldn't be used as a regular charger ^^

I have this one friend who thinks he is a tech guru just because he plays video games a lot and started to study cs for one year. Now he got a job as sysadmin and it is funny to hear him brag about the job in front of non-tech people because he sounds like a CSI Cyber episode, just throwing tech words at the people and I know that he talks bullshit.
But I have to admit, he knows how to sell himself. Probably that's how he got the job in the first place because it cannot be his experience.
Yesterday he called me, to help him edit something on a linux server. I told him "To edit the file type 'vi FILENAME' and then you can edit. I have to go now, I have a meeting." :]

People in my office sing me praises for what I can do with Linux even though I joke with them that “I have no idea how to do that - but give me half an hour and an internet connection and I’ll figure something out for you.” I even once specifically said in response to my boss commenting on my skills, “You do realize that I just like…google stuff when you ask me to do something with Linux that I don’t know how to do, right?”

But his praise didn’t change at all. There was no “Wait, that’s all it is?”

Instead, he said “Yes, but the fact that you think to do that - and that you know exactly how to phrase your searches and how to sift through the results to get the right answer, and you then integrate what you’ve learned and use it going forward - is still so much more than any of the rest of us can do. To you, it’s “just googling stuff,” but it’s still a unique and valuable skill you bring, so don’t shrug off the compliments so cavalierly, okay?“

And this was coming from an executive with an MBA. Don’t undervalue your googling skills, kids. It’s not lying if you know you can figure it out.

Inspired by Max Payne's
"The Things That I Want"

I present Polaroidkidd's
"The Things That I Love"

A sleeping girlfriend.
A terrace in a warm summer night with a power outlet.
A cold beer.
A pack of cigarettes.
A working WiFi.
A pair of charged Bose 35 QuietComforts.
A minimal electro playlist.
A peace of mind, attainable solely through solitude.

A jab at PHP
*hides*

My uni implemented Bluetooth beacon based attendance monitoring.

Raspberry pi + cloned beacons = 100% attendance.

Idiots 😂

(Edit for clarity: app on smartphone, Bluetooth beacon in each room)

Is there a good offline C# compiler for iOS? I want to program on the go as I am not by my pc a lot.

My dual monitor setup!

Old but gold 😄😄

What's with some devs around here posting their stories of doing shitty things like they're heroes or something?

Oh, you hacked your former boss and destroyed data because he did something you didn't like?

Oh, you tried to work smart, but then essentially defrauded your client by claiming you had to rewrite the app for another platform?

How many other ones?

It's shit like this that make it harder for the honest developers out there to get a client to actually trust us, and that trust is so important for both sides of a contract.

How can a client who was burned by one of these douche bags trust when another developer actually quotes a rewrite of a code base that is fundamentally flawed?

How about a business partner of the one who was hacked. What if they're as honest as can be, but heard the horror story, and now refuses to entrust anything to their developers?

It makes all our jobs harder and makes us all look like shit.

And here you are, posting it up for those precious ++'s.

Fuck you. Either shape up or do us and your clients a favor and choke on your keyboard.

Sorry !dev-related, But:
In our grocery store there‘s a 0.5L coke for 0.99 under that there‘s a 1L for 0.98 and around the corner there’s a 1.5L coke for 0.99
WTF?

Every time I feel Im getting my act together (at work) there is some AWS service which I know nothing about and that totally kicks my asss

Geeez the dev ops side of things is a total void for me..

Most incompetent co-worker: 6 month ago me 😤

But why can’t Android Studio work out of the box?
I want to develop, Not mixture with gradle and stuff...
Time for a Power Nap.

This was me when i tried react.

"Opps.. I'm sorry, but you have insufficient rights to open this Ticket."

Well. You know what? I AM THE FUCKING SYSTEM ADMINISTRATOR YOU CUNT!
YOU HAVE INSUFFICIENT RIGHTS to restrict me access to that fucking ticket!

"Oh. In that case, go ahead."

THANK YOU. FUCKING PRICK.

Being tempted by a job offer as an iOS dev that has full (paid) training. Not a fan of apple but heard swift is a nice language (assuming it is swift).

I've spent the last year and a half learning the react way as my first dev job, not sure whether it's beneficial to keep on this path or diversify.

Me, being a lowly junior dev, had the honor of being in a same group chat with a big corporation devOps team.
Finally ready to play with the big boys!!

*opens chat*
DevOps 1: "so we need to remove the CSS cache from our clients computers."
DevOps 2: "ok, well... just delete the server cache"

*watching in awe as they all try to figure out why it's not working*

This continued on for a while...
Until my boss had enough laughs and giggles and put an end to this stupidity :D

Imagine, you get employed to restart a software project. They tell you, but first we should get this old software running. It's 'almost finished'.
A WPF application running on a soc ... with a 10" touchscreen on win10, a embedded solution, to control a machine, which has been already sold to customers. You think, 'ok, WTF, why is this happening'?
You open the old software - it crashes immediately.
You open it again but now you are so clever to copy an xml file manually to the root folder and see all of it's beauty for the first time (after waiting for the freezed GUI to become responsive):
* a static logo of the company, taking about 1/5 of the screen horizontally
* circle buttons
* and a navigation interface made in the early 90's from a child
So you click a button and - it crashes.
You restart the software.
You type something like 'abc' in a 'numberfield' - it crashes.
OK ... now you start the application again and try to navigate to another view - and? of course it crashes again.
You are excited to finally open the source code of this masterpiece.

Thank you jesus, the 'dev' who did this, didn't forget to write every business logic in the code behind of the views.
He even managed to put 6 views into one and put all their logig in the code behind!
He doesn't know what binding is or a pattern like MVVM.
But hey, there is also no validation of anything, not even checks for null.
He was so clever to use the GUI as his place to save data and there is a lot of parsing going on here, every time a value changes.
A thread must be something he never heard about - so thats why the GUI always freezes.

You tell them: It would be faster to rewrite the whole thing, because you wouldn't call it even an alpha. Nobody listenes.
Time passes by, new features must be implemented in this abomination, you try to make the cripple walk and everyone keeps asking: 'When we can start the new software?' and the guy who wrote this piece of shit in the first place, tries to give you good advice in coding and is telling you again: 'It was almost finished.' *facepalm*
And you? You would like to do him and humanity a big favour by hiting him hard in the face and breaking his hands, so he can never lay a hand on any keyboard again, to produce something no one serious would ever call code.

Leaving work with a task only partly completed just guarantees my mind is going to obsess about it all night and my dreams will be plagued with lines of code.