My current project at work: purchase verification, aka anti-fraud.

It's been two weeks, and my boss is flipping out because it isn't done. A robust anti-fraud solution. in two weeks. And he thought one week was a little much.

like, fucking really?

There are companies whose entire service is helping combat fraud. and he wants this done in a bloody week?

What makes me laugh through my tears of frustration is that the company that moved into the previous office? Yep, anti-fraud. Their entire business model is providing anti-fraud services to other businesses. They even tried selling him on it when they moved in. Bossman sales guy turned it around and sold my freaking desk out from under me instead.

But like. They're a small company: they had 9 people when they moved in, and were looking to add three more, so a total of 12 people. (I totally considered jumping ship, but their stack was too different.)

So. Bossman wants me to replace 9-12 people and their entire business in a fucking week. Yeah.

"Oh, but it's just sms verification" says he. What he also wants is the ability to flag users as fraudulent, have sticky verifications so they can't bypass them by backing out, have email checks as well as sms, have deferred verification to allow collecting required info (e.g. phone number), verification fallback, lockouts, manual admin whitelisting, admin blacklisting, and different rules per merchant and rule groups for affiliates to apply to all of their merchants, and of course the ability to customize those merchant/affiliate anti-fraud rules. But he shortens this gigantic list to "I want sms verification," despite actually asking for all of the above. I don't want to know about the mental gymnastics and/or blindfolding required to equate the two, but he's nuts.

Yeah.
All of that.
In a goddamn week.

And I get chewed out when it isn't done? Fuck off.

Go build me a goddamn 5m ft^2 castle out of basalt and marble using only your toothbrush and a rusty garden trowel, and have it done in a week. No outsourcing.

talk about ridiculous.

What is the most ridiculous over-the-top "startup" thing you've been the victim of as a developer?

Alternatively, what kind of weird startup luxury would you absolutely love to have at your company?

For me, at various companies I've worked at/visited:

1. Hammocks & fatboy beanbags. Current employer has a "Netflix & Chill" corner with nice couches, and a small gym. I have encountered isolation/flotation tanks at the office of one of our partners... which is cool, but over the top in my opinion.

2. A fully automated aquaponics garden in the lunchroom. Was awesome, until some fish died and started to rot.

3. One hoverboard per employee, at previous employer. I splashed hot chocolate milk in an arc over three desks. A coworker broke his ankle while watching me spill chocolate milk.

4. Daily scrum standup meetings, on socks, in a big bouncy castle. Not kidding. Fucking ridiculous... (but secretly fun). That employer also had spiral slides between all floors, a tiny half-pipe with tiny skateboards, and someone who rode a unicycle way too much. It was a fucking circus. Stuck in the office of a Fintech company.

5. Soldering bench (at my current company), with drawers full of breadboards, servos and electronics components. Completely unrelated to my work, but it was my idea. It's just great to build a simple kits together with another random coworker while brainstorming platform features & refining specs... much better than meetings with bullshit slides.

6. Unlimited energy drink. Developed a serious caffeine habit (15-20 cans a day), and almost got a stomach ulcer. Not beneficial to employee health.

7. I really do love working from home + unlimited holidays. Just being able to honestly say "fuck you guys, I'm gonna get drunk and play games today", and at other times working until 4am and sleeping in the next day, or taking a week to work in a park in Rome... It makes work truly feel like my favorite hobby. Combined with a good sprints and curious/ambitious people, you can easily track productivity anyway.

WEB FUCKING THREE

Ok, some of this shit is interesting, let's get that out of the way:

Crypto - great for doing illegal things, great for financial speculation, interesting mathematically. But as likely to replace actual currency as I am to replace the fucking Queen.

NFT - should be written on the headstone of humanity. Entirely fucking useless, planet-roasting bro-wank dressed up as a revolution in...pretending to own shit. The only difference between a Bored Ape owner and my nephew pointing at a castle and insisting that it's his, is that he isn't thousands and thousands of pounds out of pocket by doing so.

Metaverse - AR and VR have been around before this dogshit rebrand, and they'll outlive it.

No, it's not that. It's that we now have a new species of parasite - the "Web3/Metaverse" LinkedIn guru insisting that this shit is even needed, let alone the next big thing.

Web 2.0 was a stupid fucking term alright, but it did represent a new generation of technologies that were badly needed, and adopted by the entire community. Web3 is a bunch of shit that some cunts think they can get rich off, so insist that we need. I wouldn't even give a fuck but I've already spent hours of my life explaining to clients and peers that this is UTTER FUCKING BOLLOCKS, there's no need for a blockchain in your app, there's no need for a blockchain in virtually anything. Yeah if you want some fucking 3d in your app or your page I'm your man, but if you keep saying 'metaverse' I'm going to fill it with easter eggs.

None of this shit was needed before and none of it is needed after. Have you looked at web3 games? It's Steve Buscemi asking 'how do you do, fellow computer games?', it's a fucking gambling app pretending to be something a human would do. Clash of Clans and Candy Crush already cornered the market for that type of fucking mug, right now you're making the Candy Crush business model look responsible and efficient. You CUNTS.

Believe me I didn't code today... full day with my daughter... video recording for her youtube channel... science experiments... castle... and .. and ...

I hate people who think that building software is all about one click away and generating things. I got told to complete the task faster than the speed of light.

Fancy me some rant time? Let's name that cunt, "Bob".

"
Hey Bob, I got questions for you. Are you sure you were in your mum's womb for 8-9 months? Are you the kind of twat who honk at people as soon as the traffic light's turning green?

Building software takes time, the CI/CD takes time, TestFlight takes time, approvals from the Google Play store take time, approvals from Apple App Store connect take time, Unit testing takes time and every fucking thing you can name takes time!

It's just like sex, nobody wants to be with someone who can only last in bed for 0.000000000001 nanoseconds, the longer, the better, (but not too long).

It is also like building houses, which takes months to build not hours. As from my experience so far, something tells me that you are not the kind of person who would understand how to build a house but a sand castle which takes only hours to build.

Relentlessly, you bombarded me with a pile of bollocks and a pile of nonsense is not going to fasten up the compilation of the software.

"

I think that watching Netflix's The Punisher has made me a better developer.

10/10 would binge again

"How useful was your CS degree and why?" - I studied CS at university, my education always was incredibly useful.

Firstly, the knowledge you gain in itself is useful. Furthermore, we explain and understand the unknown in terms of the known. Thus, the more you know, the easier you learn new things.

But secondly and more importantly, university teaches you *how* to think. In a structured way, like a scientist or engineer. To see the bigger picture.

I originally wanted to end here, but I've read a couple of entries doubting the usefulness of any CS degree.

Our profession isn't all that different from others. It is, however, relatively young. How's this for an analogy: We're still in the stage of building sand castles. That's fine, and can be self taught. But in years to come we'll want to build bridges and sky scrapers, which are not just "sand castles scaled up". Our sand castle knowledge won't help us here. Sky scrapers need entirely different materials and a good understanding of architectural statics.

Can you still teach that yourself? Maybe. Will a formal education with a degree be useful and generally more trusted? I bet.

Ah yes, the sound of me still working at 2:30am. Marvelous.

Gotta grab a coffin and a castle and pretend im dracula, wouldnt make much of a difference.

sigh, managers and their sand castle empires

Jar of the day! He knows what’s goin on at Redmayne Castle!

//long rant ahead!

I need to plan a Wiki with SharePoint for not connected Sites.
Im now in dispute with my CoWorker since 3 Months, this is how the conversation goes. My two bosses are involved in this and also unhappy about SharePoint.

[C refers to CoWorker, M for me]
C: Hey, we finished SharePoint with Selfservice Storage Rooms. They even have a Wiki.

M: Okay cool, will check it out

C: Well we need to also plan the Wiki inside, I already asked our Department Head and he agreed, that you will be the one.

M: Okkkkaaayy, normaly it's your job to do such things, but welp, I will look into it, if we can work with it.

(2 Weeks pass)
M: I checked SharePoint out and tested everything. The Wiki is a Nogo, we need a other solution or programm for ourself a Wiki Integration/Engine. Did you maybe check out Confluence? It has also a SharePoint integration plugin.

C: We wont do Confluence, too expensive (already overspent the budget for SharePoint in six digits 🤬). Also we wont add to SharePoint Custom Code, it needs to stay standard.

M: Thats impossible, SharePoint Wiki is shit and also handels sites just like documents, no brain behind! Also you overspent the Budget and now it's my Problem?!

C: You need to do the best out of it.

(3 weeks passes and we get a meeting with the department heads)

M: Alright I made a UseCase and documented where the essential flaws are in SharePoint Wiki and why we cant use it.

Boss: Ok if it's impossible to use, then we will stay on our Fileserver for Documents and wont use SharePoint.

M: Thats not my Point, my statement is, as status today, SharePoint Wiki is not the right solution, code or buy software to it.

Boss: We will do a Prove of Concept, if it doesnt work then we will aboard it.

M: Well it is only some missing essentials, like hierarchy and Groups for the Pages, Example Confluence has this. If we could built in this features in SharePoint, everything would work out.

C: (angry) I told you that we wont use Confluence!

M: (calm) I said we need Features, not Confluence. Please mind the consent.

(3 weeks passes, and one more meating with bosses)

M: alright here again is a analyses, why already in Theory the current SharePoint Wiki wont work. It's already flawed in the core.

Boss: Yea SharePoint is crap, I checked out confluence and thats a real Wiki.

C: Well I dont know anything about Confluence and never looked at it. But if SharePoint is a fail we need the Proof of Concept.

M: Why do we need to do a Proof of Concept, when it already doesnt work in Theory! Thats nonsence and unlogical.

Next meeting will be in 4 weeks and I will give him the FUCKING PROOF OF CONCEPT. I will be a Bastard and build behind CoWorkers back a Confluence Wiki to show the Departmentheads how to built it right.

I hate CoWorker now, he makes a part of my loved Job a hell, I will goddamn cuk Coworker to space, that fucking Cukatron of lazyness and shit 🤬. I provide the Solutions and you just say no, how dafuq will the project advance, if you always say NO! Are you so unflexible and fixed on your Castle of Ignorancy!

When a client wants you to build a castle and demands an unrealistic timeline then tries to rip you off thinking that software development is a child's play. you drunk mate?

I haven't touched Flash for at least six years, but people still endorse me for my Flash skills on LinkedIn. Because they wouldn't see a duck from a castle. Ignorant f*cks.

Fuck you, BouncyCastle. I really like you but the way you have documentation. It's annoying. Nice name. Cool project.

Here, I'm write Java Docs for JUnit tests! For every damn test case!

So damn less documentation even SO said mind your own business! It's been more than 15 hrs. Not a single reply! I died a little today. They have examples but they are not really "examples". No passion at all for documentation!

You should watch and learn from AssertJ docs. OMFG @joel-costoglia sets standards for code style and docs before pull requests. The examples are LOTR themed for god's sake. I'm not asking for fluent API. I just want docs. What class does what. A simple program structure required.

Dyn4j, deeplearning4J have wonderful docs. Why not BouncyCastle?!!!!!

I really cannot see why there still isn't an API in Java where I can get an hashing algorithm without having to catch a checked exception.

Granted, Bouncy castle is a top library. But of you just have a small application with a single method wanting to hash a few values... It's so nuts and unnecessary.

So what do you do in the catch block? Either throw a checked exception (because without that hash your app won't work), or calculate a replacement. But if it were that easy, I wouldn't have needed a hash on the first place.

I really wonder what the java developers had in mind.

Same with IO exception. I'm beginning to like python more and more.
And, of course, kotlin.

The vibrations of thee knight from the castle shall oscillate under frequency required thou who shalt dare to conquer with thee energy; shalt acquire thee vibration

#Suphle Rant 2: Michael's obduration

For the uninitiated, Suphle is a PHP framework I built. This is the 2nd installment in my rants on here about it.

Some backstory: A friend and I go back ~5 years. Let's call him Michael. He was CTO of the company we worked at. After his emigration, they seem to have taught him some new stack and he needed somewhere to practise it on. That stack was Spring Boot and Angular. He and his pals convinced product owner at our workplace to rebuild the project (after 2+ years of active development) from scratch using these new techs. One thing led to the other, and I left the place after some months.

Fast forward a year later, dude hits me up to broach an incoming gig he wants us to collab on. Asks where I'm at now, and I reply I took the time off to build Suphle. Told him it's done already and it contains features from Spring, Rust, Nest and Rails; basically, I fixed everything they claimed makes PHP nonviable for enterprise software, added features from those frameworks that would attract a neutral party. Dude didn't even give me audience. I only asked him to look at the repo's readme to see what it does. That's faster than reading the tests (since the docs are still in progress). He stopped responding.

He's only the second person who has contacted me for a gig since I left. Both former colleagues. Both think lowly of PHP, ended up losing my best shot at earning a nickel while away from employed labour. It definitely feels like shooting myself in the foot.

I should take up his offer, get some extra money to stay afloat until Suphle's release. But he's adamant I use Spring. Even though Laravel is the ghetto, I would grudgingly return to it than spend another part of my life fighting to get the most basic functionality up and running without a migraine in Spring. This is a framework without an official documentation. You either have to rely on baeldung or mushroom blogs. Then I have to put up with mongodb (or nosql, in short).

I want to build a project I'm confident and proud about delivering, one certified by automated tests for it, something with an architecture I've studied extensively before arriving at. Somewhere to apply all the research that was brainstormed before this iteration of Suphle was built.
I want autonomy, not to argue over things I'm sure about. He denied me this when we worked together. I may not mind swallowing them for the money, but a return to amateur mode in Spring is something I hope I never get to experience soon

So, I'm wondering: if his reaction reflects the general impression PHP has among developers globally, it means I've built a castle on a sinking ship. If someone who can vouch for me as a professional would prefer not to have anything to do with PHP despite my reassurance it'll be difficult to convince others within and beyond that there could be a more equipped alternative to their staple tool. Reminds me of the time the orchestra played to their deaths while the titanic sank