AboutSomebody's got a recording of McCoy Pauley? Who?
SkillsSurvived brain death behind black ice.
LocationUpper Drainpipe Australia
Joined devRant on 3/29/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
This is meant as a follow-up on my story about how I'm no longer and Ada developer and everything leading up to that. The tldr is that despite over a decade of FOSS work, code that could regularly outperform a leading Ada vendor, and much needed educational media, I was rejected from a job at that vendor, as well as a testing company centered around Ada, as well as regularly met with hostility from the community.
The past few months I have been working on a "pattern combinator" engine for text parsing, that works in C#, VB, and F#. I won't explain it here, but the performance is wonderful and there's substantial advantages.
From there, I've started a small project to write a domain specific language for easily defining grammars and parsing it using this engine.
Microsoft's VisualStudio team has reached out and offered help and advice for implementing the extensions and other integrations I want.
That Ada vendor regularly copied things I had worked on, "introducing" seven things after I had originally been working on them.
In the almost as long experience with .NET I've rarely encountered hostility, and the closest thing to a problem I've had has been a few, resolved, misunderstandings.
Microsoft is a pretty damn good company. And it's great to actually be welcomed/included.2
Long story shot,
I was the coder of a time machine and a bug took me 10 minute to the past. 10 minutes later I got to the same bug and got teleported again. This continued a while. I woke up later.4
I walk into the kickoff meeting today. The first part of this project had 5 developers and a project manager. Former project manager handled communication and sheltered us from bullshit. We built an amazing piece of software in a very short time. Customers were so amazed that they decided to reboot the project, boost the funding by several million, and let us go again. They specifically requested the same team.
Now the team looks like this: the neediest tester guy, a UX lady that doesn't have any UX background, an agile "visionary", a project manager that doesn't understand how development works, a solutions architect, 3 COTS platform specialists, a devops specialist, and an account lead. They have booked all kinds of workshops and other shit to kick things off.
So development capacity is only 60% of what it was. Management ratio was 1:5 before. Now the management ratio is 9:3. The new project manager thinks developers should be on more customer calls and responding to all customer emails during sprints. We already built this system and devops pipelines end to end. The COTS people, solutions architect, or the UX person can't program. They want us to magically convert this custom application into one based on COTS. What we need to do is make the rest of the business processes that we omitted, integrate known feedback, rework the backend, build better automated testing, improve logging and reporting, add another actor to the system, add a different authentication method, and basically work through the massive backlog.
How do they think this is going to work? Do they think we can download a custom engineered enterprise grade software system from Microsoft and double click all the way to customer satisfaction? The licenses alone are too much for the customer on an ongoing cost basis. I guess we can discuss it during the agile team-building weekend at some remote lake that the team "visionary" has set up. For the sake of fuck.
Like development isn't hard enough. Hire two more developers and lose all of the dead weight. Get a project manager that won't let the trivial shit roll down on us. What the fuck.5
Account manager: "We somehow managed to take unmaintainable spaghetti code for money again. This is a great opportunity for you."3
FUUUUUUUUUUUUUUUCCCCCCCKKKKKKKKKKK LOOPBACK. Fuck it right in the dickhole. Fuck IBM for paying the salary on this piece of shit. Fuck all of the copy pasting I have to do, fuck the fact that it never knows what fields my type will or will not have, fuck the 4 different versions of the docs they have for each version of this dumpster fire of a framework. This is the dumbest codebase I have ever worked with, and I hate every minute of it. One last fuck, it is for the guys who came before me and chose this for our companies server. Fuck you!2
The last two frontend devs I interviewed.
He had 15 some years of experience, but couldn't answer our most basic of technical questions, we stopped asking after the first couple.
Based on a technical test I got the impression that he couldn't distinguish between backend and frontend.
Which lead him to talk about arrays. I shit you not he droned on about arrays for five minutes.
"I have experience using big array, small arrays, breaking big arrays into littler arrays and putting arrays inside other arrays."
Never been in an interview situation where I've had to hold back laughter before. We refer to him as the array expert.
His technical knowledge was lacking, and he was nervous, so he just waffled. I managed to ease his nerves and the interview wasn't terrible after that, but he wasn't what we were looking for.
This was a phone interview.
It started off OK he was clearly walking somewhere and was half preoccupied. Turns out he was on his way back from the shop after buying rolling papers (we'd heard him in the shop asking for Rizla), and he was preoccupied with rolling a joint.
We started asking some basic technical questions at which point he faked that he'd seen a fight in the street.
We then called him back five minutes later you could hear him smoking "ah, that's better". After that the interview was OK, not what we were looking for, but not bad.
Top tip: If you require a joint to get through a phone interview, roll and smoke it before hand.17
There are times when being "friendly neighbor it guy" pays back.
I have a neighbors, their son is little less intelligent than average person after being injured in accident, I help them from time to time. He gets the pc trashed with adware, usual stuff, they ask me to clean it up.
Recently I broke my arm. They offered to cook for me until I recover to full health... Seriously, that's huge help when you live alone and spend most time working. I'm glad to have them.
Wanted to share with you guys, there are people who appreciate your help with their pc and can give back if you're in need.4
Fuck ever working for a company that doesn't know shit about the worth of a developer ever again.
> be me
> just got my first class masters in Soft Eng that I worked hard as fuck to get
> get a job for a pretty well known medical company here
> offered a bit less than what I was expecting but fuck it, it's a job straight out of uni doing what I want to do
> stay for a year with no bonus programme, no pay review, no objectives, no perks, literally fuck all
> see literally every other position in the company be promoted and actually supported from IT & the developers
> get the hail mary recruiter "you'd be great for this role" linked in DM
> follow it through and go to the interview
> nailed it
> comes to negotiating a starting salary and they actually laugh at my current rate and immediately raise it by about 30% with bonuses, reviews and all that shit occurring regularly
> later virgins5
My new mobile development teacher just admitted he has never learnt git or any other VCS, I asked him what he does when shit happens and he just said,
"I just have a folder for each version backed up to Google Drive"
This is the guy that's teaching us? Surely as a teacher you should be setting a proper example and using good practises....?16
When you start something, many things come across your way. Some are good, some are bad but the experience that they give is really useful for proceeding forward in future.
"WTF IS THIS?"
Exclaimed the developer that had never bothered to learn proper architectural patterns such as MVC in his web development are, failing to grasp the folder structure that was open in front of him, gasping at those strange php files that contained not only namespace declarations....but requires, uses and GASP! CLASSES!!
"That is Laravel my dude, built that in Laravel some time ago. Been running without an issue ever since." I mentioned as I reminded him that i had provided documentation had he ever needed to update or work with the application(currently it just needed a static page, which is why he had the app open in his editor)
See children. This is why you don't just learn a tool and never bother to learn something else.
Y'all should have seen how confused this dude was.
Das what yo dumbass gets.
OAN I am getting placed into more hardcore Business Intelligence roles.
The ammount of statistics and overall math required is....
Damn near 0. Data Scientists are full of shit. Anyone in an analyst role is full of shit.
I would know.
I IS one.14
My job title should be Fireman.
Seriously, the only reason I think my boss makes such stupid fucking decisions and starts fires everywhere is because he knows I have to and can put them out.
Infuriatingly blood boiling or compliment? Can’t decide...8
My head is melting. Does anyone have a colleague who constantly complains about missing specs, documentation, project organization, bad processes and procedures? Everything needs to be planned. Not a single small code change can be done without reviewed details. 10min job becomes a week-long session of whining and dabbling.
You give the guy a small task and at the end of the day nothing is done. Just page after page of written documents and lists in Word and online notebooks. Version numbers, meaningless measurement results, latencies etc. And all you asked was "could you just fucking fix this one thing and quickly compile and check it". But no. There must be a review and at least 10 people need to be called into conference. Someone needs to approve everything just so that he can later move to blame to others. "Yeah I know it's not working but I showed you the code and you reviewed it!". Yes, you did, but other people have work of their own so sometimes you need to tie your own shoelaces.
And sometimes finally there's some work done. All indentations are shit. There’re code changes everywhere just because the guy didn't like the previous smaller, compact and logical code. The code doesn't even compile properly anymore. And if you complain, the reason is "there's no proper reviewed and stamped process description, so I cannot know if a variable is supposed to be 10 characters long. Besides 200 character long variable names are much more descriptive". For fucks sake.
Some coders should've gone to work in some tax office basement.9
So i've spent the day:
a) Finding evidence (again) of product not doing their job, to send on to one of my managers. So we can again discuss why she's still here.
b) Explaining to my iOS developer that although all the devs are in agreement that 2 of them are not pulling their weight and shouldn't be here ... they will definitely still be here because management actually want to keep our multi-timezone setup as they see it as beneficial. We, do not.
c) Having a meeting with another manager, in a different department. (Backstory, a member of their team has had many complaints filed against them by various members of the building, including one from my team). To let them know that my employee felt like you ignored her concerns and complaints and are going to allow this person pass their probation without considering the implications.
I hope to actually find some time in the reminder of the day to actually achieve something, rather than just telling skidmarks that they are in fact skidmarks.
... but probably won't due to 3 hours of pointless back to back meetings, where we answer the same few questions every week.
I really do love being a tech lead. So refreshing.
If git was written in english or in ancient greek it made no difference. It's everything counter-intuitive and you have just to learn commands by heart and google the errors. Because nothing makes sense, even if you know how it works and you used it for years6
Casually Client Team Asked A Developer Team,
What is your favorite game?
**Blame Game**, One of the junior developer murmured.
Pro tip: If you are a junior, or senior but new at the company, don't start your conversations with:
"We're doing X wrong. At my previous company we did / at school I learned /in this book I read / according to this talk I watched, the right way to do X is ..."
"I'm curious why were doing X this way. I'm used to doing it differently."
I love flat-hierarchy teams, and people who think about flaws in procedures and proactively try to improve the tools we use are awesome, but the next kid walking up to me yelling we use git flow "wrong" will be smacked in the face with a keyboard.
If you come to me with curiosity and an open mind, I'll explain, and even return the favor by behaving the same way when I'm baffled by your seemingly retarded implementations.
Maybe we can learn from each other, maybe discover that "how I learned it" is sometimes good, sometimes bad.
But let's start with some social skills, not kicking off into every debate with a stretched leg and a red face.24
Today at 'Derp & Co' a fellow co-worker decided that had duplicated data on Relational DB is good!
- Dev: 'but what if we have 2 companies in diferents groups?''
- co-worker: 'Just call it company A and Company B'
- Dev: 'but... this is not what...'
- co-worker: 'Trust me Dev, is the easy way'
I want the professional way, not the easy (and damn wrong) way :(, I can't improve myself like this.
Also, dead line is here too... TT^TT
Last sprint and still with doubts about the DB structure.12
coolest thing I ever built?
except it's not cool, and not sure if it's a career at all.. not so good on a thing, just some knowledge here and there..
now I am sad about my life1
Awsome feeling when you teach some one from non tech background about the tech jargons and they understand..1
Long time, no rant. Why is facial hair so difficult to control? How do people even grow beards without looking like hobos all the time? Do I have to make some sort of sacrifice to a dark and malevolent entity?
Believe me, it's so much easier to keep on top of shaving body hair than taming face fur. Especially because your facial hair is, you know, on your *face* which means it's very visible. You can't hide it if you mess up. Unless you decide that wearing a balaclava is a good idea when going outside, like when going grocery shopping. Generally that isn't received too well though.17