Details
-
AboutProblem solver and lover of clean code.
-
SkillsJQuery, JS, SharePoint, Knockout, CSS, C#, MsSQL,
-
LocationBurnham-on-Crouch
Joined devRant on 4/16/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I wish companies stopped doing interviews n just stuck to "u have X days to finish this test-project" and judge me by the code/design/architecture
Im a deer to headlights when it comes to interviews -_- I'd even forget my own name on a bad day ffs4 -
Highlights from my week:
Prod access: Needed it for my last four tickets; just got it approved this week. No longer need it (urgently, anyway). During setup, sysops didn’t sync accounts, and didn’t know how. Left me to figure out the urls on my own. MFA not working.
Work phone: Discovered its MFA is tied to another coworker’s prod credentials. Security just made it work for both instead of fixing it.
My merchant communication ticket: I discovered sysops typo’d my cronjob so my feature hasn’t run since its release, and therefore never alerted merchants. They didn’t want to fix it outside of a standard release. Some yelling convinced them to do it anyway.
AWS ticket: wow I seriously don’t give a crap. Most boring ticket I have ever worked on. Also, the AWS guy said the project might not even be possible, so. Weee, great use of my time.
“Tiny, easy-peasy ticket”: Sounds easy (change a link based on record type). Impossible to test locally, or even view; requires environments I can’t access or deploy to. Specs don’t cover the record type, nor support creating them. Found and patched it anyway.
Completed work: Four of my tickets (two high-priority) have been sitting in code review for over a month now.
Prod release: Release team #2 didn’t release and didn’t bother telling anyone; Release team #1 tried releasing tickets that relied upon it. Good times were had.
QA: Begs for service status page; VP of engineering scoffs at it and says its practically impossible to build. I volunteered. QA cheered; VP ignored me.
Retro: Oops! Scrum master didn’t show up.
Coworker demo: dogshit code that works 1 out of 15 times; didn’t consider UX or user preferences. Today is code-freeze too, so it’s getting released like this. (Feature is using an AI service to rearrange menu options by usage and time of day…)
Micromanager response: “The UX doesn’t matter; our consumers want AI-driven models, and we can say we have delivered on that. It works, and that’s what matters. Good job on delivering!”
Yep.
So, how’s your week going?2 -
Something that I absolutely hate about the IT industry:
When a feature is deployed the chain is like this:
Dev -> Testers -> QA -> Product Manager -> End User
But when things break in production and management wants to yell at the staff... only the devs get the heat and no one else, as if they weren't responsible for anything at all.
Really fucking hate it.7 -
The company I work for now has no PM, no UI/UE. It’s just me, because I’m a full-stack engineer. I originally thought that full-stack was just front-end and back-end. I kind of want to run away.7
-
Honestly idk but that one chapter from mythical man month, "Plan to Throw One Away", stuck with me:
"Where a new system concept or new technology is used, one has to build a system to throw away, for even the best planning is not so omniscient as to get it right the first time."
In my current project I've seen this play out, initial development was very prototype-ish and just not well designed but when we got a somewhat decent state we had to continue with it instead of starting again and doing it properly. And now the consequences of that are hitting, progress for new features is incredibly slow, the software is very error prone, a bunch of dead code all around, ...10 -
Why is it that EVERYTIME before going on vacations I am loaded with work, that production problems are sent to me and must be fixed ASAP, and that everyone needs me right away all the time. Manage your time stop sucking out mine 😤
-
I quit my job. Today was my last day. Feels so good to get rid of the toxic workplace attitude.
I really wish someday managers understand the difference between an estimate and deadline, will reduce the pressure on devs.
I'm glad that I can take a break and explore what I want to do next 😀12 -
"full stack" means "you'll be doing everything from gathering client requirements through data architecture up to the UI design and of course implementing all of it"
"backend" means "you'll be coding everything from database through server-side code and client-side code including html and css"
"we need you on-site all day every day" means "we have no idea how and why we should use repositories with remote access despite being a company developing an internet app, and we don't trust that you would be working anyway"
"interesting challenging projects" means "the same boring crap as every other company, running on an incredibly botched and dezorganized codebase".
"competitive pay" means "actual pay is around 1.5 times the minimum allowed pay, and everything else is being siphoned off into (stupid and useless) 'benefits' like massage and fitness discount coupons"
"friendly collective having fun at numerous company events each years" means "it is mandatory for you to participate on our weekend drinking retreats but you'll only find out when we fire you because you're 'not a team player' after you refused to participate on those"9 -
Well, I got it. The new job that is so from December first I really am a C# developer :)
We just have to agree on the salary. I will at least get more then I have now (as support technician) and well it's kinda a dream come true.2 -
Sometimes I wonder if I'm truly a good programmer, or if I can just google things better than the average bear.4
-
New random background image for my homepage.
Dunno where I found my inspiration, just opened inkscape and started clinking the mouse7 -
Sad story!
She : i am breaking up with you because I love another guy.
Me : since when?
She : 6 months.
He : why you didn't tell me then?
She : we have updated our privacy policy!!2 -
(Q: How much are you allowed to Google as a developer?)
“You’re allowed to Google as much as you want. This is not school, you’re employed to solve a problem. Nobody cares whether you Google for the answer or remember the answer from another Googling.”15