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
Search - "test dev"
-
Developer (master's degree, -bleeping- smart guy, no kidding) was bragging on how he made a piece of code 3x faster (with the usual pinch that the original dev was incompetent) and spent nearly 6 weeks working on it (wrote his own parallel-foreach library because Microsoft's parallel library was "too slow").
I was the original dev and he didn't know I had my own performance counters where I broke down each stack (database access, network I/O, and the code logic).
Average time was around 5ms (yes milliseconds) and worst case was around 10 seconds. His '3x improvement' was based on the worst test case, which improved by about a second. Showed our boss my graph (laughed out loud, said 'WTF', other curse words) and the dev hasn't spoken to me in weeks (I say 'hi' in the hall and he keeps walking)
Take that master's degree and high IQ and shove it.17 -
Fuck today was weird.
Today I received almost half a million on my bank account. 😯
Someone changed the ancient cryptic billing system. My user account at work has id 32 in the database, and the dev referenced the size of the creditor id instead of the of the value of the ids itself, and they're u32 ints... So ALL the money moving through our platform was accidentally transferred to my associated bank account.
For all the unit tests we have, this bug tumbled right through.
And no one at finances thought a transfer that big, to a backend dev they know by name, was suspicious — with almost no money going to other creditors...
That worries me a bit. The fact that this shit can happen, even at high test coverage, just because someone mindlessly did a wrong autocomplete or something.
Of course I will send it back... after two weeks and a few hundred € of interest.12 -
Project handover:
"Mmh okay, so what about test coverage?"
Dev: "zero"
Team taking the project "why???"
Dev: "You don't need test if you write perfect code"
Silence in the room... Followed by awkward laugh.18 -
Before an interview prepare a list of questions for them, they expect it!
My list to give inspiration:
Describe your company culture? - if the response is buzzword heavy, avoid.
What’s the oldest technology still in use? - all companies have legacy systems but some are worse than others
Describe your agile process? - a few companies I’ve interviewed with said they are agile but it’s actually kanban
Are developers involved with customers?- if they trust you to talk to customers you can infer trust to do your job ( I’m sure others will disagree)
Describe your development environment?- do they have such a thing as dev, test and prod?
These are the only ones I can remember but should give others a bit of inspiration I hope 😄9 -
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: "..."11 -
My employer has a dev studio in Cali.
The office is gigantic.
It has amenities.
It has a stocked fridge full of iced coffee, energy drinks, and apparently wine.
All the devs have totally enviable hardware.
And they probably earn twice what I do, or at least 50% more.
Yet they write absolute shit, never test their code, and push broken updates every day, often marked as "ready for final testing." Their codebase is full of hacks and guesses and stale cruft and worst practices. I wrote a rant recently about one of their fuckups, which involved 18 million Facebook errors per. day. So that should give you some idea as to the quality of their code, and their level of can't-be-bothered.
Again, they make 50%-100% more than I do.
Their whiny lead dev is bloody lazy when it comes to building things correctly, and totally prefers to half-ass everything and complain instead. He probably makes 150% of what I do, doing like 25% as much work, and maybe 10% as well. Doesn't quite compare though, as he's a Unity dev, not a backend dev. So his work isn't as critical.
akagdkdafavskakeuxbfh.
Bloody pisses me off.
"But their cost of living is higher!"
THEY SHOULDN'T EVEN BE EMPLOYED.rant root gets angry this is the short-short version overpaid crap-tier devs but i got too angry this was originally to be a comment22 -
New senior dev joined the project today.
Senior dev: "There's no way for me to test my changes before I merge this into develop"
Me: "Can you at least run our test suite?"
An hour later the develop branch is fucked and everyone who has merged it locally has pages of red errors splattered across their screens whenever they run any tests.
Start looking into what the fuck is going on.
Notice that all the errors are related to changes the new guy made.
Ask him if he ran the tests..
Senior dev: "Nah they wouldn't catch anything locally "
Stare at the stream of red text running down my screen.
Normally I wouldn't care but we were trying to prepare a release... RUN THE FUCKING TESTS ASSHOLE.9 -
Job interview goes really well. Senior Dev 90-100k.
Ok, so for your "test" write up a proposal for a web based bulk email sending system with its own admin panel for building list, tracking emails, and with reporting.
I write up an estimate. Low ball the absolute fuck out of it because I'm trying to get a job. Know a few good libraries I can use to save some time. Figure I can just use sendmail, or PHPMailer, or NodeMailer for the emailing, and DataTables Editor for a simple admin CRUD with reporting. Write the thing up. Tell them they can have it in LAMP or Node.
Come in at 36 hours.
Then these fucking wanks told me they wanted me to actually do the project.
My exact response was:
"I bill $50 an hour, let me know"
They did not let me know.
Young devs, jobless devs, desperate devs. I've seen a fair amount of this. And for the right job I might go as high as maybe 4 - 6 hours of unpaid work for some "programming test". But please be careful. There are those who will try to exploit lack of experience or desperation for free work.15 -
Coolest project: I once worked for a customer who hosted an exhibition for a few thousand visitors in a big event arena in Stockholm.
They didn't want to use the existing ticket reading system on the arena so I had to build my own application compatible with barcode scanners (they said this about one week before the event).
It wasn't a complicated application to dev but with the tight deadline and no time to actually stress test it, it was the coolest thing to see hundreds of people streaming through the ticket station flawlessly.
Day 2 of the event I built a simple web application so I could see the flow rate of read tickets while I sat in the arena pub with a beer.6 -
"I'm just trying to replicate {ticket-1234} so I can write a quick hotfix."
- "Oh, it doesn't work on dev."
- "So... I have to test on stage?"
- "It doesn't work on stage either."
- "Uh, on prod?"
*office laughs*
We're doing it live folks.2 -
5th June is World "Environment" Day..
Reaction of Software Engineer -
Which one? Dev, Test or Prod?
😂😂2 -
Newspaper: This CEO is one of the top entrepreneurs in the country, a true tech visionary shaping the future.
--- 3 months previous ---
Lead dev: O2 have said they are will pre-install the app on all their Androids but they need documentation from us.
CEO: documentation? on what?
Lead dev: Our unit test coverage, bugs found / fixed, security scan results, performance assessment, if and where its storing any data etc.
CEO: Ah were not doing any of that crap, bloody unit tests, its not necessary, tell them no.
lead dev: ..... eh ok
O2: *approved*
... true visionary, well done to everyone involved.3 -
Being told I’m not experienced enough to get a senior dev job I interviewed for.
Even though I aced the first 4 interview rounds, the tech test feedback was “the best solution they had ever seen”, and I’ve been a senior dev for 25 years.
Time wasting assholes.3 -
!dev
Nearly had a crash today driving home and almost had a heart attack. Apparently my car had the heart attack for me and started doing. A speaker test.
So I'm contemplating what just happened and my car's speakers start going BEEEEP BEEEP BOOOOOOOOOOOOP (Subwoofer).
Then the radio came on and switched to a Spanish station.
I looked it up, apparently I had entered diagnostic mode on the infotainment system when I was fiddling with the wheel buttons as a stress relief.
Long story short, the diagnostic mode informed me that my car runs Windows ME!
I would like a new car please, kthxbye.6 -
I'm convinced code addiction is a real problem and can lead to mental illness.
Dev: "Thanks for helping me with the splunk API. Already spent two weeks and was spinning my wheels."
Me: "I sent you the example over a month ago, I guess you could have used it to save time."
Dev: "I didn't understand it. I tried getting help from NetworkAdmin-Dan, SystemAdmin-Jake, they didn't understand what you sent me either."
Me: "I thought it was pretty simple. Pass it a query, get results back. That's it"
Dev: "The results were not in a standard JSON format. I was so confused."
Me: "Yea, it's sort-of JSON. Splunk streams the result as individual JSON records. You only have to deserialize each record into your object. I sent you the code sample."
Dev: "Your code didn't work. Dan and Jake were confused too. The data I have to process uses a very different result set. I guess I could have used it if you wrote the class more generically and had unit tests."
<oh frack...he's been going behind my back and telling people smack about my code again>
Me: "My code wouldn't have worked for you, because I'm serializing the objects I need and I do have unit tests, but they are only for the internal logic."
Dev:"I don't know, it confused me. Once I figured out the JSON problem and wrote unit tests, I really started to make progress. I used a tuple for this ... functional parameters for that...added a custom event for ... Took me a few weeks, but it's all covered by unit tests."
Me: "Wow. The way you explained the project was; get data from splunk and populate data in SQLServer. With the code I sent you, sounded like a 15 minute project."
Dev: "Oooh nooo...its waaay more complicated than that. I have this very complex splunk query, which I don't understand, and then I have to perform all this parsing, update a database...which I have no idea how it works. Its really...really complicated."
Me: "The splunk query returns what..4 fields...and DBA-Joe provided the upsert stored procedure..sounds like a 15 minute project."
Dev: "Maybe for you...we're all not super geniuses that crank out code. I hope to be at your level some day."
<frack you ... condescending a-hole ...you've got the same seniority here as I do>
Me: "No seriously, the code I sent would have got you 90% done. Write your deserializer for those 4 fields, execute the stored procedure, and call it a day. I don't think the effort justifies the outcome. Isn't the data for a report they'll only run every few months?"
Dev: "Yea, but Mgr-Nick wanted unit tests and I have to follow orders. I tried to explain the situation, but you know how he is."
<fracking liar..Nick doesn't know the difference between a unit test and breathalyzer test. I know exactly what you told Nick>
Dev: "Thanks again for your help. Gotta get back to it. I put a due date of April for this project and time's running out."
APRIL?!! Good Lord he's going to drag this intern-level project for another month!
After he left, I dug around and found the splunk query, the upsert stored proc, and yep, in about 15 minutes I was done.1 -
Dev: Breaks unit tests
Same dev: Merges it to master anyway
Same fucking dev: Can't merge to master coz CI is screaming at you? Merge locally and FORCE push.
Me: Hi, I'm blocked. I can't merge to master coz of this failing test, can we get on a quick call and figure this out?
Same fucking fuckface dev: *after 3 fucking days* Yeah, I don't know why it's failing.. the results seem to be inconsistent..
Jesus Christ. I am so close to leaving this side-project because of the frequent shit I have to go through with this fucking idiot.
God I wish I didn't need the money.14 -
Me: Hi Guys, theres no docs on our custom push notification / deeplinking implementation. I've tried to work backwards from a QA testing doc to add new links. Can someone tell me if this is all ok? It seems to behave a little weird.
Dev: Looks ok, but we've moved to the braze platform for sending notifications. You'll need to trigger braze notifications now. Test that it works ok with that <confluence-link>
*hour later*
Me: I've tried the debugging tool, both with my payload and one of the samples from the link. It displays on the phone, but tapping it doesn't trigger the deeplinking.
Dev: No it works, try one of these <screenshot of samples I used>
*hour later*
Me: Tried it again on the real device to make sure, as well as on develop and master. Not working with those samples or mine.
Dev: No it does. It comes in here in this library <github link to line of code>
Me: ... Nope, debugged it, it doesn't get passed the next 'if' check on the next line as its missing a key/value. The whole function does nothing.
Dev: Oh do you want to send a braze notification?
Me: ..... you told me I had too .... yes I guess.
Dev: ok for a braze notification it works different, send this <entirely different sample no where on the link>
Me: ...... but ..... this is only for braze notifications ..... why .... all the samples have deeplink url's .... but they don't ....... are you ..... FFS!!!!! !@#?!
(╯°□°)╯︵ ┻━┻
┻━┻ ︵ヽ(`Д´)ノ︵ ┻━┻
(ノಠ益ಠ)ノ彡┻━┻
┌П┐(ಠ_ಠ)1 -
“Your time zone is not my concern” - manager of the backend team
I asked if there’s another way for us to get test data into QA. That doesn’t involve us staying on until 9pm to get a backend dev to modify the db manually, everyday.6 -
My first dev job. Me and another guy get hired at the same time. He will be the lead dev, and I’ll be the junior dev on a long term project. Project gets delayed (and eventually canceled, but that’s a different story), so the lead dev decides to give me programming challenges to test my skill level. I successfully complete the challenges, but they aren’t up to his standards. Belittles me in front of our manager. Afterwards I ask him to show me how he would have done it. The dude can barely type let alone show me the way it should be done. I say nothing to the manager.
A few weeks pass, it’s clear the project we were hired for is canceled, so we are given other work. They task the lead dev with porting the company website to Wordpress so non-devs can alter content. They chose Wordpress mainly because the lead dev said he is familiar with it. Two weeks later, no progress has been made. They ask me if I can do it, and I do it in 2 days including additional functionality that was requested. Manager asks me why I thought lead dev couldn’t do what I did. I said, “I don’t think lead dev knows what the fuck he is doing. I don’t think he knows how to program.” Manager says, “Huh.”
Several months later lead dev is still there, but has yet to work on any projects with any success. They finally let him go.
Glad to finally get that off my chest.6 -
I was assigned a girl that's new to the industry (but with a master's degree).
I had high hopes, as people told me she is quite a curious fellow. As I am just a junior Dev with 2 yrs of experience Ididn't know if I could handle her.
We started working on a project. Which was a change request for a previous project I had developed. I gave her 2 days to read and understand the functional requirements of previous project and this CR. Then explained everything too.
Then I gave here another 3 days to read the previous design document to learn how this code worked.
I asked her multiple times if she has any questions. She said she got everything. Cool.
One week goes by. We start to code the CR while she is shadowing me. I explained why we chose one of the two approaches. And why we are making any of the changes. She as usual nodded in agreement.
I asked her to create Unit test cases.
She couldn't write even one. So, I quizzed her, she knew nothing about the project! Nothing at all!
FUCK!
I wrote down the test cases in short hand and told her to document it (by reffering previous UTC). She wrote the test cases in short hand in the document. And she reused the previous document and did not even clean it out.
After fixing the document I asked her to execute them. But nope, she doesn't even know how the application flows for this project. FML.
It took her 3 days to write and test 8 test cases.
Now she is assigned to me in another project. This one is more complicated. And I gave her a function skeleton to complete. I figured that it will take me 15 minutes so let's give her a day. But nope. 3 days no progress.
I get it someone might not be quick to grasp something. But you know what grinds my gears? That even after this you act like a know it all! Fuck! For someone who hasn't worked with her she is the most dilligent developer.
How the fuck does someone survive masters and suck so bad!22 -
My setup at work as a juniour dev. Got a month ago a 3rd monitor (the left), because I'm working on some backend services and had to test them with a touchscreen. Now only the frontend dev and I have 3 monitors in the whole company 😁6
-
micromanager: "Quick and easy win! Please have this done in 2-3 days to start repairing your reputation"
ticket: "Scrap this gem, and implement your own external service wrapper using the new and vastly different Slack API!"
slack: "New API? Give me bearer tokens! Don't use that legacy url crap, wth"
prev dev: "Yeah idk what a bearer token is. Have the same url instead, and try writing it down so you don't forget it?"
Slack admin: "I can't give you access to the slack integration test app, even though it's for exactly this and three others have access already, including your (micro)manager."
Slack: "You can also <a>create a new slack app</a>!" -- link logs me into slack chat instead. After searching and finding a link elsewhere: doesn't let me.
Slack admin: "You want a new test slack app instead? Sure, build it the same as before so it isn't abuseable. No? Okay, plan a presentation for it and bring security along for a meeting on Friday and I'll think about it. I'm in some planning meetings until then."
asdfjkagel.
This job is endless delays, plus getting yelled at over the endless delays.
At least I can start on the code while I wait. Can't test anything for at least a week, though. =/17 -
QA: did you test the app first?
Dev: Yes, I test all my code all the time.
*QA crashes the app within first 5 seconds.*4 -
"Your resumé looks really good. We would really like to hire you. But you need to do this completly job unrelated test/coding challenge first."
----
"Is the test Android related?"
"Yes"
*Opens Test* -> "what ist the complexity of this function (written in c)"
*Scrolls*
"Implement algorithm xyz in Go lang"
*Closes test and breaks something*
----
"You will need to Code on a small Android projekt so we can see how you work"
"OK, how much time will i need to plan for it?"
"Our lead dev decided to make it small so its only 4-5 days."
----
What is it with all this stupid hiring test these days? And what do these recruiter think?8 -
!dev
Me *downloading some weird linux distro to test in VirtualBox - I only do this once a month for like 1 hour*
my brother: Oh my god! Are you downloading something again? Moooom he is downloading something non-stop
every day:
my brother *watching some series/YouTube videos/playing ping-sensitive multiplayer games - all the fucking time, everything he does all day is this + eating and sleeping*
me *retrying multiple times to load anything, including devRant* 😒😠9 -
I started this new freelance project where I am building some android libraries for the client. Anyways, during meeting I was about to present my results and suddenly backend seemed to be down. I looked into the round "are your servers down?"
Team Lead: "Yeah our cto, also our only backend dev, is developing a new feature."
Me: "Okay but why is production down?",
Team Lead: "Ah dont worry we always test on production. We have a pretty solid hardware, we will even upgrade it soon!"
Me:"... How about you just separate your stage environments and have a develop environment?"
Client: "see, this is where our strength is. We dont need a develop stage we have very strong hardware and our backend is fully in PHP"
Thanks God I'm a freelancer3 -
This week Im firing a guy who I hired 5 weeks ago. I cant take it anymore. I setted up a nice environment for him and he keeps taking whole day sometimes two or three to do a 2 hour task. He came from electrical engineering background and never had a software dev job. As a person hes more creative type not logical based type. I dont have nor patience nor resources nor time to teach him basics that be could google but simply doesnt have the mindset to do. Sorry bill gates not everyone can learn how to code, or at least not everyone should.
Advice to other people hiring new hires: test the shit out of them before hiring, dont hire from gut. This guy was giving out a nerd vibe, but the only nerd thing that he has is nerdy puns, other than that as a software dev he know less than I did when I was 12 years old.25 -
I have to start my best moment last year with a confession: I moved from Dev to Test half a decade ago. Naturally I do a lot of automation. My Best moment was when Dev said my automation code is so well structured that he wants to work on that and not an the production code anymore. Gave me that warm "still got it" feeling 😊2
-
Indian web dev company (during the interview)::
We follow standards
Me:: Hey, can I get the project's github link so that I can fork it, do my tasks, run test cases, push and, make pull request that you can review, run integration test, and finally merge.
Indian web dev company:: What?? Here's the ftp credentials.
Me::12 -
>> this === rant
<< true
At beginning of this year, I only knew HTML, JS, and CSS so I just applied for offers like "Jr Apprentice Dev in Front-End"
In a interview call, the woman told me that they will send me a test asking about my JS and HTML5 knowledge.
When I look in my inbox, the mail subject says "Back-end Test".
Then I call the woman:
Me: "Hello, I have received the test mail, but maybe it's wrong. I applied for a Front-End position and the test is about backend! "
She: "Do you have skills in JS and HTML5?"
Me: "Yes!, and CSS3"
She: "Well, the test is about that. JS, jQuery, and HTML5"
Me: "..."
Me: "Sorry, that languages are Front-End. In the subject say 'Back-End' and Back-End is PHP, SQL, MySQL, Java, .Net... I don't know nothing about that. I only know HTML, JS, CSS."
She: "It's the same"
Me: "I sorry but it's not the same. Fron-End is client-side, what users sees. Animation, colors, FXs, buttons, forms... And Back-End is server-side, what users doesn't see."
She: "Well, JS, HTML, and CSS is backend for us. We call it that way too"
Me: "Sorry but that is wrong. I invite you to read some basic info. Now I am confused"
Of course that I am not confused. That idi0t was wrong.
Perhaps recruiters should take some info about areas where they are recruiting... (:T)3 -
Me passing time on the weekend
Random call from unknown number
Turns out it's the manager
M: hey , how is your weekend going ...
Me: nothing much ... Whatsup ?
M : yeah well , we wanted to push some minor adhoc fixes as some clients wanted it urgently
The Devops folks need developer support . Can you pitch in and monitor
Me : I'm not aware of what changes are going , i don't think i can provide support
M : don't worry it's minor changes , it's already tested in pre prod , you just need to be on call for 30 mins
Me : ugh okay .. guess 1 hr won't hurt
M: thanks 👍🏽
Me: *logs in
*Notices the last merged PR
+ 400 lines , implemented by junior dev and merged by manager
*Wait , how is this a *minor* release...
*Release got triggered already and the CI CD pipeline is in progress
*5 mins later
*Pipeline fails , devops sends email - test coverage below 50%
Manager immediately pitches in ...
M: hey , i see test coverage is down , can you increase it ?
Me: and how do u suppose I do that ?
M : well it's simple just write UTC for the missing lines ... Will it take time ?
Me : * ah shit here we go again
Yeah it will take time , there are around 400 lines , I am not aware of this component all together
Can you ask junior dev to pitch in and write the UTC for this
*Actually junior dev is out on a vacation with his girlfriend
M : well he's out for the weekend , but
as a senior dev , i expect you to have holistic understanding of the codebase and not give excuses ,
this is a priority fix which client are demanding we need this released ASAP
Me : * wait wat ?
---
I ended up being online for next 3 hours figuring out the code change and bumping up the UTC 🤦🏾9 -
Fuck software assurance.
Fuck functional specifications, fuck software requirements, fuck V-model bullshit documentation, fuck integration test plans.
Fuck trying to shoehorn waterfall requirements into what clearly was an interative development.
Fuck me for being a single dev handling all this bullshit by myself.3 -
Me as Junior Dev doing mysql first time, specifically INSERT test data to test db, sucess on first try.
My Senior co-worker says: WOW, Baby's first INSERT...... that sounds so wrong out of context xD -
!rant
Our lead dev in the company seems to be a smart guy who's sensitive about code quality and best practices. The current project I'm working on (I'm an intern) has really bad code quality but it's too big an application with a very important client so there's no scope of completely changing it. Today, he asked me to optimize some parts of the code and I happily sat down to do it. After a few hours of searching, profiling and debugging, I asked him about a particular recurring database query that seemed to be uneccesarilly strewn across the code.
Me: "I think it's copy pasted code from somewhere else. It's not very well done".
Lead Dev: "Yeah, the code may not the be really beautiful. It was done hurriedly by this certain inexperienced intern we had a few years back".
Me: "Oh, haha. That's bad".
Lead Dev: "Yeah, you know him. Have you heard of this guy called *mentions his own name with a grin*?"
Me: ...
Lead Dev: "Yeah, I didn't know much then. The code's bad. Optimize it however you like. Just test it properly"
Me: respect++;2 -
for 2019 I want to be the very best dev
that no one ever was
to code them all will be my test
debugging is my cause
I will travel across the net
searching wide on tor
each singleton to understand
the power of the code
devmons its you and me
you know its our destiny
devmons
you're my best friend
and our firewall will stand
Devmons!13 -
Im going to fucking murder the QA team if they don't stop sender bullshit issues!
QA: hey dev, there is an error with attached files.
Me: okay what's the issue?
QA: it's just a random file that gets attached. Can you fix it by the end of the sprint(tomorrow)?
Me: I need to investigate it a bit before I can tell you how long it will take, how can I reproduce it?
QA: idk, it was just there.
*several hours of testing later*
Me: I've tried to cause the 'issue' on my local server, the test server and the live server. But I haven't seen it and I have no clue what could cause it.
*30min. before I go home*
QA: dev you have to fix it before you go home! Because we have some other important issues you have to fix tomorrow!
FUCK YOU AND YOUR IMAGINARY ISSUES I'M GOING HOME1 -
Woke up this morning with a fuck this shit mood. I need to write test specs for a system I don't know shit about, and it seems no one who work with this system wants to talk to me, so I gave up and started devranting and reading a game dev book. Fuck this shitty job.2
-
Huge dev-team presentation today with YouTube livestream link available to all clients.
Management wanted us to test our laptops, connections and cables to the bone, so that every computer will work 100% while the stream is running.
You know what didn't work?
The goddamn streaming camera device.1 -
Dev: My VM is not working. Something is wrong with VM.
Me: Have you made any changes to the code?
Dev: It shouldn't matter my VM is not working.
[I go and check the Dev's VM.]
Me: ಠ_ಠ The build output literally states your unit tests failed -
My PM once inserted test data directly into the dev database [ We do have an admin panel ].
Took screenshots of what was not working properly with the imagined data.
Posted them on the WhatsApp group.
Greets me in the fucking morning with "I WROTE TEST CASES YESTERDAY".
FTW -
Greatest thing just happened.
Get a ticket about orders not being processed in our webshop. Angry customer. Critical!!!!
Starts troubleshooting. Nothing has changed in the code recently, was working just fine yesterday. Works locally and on test server. Hmmm...
Take a chance. Writes back to customer: “there! Try to place an order again” without changing anything.
5 minutes I get back “awesome! Everything works again and all previous orders have appeared. Good work!”.
Happy customer. Happy dev :)
Fin7 -
I spent four hours just getting my dev environment working again today.
Whenever I switch branches on this project, I keep to run a script that does migrations, seed data, test db setup, static test info, etc. etc. etc. It takes 12-15 minutes to run.
Today, that script failed.
Apparently one of its steps requires running some of the project's code to produce valid objects. Makes sense. However, my ticket involves breaking a crapton of models (removing accessors) which I've already done, and then patching the behavior, which I haven't. Which means a lot of things are currently broken. Makes sense why the script fails.
However, I can't run the script on a different branch and then switch back because that simply doesn't work (for reasons), so I needed to find some workaround. I eventually did, but every attempt cost me 12 minutes.
Today was not fun, and certainly not productive.
I wonder when they're going to fire me 😅7 -
Had a job interview for a front end dev (Involving a technical test). After couple of days, recruiter says - Unfortunately they say that you are too focused on best practices so they want to pass.3
-
Basically a senior dev that felt attacked because I (still in (IT-) school) could solve his 'oh so hard' programming test 'with ease'. He then went on and wanted to hear one specific answer from me on a very broad question. I (obviously) couldn't read his mind, so he started using that to make me look bad in front of the recruiter.
What a nice working environment...5 -
You have to integrate company A system with company B.
You look up B`s api documentation, write the necessary code, test it thoroughly. Done
__________________________________
A wild dev from B has appeared!!!
------------------------------------------------------
him > you cannot use this SDK to implement this solution. You must use a different one...
You > (coming back to him after scouring through the docs) . Ok which sdk is it then? I can't find it anywhere. Could you send it to me pls?
him > I don't kbow, my knowledge doesn't go that far. Send an email to the dev department.
After sending the email, and spending a couple of days trying to figure out which sdk was he referring to. His department answers that the sdk you should use, is the one you already used. The only one they have.
A couple of days lost, because certain smart-ass could not refrain himself from meddling in the project.
What would you do?
Note: Killing him is out of the question :)8 -
Where I currently work (and have done for 10 years) we were recently recruiting for another dev, and one of the other devs and our line manager were running the interviews.
After 3 or 4 failed interviews they decided to test the questions on me... I got 3 out of 10 :(
My argument was (and still is) if I get stuck programming I can google, or you can teach me new stuff. And I can make a good cup of coffee2 -
Lead Dev: Could you please make blahblah for us to use while making blah?
Me: Sure, np
Me: (to friend) hey could i test the connection for blahblah on ur pc
Friend: Sure, not doing anything anyway
Me: Thanks!
Me: Finds issues, fixes, and finishes blahblah
Me: Can i just borrow ur pc one more time
Friend: Ok... looks like its working
( i leave the room to fix small bug )
Lead Dev: (Friend) just showed me blahblah,he really did a good job on it
Me: ... Oh, yeah, he didnt rlly do anything though.. I just needed his pc to test it
Lead Dev: oh yeah, but, yknow he really did a good job on it, im sure u did too..
Me: ...2 -
I really, really, fucking god damn it REALLY need to move a legacy project from the grave yard server and get it in git, and then build a dev environment for it, so I can stop making incredibly volatile changes direct to PROD (backend, frontend and DB all at once and then test it while it’s live and being used, but fuck me if I can be bothered digging through a 10GB code base and attempting to make it work in a multi-environment setup when it’s going to be a long trip down the error logs until it works again 😱🔫2
-
Friend of mine: so I wonder how do you test your applications in the startup?
Me: testing? *grabs his coffee laughing*
Actually we have a complete build pipeline from commit/pull-request to dev and production environments. No tests. Really. We are in rapid product development / research state.
We change technologies and approaches like our underwear (and yeah, this is frequently). If we settled some day and understood the basic problems of the whole feature palette, we'll talk about tests again.rant early product development test driven development proof of concept don't make me laugh prototype startup3 -
Manager: This dropdown is hard to use on mobile
Dev: I thought building this for mobile wasn’t in the scope?
Manager: I changed my mind. It’s a lot easier for me to test on mobile so just rework it so it works on mobile. But only for testing.
Dev: How about I make the dropdown a rotary dial instead?
Manager: Good idea!
Dev: …9 -
Me: We really need to improve our unit test coverage.
Team/Boss: <sarcasm> Haha yeah.
Production Bug: I'm doing something nasty to a client, because a dev broke something but no test coverage.
Boss: How could we have prevented this?!1 -
Backend colleague : the API is online. It's tested and working, you can start the dev.
Me trying to manually call the API with all the fields pre validated : "error : invalid fields"
EVERY. FUCKING. TIME !
To all the backend developers : we are NOT your personal testers, and we are NOT supposed to clean your mess because you're too lazy to FUCKING TEST THE HAPPY PATH!!!
Thank you for your consideration.5 -
Episode 2 of this rant: https://devrant.io/rants/851636/...
PM went to meet with the provider and came back, so I had a talk with the PM and it went like this:
Me: so how did the meeting go? Hope they corporate with you
PM: *in a sarcastic voice* Bro, you need be a good dev, they told me only a good dev can implement Master Card API calls, and its all in the docs. That's all they told me, so you should know how the meeting went
Me: *there is no wifi in jail, there is no wifi in jail, there is no wifi in jail, there is no wifi in jail* Fine bro, I'll go back to school and come back after 12 years.
Seriously when I send the provider the request and the body and all they tell me is: You have an error, Id must be unique but they fail to point out the exact error or at least send me a valid ID to test, how does this make me the bad dev and him the genius that can run Apple, Google, MS all together at once!
What is even worse, when I called the provider he told me: Man transaction ID must always be unique, how could you not know this, how is Mastercard supposed to differentiate between transactions!!
But hey, no one told me transaction id must be unique, primary keys are never unique, like DUH!10 -
I've been writing a complex mutation engine that dynamically modifies compiled C++ code. Now there's alot of assembly involved, but I got it to work. I finished off writing the last unit test before it was time to port it all to windows. I switched into a release build, ready to bask in the glory of it all. FUCKING GCC OPTIMIZATIONS BROKE EVERYTHING. I had been doing all my dev in debug mode and now some obscure optimization GCC does in release mode is causing a segfault...somewhere. Just when I thought I was done 😅5
-
I fucking hate the fact that this group I'm side-hustling for gives maintainer access to every shitty dev they have.
Dev pushes four commits directly to master branch. Each time, pipeline fails on unit tests.
Shithead ignores failed tests and manually deploys to stage anyway.
Fuckface then declares (in group chat) that her "fix" works on stage and proceeds to merge to RC branch without updating the fucking unit test.
Pipeline fails (of course) and remains unfixed for the last EIGHT FUCKING HOURS.
This is what I woke up to at 6-fucking-AM in the god-damn morning.
*insert multiple expletives and insinuation of mother's excessive girth by comparing waistline to equator1 -
Manager: We need to fix this QA backlog. I’m going to share the workload of doing QA.
Dev: Please don—
*Dev email notification getting spammed with approvals*
Dev: …Are you even pulling the code down to test it locally?
Manager: There’s no time for that! We have to get this PR backlog pushed through! I’m just looking at the code to see if it looks good and approving based on that.
*Later that day*
Manager: HEY NONE OF THE FEATURES ON STAGING MEET THE REQUIREMENTS AT ALL. THIS IS A BUGGY MESS, WHAT HAPPENED GUYS??
Dev: …6 -
When did it become a trend to give people 4 hour technical tests? As a 32 year old man who commutes to work (1.5-2hrs each way) where do they possibly think I'll ever get that amount of time to complete a "test".
What's wrong with a github link and a face to face chat? A decorated linked in with recommendations?
Why can no one have the confidence to hire a dev?4 -
Hi, some time ago I was looking for a good app on Play Store and Bam! I found devRant. I opened it and the first rant I saw was from aswinmohanme. It was an image of Marilyn Monroe, but somehow created with circles, hope you understand me. I thought this is a great opportunity to test my dev skills so I opened Visual Studio and started coding. Today, after 2 days od work, I finally done it. It was written in C# and I have to say, I'm very proud od my child :^)
Link to repo on GitHub:
https://github.com/adampisula/...
In Debug directory there are some examples of this on action. If you're working on Linux just build this solution with Mono.4 -
Rant!!
Fuuuuuuuuuuccccccckk this new dev hired is such a dick he keeps on not testing his own code for simple things and expects everyone else to test it on local and tell him his bugs.6 -
So...Worked my butt off to have a website developed by a certain date client and I agreed on. Finished the site 3 weeks ago and sent dev link. Client has been completely silent; unreachable by email (I sent 5 in past 3 weeks) and phone (left 2 voicemails and a message with his receptionist today). In ALL five emails I told him I needed the email addresses he wants used to route his sales leads to...Got nada.
So today I seen that the lead forms have been tested on the website. Dude can't get back to me for 3 effing weeks, BUT can test his lead forms.. You know, without the lead email addresses that i asked for 5x. Ugh, idiot!!!2 -
This junior dev is killing me with all of the bugs in the code ... like did you even test it to see if it works fml1
-
Test server not working as expected - check with test team.
Test team experiencing the same problem - report to dev.
Dev team says the issue is not on their side - check with the service owners.
Service owner says it might be a problem with the request and gives me another point of contact - send an email with all the info.
POC says it doesn't have anything to do with him and copies "the right person".
Next person says to ask a different team.
Get reprimanded for asking too many teams.
Jeez idk, maybe if you stopped passing on the blame like a hot potato and actually helped me out I wouldn't need to.5 -
Just applied to a job with Microsoft with no professional dev history at all... I consider it a Turing test..3
-
Age test: How many/which of these did you have to deal with in your life as a dev/tech person?
My answer: Every damn one.24 -
Writing the new software dev test for our incoming interview process.
Me: And here is where we ask them to parse HTML with regex.
Lead developer: You are fucked up and the villain of this movie, multiverse and everything in between, fk u.
CMS Admin: And I thought Palpatine was evil. That is legit fucked up, fk u.16 -
Got a few Jira tickets reassigned to me because the dev who was supposed to work on them got stuck on another project. It's fine, that happens.
I open the tickets. No descriptions for all of them. No screenshots for those reported as bugs, nor any replication steps. No attached test cases or, well, ANY useful information.
I talk to our BA, he says that all information I need are in OTHER tickets on ANOTHER BOARD that business manages but I DON'T HAVE ACCESS TO. Honestly, these shitfucks could've just done simple copy/paste. But nooooo...
So I reassign all the tickets back to their original reporters (business testers) with comments requesting more information.
It's been a week. Now I have no idea what to put in my time sheet.1 -
Name of the branches in a git repository are like
dev
dev-branch
dev-hotfix
dev-test
dev-merge
dev-app
dev-com
dev-com
dev-ref
dev-staging
dev-username1
dev-username2
dev-username3
.
.
.
.
.
.
Master -
Building my own accounting software because everything else is overly complicated and is trying to compete with enterprise accounting tools. All I want is some budgeting, some bill tracking, and categorization.
Writing in Ruby because I'm a masochist. Using built-in minitest because again 😈.
I have currently around 62 assertions. As soon as I add ANY new test that's literally asserting true, everything comes unglued and 20+ failures pop up. Take it out, 62 passes.
I feel like I'm going crazy at this point. The errors also don't make ANY sense. Shit like, "that record doesn't exist" when it's clearly a part of fixtures and is only used in ONE test(the one that's breaking).
Installed minitest bisect, and it's like 🤷♀️"lol get fucked bro!"
So I came here to rant about this before my battery dies and I go drink myself to sleep.
Thank you for coming to my dev-talk.8 -
I used to work on a production management team, whose job was, among other things, safeguarding access to production. Dev teams would send us requests all the time to, "run a quick SQL script."
Invariably, the SQL would include, "SELECT * FROM db_config."
We would push the tickets back, and the devs would call us, enraged. I learned pretty quickly that they didn't have any real interest in dev, test, or staging environments, and just wanted to do everything in prod, and see if it works.
But they would give up their protests pretty fast when I offered to let them speak to a manager when they were upset I wouldn't run their SQL.2 -
You lousy fucking test class of an ass wipe,
TLDR; it fails and it passes all at the same time.
So during a deployment, one of the pre-deployment test classes fails, not something anyone has worked on so figured I run it manually to see what’s going on, but no the shit of a thing passed second time around.
Now because we can’t deploy without 100% of the test classes passing so I have to organise another deployment which it fails again. Fuck this,
Unprotects master
Git checkout master
Git merge dev
Git push master -f
Protects master
Skrew this!
Well would you look at that, it works now 😰 -
This was some time ago. A Legendary bug appeared. It worked in the dev environment, but not in the test and production environment.
It had been a week since I was working on the issue. I couldn't pinpoint the problem. We CANNOT change the code that was already there, so we needed to override the code that was written. As I was going at it, something happened.
---
Manager: "Hey, it's working now. What did you do?"
Me: *Very confused because I know I was nowhere close to finding the real source of the problem* Oh, it is? Let me check.
Also me: *Goes and check on the test and prod environment and indeed, it's already working*
Also me to the power of three: *Contemplates on life, the meaning of it, of why I am here, who's going to throw out the trash later, asking myself whether my buddies and I will be drinking tonight, only to realize that I am still on the phone with my manager*
Me again: "Oh wow, it's working."
Manager: "Great job. What were the changes in the code?"
Me: "All I did was put console logs and pushed the changes to test and prod if they were producing the same log results."
Manager: "So there were no changes whatsoever, is that what you mean?"
Me: "Yep. I've no idea why it just suddenly worked."
Manager: "Well, as long as it's working! Just remove those logs and deploy them again to the test and prod environment and add 'Test and prod fix' to the commit comment."
Me: "But what if the problem comes up again? I mean technically we haven't resolved the issue. The only change I made were like 20 lines of console logs! "
Manager: "It's working, isn't it? If it becomes a problem, we'll work it out later."
---
I did as I was told, and Lo and Behold, the problem never occurred again.
Was the system playing a joke on me? The system probably felt sorry for me and thought, "Look at this poor fucker, having such a hard time on a problem he can't even comprehend. That idiotic programmer had so many sleepless nights and yet still couldn't find the solution. Guess I gotta do my job and fix it for him. I'm the only one doing the work around here. Pathetic Homo sapiens!"
Don't get me wrong, I'm glad that it's over but..
What the fuck happened?5 -
I'm 2 months into my first dev job. Today, I was working on upgrading one of our products to React 18. Had a feeling my UI changes weren't being pushed to AWS so I wanted to test that. Changed all labels from ".. filter users..." to "shmilter shusers". Committed, then nearly pushed those changes for a PR. There are multiple lines of defence and only a 5% chance that no one would spot it but as soon as I realized that there's a small possibility that our customers would suddenly see "shmilter shusers" on their instances, I had an absolute fit. Maybe it's a "you had to be there" kind of thing but I don't remember the last time I laughed this hard.5
-
So, we’ve a small UK based dev team, we follow good practices and get good results. But ‘they’ want to deploy quicker (it was suggested we skip the test phases...) but don’t want to invest in more staff.
So their suggestion is to outsource development to Bangladesh and have us in-house devs work on discovery and innovation.
I’m uncomfortable with this as it feels they are thinking they can get quicker and cheaper dev done abroad (which I hate as it feels disrespectful to my fellow dev brothers n’ sisters).
Also disjointed as in my experience planning and dev’ing work best when you can talk face-to-face.
Thoughts?4 -
We have this important product with deadline closing in. Dev who was working on it for months went on vacation. Bugs came out, no comments in the code, no docs, some of the variables are as verbose as var abc = "some weird shit"; and I'm tasked with trying to test, fix algorithms and instruct on how to use it.
This isn't first time happening, so I'm dusting off my CV this weekend.5 -
I once ran a batch import job to stress test with much more data than usual in staging... so I thought.
I sshd into prod by accident. History search can be a bastard at times...
The moment I realized what I was doing was crazy. I was shivering and thought I get fired if anything went wrong.
fortunately I just duplicated the original data for the test, and the system was built to ignore unnecessary updates... so the data was correct and nothing went wrong.
Not an active stupid dev choice but still something I will remember for a while. -
In my web dev languages class today I went to try the feature to test the site through VS. Literally every browser BUT Edge would load... Even a Microsoft product knows that Edge is shit.
-
tl;dr - My company makes me pass around code over email. Is this normal?
How we fix bugs at my company.
1. Simulate bug in dev env (ok, cool)
2. Get the required code from svn and make changes locally (so far, so good)
3. Deploy changes in dev env and test (yeah!)
4. Take screenshots of fix in action along with the files you've changed and mail it to the respective leads (really? send code via mail?)
5. Keep changing your fix based on feedback and keep repeating above steps (what!)
6. Once approval mail comes, check-in your code in the svn branch for deployment and testing in the test env (QA team)
My question to you fine folks is, is this normal? Is this how most companies work? Passing around code over e-mail? Where the different versions of your fix are just attachments in emails. Or have I committed a sin by being a part of this heinous act?9 -
I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.
My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.
For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.
Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)
Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”
Dev X: “I don’t know how to access Jenkins.”
And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.
But the next day, I lost my shit.
I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.
For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.
Two stood out to me. I read them slowly.
“I think you should name this unit test better” (That unit test existed before my PR)
“This function was deleted and moved to this other file, just so people know”
A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.3 -
There was one time i went to Python dev position. HR company test was first of process and test was all about dotNet and C#, plus VBScript. I sat there until the finish time, did nothing.
-
Today I was writing Selenium tests and was struggling to find a good way to test a text editor. We did a weekly code review and my team lead rewrote the test ij 10 lines to generically handle all cases.
Hopefully I'll be a good dev someday. 😔4 -
Bored waiting for a long running test cycle to complete, so...
Monopoly: Software Dev edition.
All properties are companies with apple and alphabet being the most expensive ones, course the online version plugs into stock tickers to accurately reflect the current share price.
All railroads are broadband providers.
You don't build houses or hotels, but patent portfolios and 'landing on another property' becomes 'infringing on a patent'.
Cards:
- Kickstarter refund, collect £200
- Hit by ransomware, pay 1bitcoin.
- You are sued in East Texas, go straight to jail, do not pass go, do not collect dividends.
- Get out of court free card.
Yeah, I'm that bored that I'm rewriting bloody monopoly...5 -
My co-worker, still studying but working as a "senior dev", just decided that we don't need a test/staging environment anymore. We just "validate" (we also don't use the word "test" anymore) newly created features in production.
Makes absolutely sense...
Thank god I have a new job from february on!1 -
Kinda all other devs translate incompetent with a lack of knowledge
i would go with not able to recognize his lack of knowledge
Story 1:
once we had a developer, whom was given the task to try out a REST/Json API using Java
after a week he presented his solution,
2 Classes with actual code and a micro-framework for parsing and generating JSON
so i asked him, why he didn't use a framework like jackson or gson, while this presentation he felt pretty offended by this question
a couple of weeks later i met him and he was full of thanks for me, because i showed him, that there are frameworks like that, and even said sorry for feeling offended
- no incompentence here -
Story 2:
once i had a lead dev, who was so self-confident, he refactored (for no reason but refactoring itself) half the app and commited without trying to compile/run test
but not only once, but on a regular basis
as you may imagine, he broke the application multiple times and blamed the other devs
- incompentence warning-
Story 3:
once i had a dev, which wanted to stay up with the latest versions of his libraries
npm update && commit without trying to compile/testing multiple times
- incompentence warning-
Story 4:
once i had a cto
* thought email-marketing is cutting edge
* removed test-systems completely to reduce costs
* liked wordpress
* sets vm to sleep without letting anyone know
- i guess incompetent alert -2 -
I decided to work with #atom lately, and I made a fresh install on a VM to test some packages outside my real dev machine.
Just occurred to me that "by #GitHub" now means by #microsoft... So MS now really controls the IDE market from any possible angle.16 -
There are a lot... I am going to pick the interview dialogue (incl. test) with the government.
Following situation:
-5 recruiters
-3 candidates (including me) who have all passed an online test that did last for 3 hours
The online test was for the government to see how every candidate is good at math, English, situation adaptation, historical questions, a little bit of techy questions like "What does fps stand for?" and basic questions like that.
Even tho I did apply for a job as a software developer, there was not a single fucking question about programming. I shit you not. Anyways...
After everyone did introduce themselves. I was given the following question by one of the recruiters:"How do you think will the regular work look like to you, if you were to schedule it? We will be starting with you, <myName>"
Me:"Since this is hopefully going to be my first job in software development, I can only assume it for now. Based on my knowledge about this specific topic that I have made by reading other software developers' work experiences in form of textual content, I guess that I am going to do this [...] and that [...]. Oh and after this comes the planning phase (I had mentioned the sprints and agile "frameworks") and meetings of how the projects are doing so far.
After this comes the phase of sitting down and getting to work on the project I am assigned to.
At the end comes the "see you tomorrow, xyz" phase and everyone leaves."
Somebody else from the 5 recruiters:"I am sorry to interrupt you right here, but we are not offering you a dev job. It rather is a mixture of dev and sysadmin. You will be working most of the time fixing someone's problem with their PC and not sitting in a dark and empty corner of a warm room."
This was such a disrespect that I could not give an answer to. I was deeply shocked. Developers need more respect. Most of the fucking things you use, are created by developers, you asshole.
"We will be very happy, if you can call us by tomorrow to let us now if you are still interested."
Me does not even bother anymore and blacklists that government as a "trust me. You do not want to work there" type of job offering place.
Since I did not sign any NDA. It is the government of Germany.
PS: I did apply for a *dev* job. But somehow they did decide to create a new job and assign me to it. That is not professional.5 -
I have a new boss who was hired today. Well, I guess he's supposed to be a 2nd in command to my current supervisor, but I still have to report to him too I guess.
This dude is a high-sodium seasoned dev, and the kind who thinks anyone who's been in the industry less than 15 years should be at best a test engineer or thrown into the 7th ring of Customer Support.
Ugh. I'm now out of gin, which was my backup to my scotch. And this prick expects me to have a PR ready for him to review on a whole new application I've been working on for the last 2 weeks by midday tomorrow. And today was his first day.4 -
Been going interview crazy this week! The Dev rant community has helped me so much I'd like to thank each and everyone of you for helping me finally get running!
Have my first coding test to do today, have to build the attached file and i'm excited to get started! If you spot any pitfuls please let me know!
Thanks you guys so much! Will let you know how I get on!15 -
Dev: The server is completely down right now. Nobody can access the application, we need to divert some resources to horizontally scaling our app.
Manager: Hm, this was not in the schedule. I need to consult senior leadership on what to do about this. I don’t want to be held accountable for making a decision on this complex and highly nuanced situation.
Dev: No need, I have a solution. Just need a week to build/test/deploy the ability to horizontally scale.
Manager: But that will cause delays to new features.
Dev: New features don’t matter if the app can’t even load.
Manager: Ok you can implement your solution but it can’t take any time. I need those new features out.
Dev: ???????5 -
What the hell is with startup CTOs thinking dev applicants are willing to do an "8 to 10 hour" take home coding test before even a first in person interview?! Seriously?8
-
Me: We have a new research project for you. We need you to test these 2 new services, see how they will fit into the new application, look at alternatives if necessary etc. At the end we need you to write a report with your findings, showing how you would integrate them to achieve X, Y and Z, and how much it would cost each month.
Dev: sounds good, I'll come back to you when I have it.
*2 and a half weeks later*
Document paragraph 1: The new language translation service doesn't support the languages we need.
Document paragraph 2: Here's my proposal for integrating the new language translation service.
*review*
Me: So I had a look at the doc and it says it doesn't support the languages.
Dev: yeah unfortunately not.
Me: Ok, so when you discovered that, why didn't you look for an alternative? Or come back to me and say it's not going to work.
Dev: I dunno, I thought you'd want to see the rest of the research first.
Me: ... not if we know for 100% undeniable fact that it will never function.
Dev: Ah ok, I didn't think of that. I'll do that next time, don't worry.
... aw how sweet, he thinks there will be a next time. Poor guy.2 -
Manager’s PR Description: I made changes relating to a ticket which should work as expected. I also made various other changes as I saw fit, test whatever else I changed too.
Dev: …2 -
/*
"Not wk135, but blah blah blah"
Please don't misuse wk135 (Sorry)
It's about coding tests
Thank you. */
=>
A company took their technical test on this really weird website. There was a Windows Narrator guy's voice giving instructions while a timer was running. I had to flash my ID to the webcam and then fit my head on an outline on the screen. It was for a web dev position. I had to speak into the microphone to answer the Narrator's questions and then send the video to them. The questions were weird and hypothetical, mostly. I just thought that their process was dumb and unnecessary.
=>
I don't like aptitude and algebraic tests. One company, I remember, had their test on Google Forms. For some multiple choice questions, they put check boxes instead of radio buttons. So, I could just blaze through it selecting all options. Some of the questions had their first option as "All of the above" 🤔. Fortunately, I didn't pass the test.
=>
The company I'm interning with, starting from next month, had a good interview process. They asked me questions on JavaScript, CSS, and a few on algorithms and data structures. I was also given a task where I had to make a css animation of trees. I'm glad they didn't have an algebra entry test.
😊 -
Was writing a functional test in AdonisJS that queries an API endpoint with data and my test stays red with a dainty `expected 500 to equal 200` assertion failure.
In frustration, I yelled "What must I fuchen do to get my 500 to become a 200". Then my dev friend, an absolute fuchen genius tells me, "Subtract 300." I hope the prat stays debugging his code for a week!!8 -
I've been developing an Android app for a specific model of a handheld barcode scanner (almost 3 months) for our customers.. We are finally going live with this application so my boss ordered a new batch of devices. Bought the newer, fancier model instead of our test/dev model...
*Fatal error galore, different storage type, different barcode reader, deprecated functions,..*
Oooh the joys..
(Needs to be finished by tomorrow)2 -
So first of all I'm not a dev.
I'm a software tester and my test manager is a douche, but this is not it.
Today I went to the end user place along with him to teach them how to test properly and how to manage the software test cycle in JIRA.
I did a demo and showed the users the software the dev team developed and of course there were a lot of rants about it.
Users noted down a list of things to be changed and we kept going.
By the end of the demo, my test manager started discussing the fact that I told these guys to open Bugs without test objects on Jira.
I mean, we don't have a test cycle or test cased yet but these guys found issues already, what's the point?
So here's the funny part.
He then starts telling users (which ignore testing fundaments) to create a test cycle called 'meeting of today dd/mm/yyyy" and create tests below it which were named with the names of who created them.
All of that without a logic and ignoring the fact that these tests were not tests.
I was laughing my ass off while assisting this total mess and I almost lost control.
And this is my manager.
Luckily, tomorrow is Saturday.4 -
Like a lot of people, I have created an account on a website to find a job.
The funny part was when I was asked for my city (with a little * to indicate that the information is required) and ... the field was just gray and unusable ...
The solution was simple, edit the html to enable the field and add the selected value manually because it wasn't added automatically on selection.
Today i'm not sure if this was a test, a troll of just a crapy form ...
(actually it wasn't speciallt a dev site so i suppose it's the answer 3...) -
What is it with devs (not all, by any means!) who don't understand networks or basic computer operation? I'm not talking about anything complex, but things like the dev who asked if his IP address could be whitelisted so he could remote in from home. We asked what his public IP address is and he said 10.0.0.27.
Or the new dev who started and said her laptop camera didn't work and logged a ticket, only to be asked if she had the camera cover open or closed and said, "oh, that's what that lever is for."
Don't get me wrong - many devs and sysadmins and IT people of all fields are excellent. And there are some who are crap in every field. This is no rant about devs in general, just *these* crap devs that I can only throw my hands in the air and think, well, they scored ok in the SQL test.4 -
For a long time, I wanted to be a part of open source communities. I've been a dev for 6 years now.
I have the skills needed to help out but usually I'm fairly unexperienced on working with big teams, code reviews, and build-test systems they often use. So I'm scared as hell to even begin with. I feel unsecure to reach out and ask for helping or send a basic fix / pull-request.
What are your suggestions, how did you start working on open source projects?
Teach me senpai.3 -
TL;DR Dear boss, firstly, you always get someone to review anything important done by a fucking intern.
Secondly, you do not give access to your fucking client's production server to an intern.
Thirdly, you don't ask your fucking intern to test the intern's work that has not been reviewed by anyone directly on your client's fucking production server.
Last week, the boss and one of the lead devs (the only guy with some serious knowledge about systems and networking) decided to give me (an intern who barely has any work experience) the task of fixing or finding an alternate solution to allowing their support team access to their client machines. Currently they used a reverse SSH tunnel and an intermediary VH but for some reason, that was very unreliable in terms of availability. I suggested using OpenVPN and explained how it would work. Seemed to be a far better idea and they accepted. After several days of working through documentations and guides and everything, I figured out how OpenVPN works and managed to deploy a TEST server and successfully test remote access using two VMs. On seeing my tests, the boss told me that he wanted to test it on the client network. I agreed. Today he comes to me and he tells me to prepare testing for tomorrow and that the client technician is going to give me access to one of their boxes. And then he adds, "It's a working prod server. We'll see if we can make it work on that" and left. I gaped at him for a while and asked another dev guy in the room if what I heard was right. He confirmed. Turns out, the lead dev and the boss's son (who also works here) had had a huge argument since morning on the same issue and finally the dev guy had washed it off his hands and declared that if anything goes wrong from testing it on production, it's entirely the boss's own fault. That's when the boss stepped in and approached me. I ran back to his office and began to explain why prod servers don't top the list of things you can fuck around with. But he simply silenced me saying, "What can go wrong?" and added, "You shouldn't stay still. You should keep moving". Okay, like firstly what the fuck and secondly, what the fuck?.
Even though OpenVPN client is not the scariest thing to install, tomorrow's going to be fun.4 -
I didn’t turn down a dev freelance project when the client decided against going with best practices because the solution I offered was a well-established design pattern but created a need for a financial management change she didn’t like. I stupidly built what she asked for. It worked fine in the 3rd party vendor test environment but failed on production. After hours of analysis of code to ensure no changes happened to my source during test->prod deployment, and the vendor denying they had config differences between them, and the client refusing to pay, all I could do was abandon the project.2
-
Our best dev/arch just quit.
C dev lead & a dev staying late chatting.
Lead: am building, takes long
Dev: unit testing, time taking
Ask them y they r building on their latitudes when we got them linux precision with xeons/64gb workstation 1 each ?
Both: I code on latitude.
Build/test times. (pure Java/maven)
Latitudes=an hr or more
Precision=2m to 11m
Jenkins Infra we have =10 mins with test & push. Parallel builds support.
Am suposed to help with an open mind. They now want Mac pro12 -
Google in their *infinite wisdom* has decided the .dev domain they bought should be forced to https in Chrome 63 fully knowing it's a common test gTLD for Web developers.3
-
My favourite dev tool? I would't be able to do my work without any tool, which's in the list. I love IntelliJ IDEA & Webstorm, Java, JavaFX, Maven, Git & Gitlab, TeamCity, Upsource, YouTrack, Artifactory, wtf that list's kinda the complete tech stack. But I completly hate AWT & Swing (AWT fucks up on my Linux install, such a frame creates in about 10-20 seconds, if you test the app locally, you loose approximately 15 seconds per minute, and Swing uses AWT internally too), I hate Gradle (screw Google for standardizing it), and so on. Wow that's like my complete tech stack, what the fuck happend? The question was one tool, help me.1
-
Our employee management system, for some reason, stored Testlists (I work in QA) linked to the user accounts that created them. Now after an colleague who worked there for five years left pretty much all our data was suddenly down the drain and nobody backed the fricking server up because, hey, whats the fun in that. Now all the tests need to be rewritten and other than the whole gui test automation of our product, maintenance of the same for another product, manually testing dev issues and training my new code monkeys to frickin not commit non working code to the trunk I have now also "Make a better Employee management system" (roughly translated those are the specs I've got) on my plate... I can remember back to the care free days of just before my boss asked me if I wanted to try to automate some of the test cases... How did I ever survive this paralyzing tranquility. Ha, surprise.
!rant, I fucking love the stress and juggling a shit ton of problems at the same time keeps ine on edge.2 -
Why Gmail. Why the fuck do your search parameters, especially your date filters, not work anywhere near as expected.
You make me have to query and test, query and test, just, randomly fucking guessing because, fuck it, right?
With a good 10 second refresh time. I love twiddling my thumbs and pulling my hair out.
after:2018/11/1 should produce emails from Nov 1st onward.
Not, TODAY ONLY, if no other parameters are
specified.
If there's a from: parameter, now we want to do after Nov 1st, right?
And also, don't show me how to sort in reverse order, either. Not without a complete rewrite of my class there, which clearly I'm too lazy to do right now.
Fuck the Gmail Api, responsible for weeks of wasted dev time... or more aptly put, "fuck devs using our gmail api" says the maniacal, sociopath devils that created it
fuckers.1 -
Bug I had to fix today: some elements in our React app were being swapped with other elements.
We had `<foo>bar</foo>` on the component but on the html `foo` was being swapped with some other element in our app. It's contents ("bar" in the example) were being left in place, though, so we were getting `<baz>bar</baz>`.
This would only happen when running on production mode. On development everything was fine.
Also, everything seemed fine on the React dev tools. `foo` was where it was supposed to be, but on the html it was somewhere else.
Weirdest shit I ever saw when using React. I found a way to go around it and applied that fix, but I'm still trying to track this down to the source.
The worst part was waiting for fucking webpack to finish the production bundle on every fucking change I wanted to test. I didn't miss the change-save-compile-test flow at all.
What a shit day.4 -
FUCKING MICROSOFT IIS SHIT.
I'm a .NET dev since 13 years and EVERY FUCKING TIME STUPID IIS MOTHERFUCKER AND STUPID WINDOWS SERVER have a different problem setting up because of some permission.
You can't never get a site up in IIS without loosing time and patience having weird 400/500.x errors because every fucking machine have to set up some tweaky and hidden permissions.
I have 2 identical fucking win servers and deploying a .NET core applications and on one works (test server) and obviously, on the production server it gives troubles.
FUCK YOU MICROSOFT FUCK YOU I would take the IIS devs personally here and whip them to death until they don't resolve the fucking thing3 -
Went to firefox test pilot and they really got some cool ideas there (e.g. snoozetabs: https://testpilot.firefox.com/exper...) only if firefox devs invested 1% of fucking around with "cool ideas" to maybe getting the dev and responsive tools up-to-date..1
-
- 5 days until customer integration test. I finished my work for the test a week ago so I am relaxed. 10 days of estimated work for other team, 1 dev scheduled for this task.
I reminded of the deadline, which seemed not realistic anymore; "Don't be so pessimistic" they said, "Everything is fine", "We'll get it done".
- 2 days to go and half of the system doesn't work, the external test system rejects all data (nobody had time to read the specs -> let's call it 'assumption based development' (ABD))
I reminded of the deadline, and that I would like to have an internal test with all components beforehand; "Don't be so pessimistic" they said, "Everything is fine", "Just some minor issues".
- 1 day to go and dev from other team called in sick... (and I can really empathize this decision); "Someone else can jump in and finish the work" they said.
- An hour later the test was cancelled not even 24 hours before it should take place. We could have rescheduled the test more than a week ago, that wouldn't have been so disgusting and even save our customer some hours of preparation effort.
I hate myself when I was right from the start but wouldn't enforce my position because I'm too kind sometimes. -
I'm so fkin happyyyyyy!!
2 months ago a friend hits me up and says "lets make a fkin website"
I had no knowledge of web dev and didn't take it seriously cuz "web dev is for losers who can't code, also they get paid in peanuts" as stated by someone I highly respected back in school.
Fuck him.
It's all changed.
I never thought I'd say this.
But web dev is the best thing I've picked up in 3 years
Been making steady progress in js, php, sql then picked up jquery and made a few dynamic test sites. God it was so fkin satisfactory. Started node- it's intimidating but I'll get the hang of it soon and thinking of starting vue or ember as soon as I'm confident in all the stuff I've picked up. Oh and friend's website?
Fuck that it's a trash concept. I still thanked him for getting me to start web dev and moved on.
I still have my roots in c++ and Python and I'll never forget them but I think this may be the start of a wonderful journey. Be sure to burst my bubble I'm just a noob now10 -
Dev sent out a code review request.
I take about an hour, ask questions, make suggestions, general feedback, etc.
Today I noticed none of my questions were answered, developer closed the review, and the code merged into the production branch.
So I email him, asking him why the review was closed and why none of my concerns were addressed before merging to production.
Dev: "No one responded or left feedback, so I thought it was OK to merge up."
Me: "I reviewed and left feedback within the hour you sent the request."
Dev: "Oh yea...you did. Sorry. The code is already in production, but if you still want to leave feedback, create a work item, and I'll take a look."
No you won't.
An example of the code...The dev added an async method to a test harness *console app*. Why? .. check in comment was "Improves performance and enhances the developer experience.."
NO IT DOESN'T!
OK..that's off my chest. No one is getting punched in the face today.6 -
That moment a non dev friend wants to get into web dev and ask you want he needs, you give him a list with 5 languages, 20 libraries/frameworks to use, 8 tools, 25 devices to use to test and a letter saying "Good luck learning all of that"1
-
Just needing somewhere to let some steam off
Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.
For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.
Introducing Rancher
We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.
Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.
As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.
Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.3 -
Development tools for embedded projects shouldn't need fucking internet to operate. Every fucking app needing internet to even startup is getting more and more stupid. I do a LOT of development offline. I usually have my dev machine away from internet for weeks at a time. It very nice to not have to deal with update issues and the like during this time. So naturally I choose tools to do offline programming for both desktop and embedded. So I decided that for my embedded work I wanted to have better environment than Arduino IDE. Now enters VSCode with Platform IO. I download all the target platforms for my boards. I get it all working and installed. Then I take my computer to my non internet location. I fire up VSCode, select the platform, create a test project, and compile the code. Everything is working great. Then I go to upload the code to my board:
"Blah blah blah you need internet first time talking to a board blah blah blah." Seriously? WTF? Who does stupid shit like this? Once you install your dev tools they should be fucking installed! Now I have to drag my fucking dev boards to another location and do a test install just to do fucking offline programming.
FUCK YOU PLATFORM IO!
Notice I don't blame VSCode for this. I know this IDE is very internet dependent, but it works once you get your plugins installed regardless of internet. Unless of course you are doing internet based programming.3 -
What browsers do front end devs here normally test on? I test on Firefox and Chrome because...that's all I use, but what about Edge/Safari or god forbid IE11?
I'm more familiar with backend dev ops so my testing consisted of checking Firefox a lot. :P6 -
!rant.
Most QAs are dumb beasts, unable to think clearly or rationally, lazy parasites that suck the lifeblood out of a project.
Except this one guy I work with. He blackmailed the CTO to move, and landed himself a junior dev job.
He joined my team a few months ago.
"Right" says I "forget the crap you've learned so far. Here's a list of algorithm books from Amazon. Order them and read them. There'll be a test at the end."
He did. He is now reviewing lead dev work and merrily trolling their poorly performing work. Speaking to them in Big O (and so confusing the crap out of them) and earning stars at every turn.
I'd like to think I had a hand but all the effort was his.8 -
Went for a dev job interview in which the senior software engineer said this...
"Javascript is like Java but scripting"
I didn't say anything to this. I don't know if it was some sort of a test (even though I was in the middle of a 4 page test for them).
Evything text and every every reference I have ever seen about Java and Javascript is that they are nothing alike. What would others have said to this?
FYI - I didn't get the job. Which I am pretty glad about as I didn't like the software engineer guy, and I don't think I would have liked working with him. He had this fake friendly exterior but the fuckwit personality was shitting through every gap in his skin.... I just noticed I used the work shitting instead of shinning, I think it is suitable so I will leave it.1 -
The reason for half the web-dev world sufferings is that Microsoft won't stop choking their users with explorer or edge, and half of the client are too dumb or lazy to download a different browser to test stuff. Fuck this shit man! Nothing works the way it should on this bitch.
Everytime my manager says- It should work perfectly on IE because client doesn't have any other browser, I curse IE for exisiting. If you can't improve it, just remove it you freakin' sadists. It'll not be an embarrassment to load something better on your OS. If anything, it'll get people to like you maybe. Like you for accepting your fuckery and making a decision in favor of the web dev world and innocent windows users, who only use your explorer to download other browser asap. For just that one time and for all your arrogance, you're making the whole world suffer.2 -
A dev found a bug I created where I set a SQL parameter name to @OrderID instead of the expected @Order. The standard is @OrderID, there is one stored proc where it's @Order.
Oops...I didn't catch it because the integration test didn't cover that area of the code. My mistake...I should have checked...I take complete responsibility for the screw up.
He let me know by email..
"When refactoring, from now on check the stored procedure parameters, there are a few that don't follow the standard."
I was like "from now on..."? ...wow....bold comment from someone responsible for code that doesn't check for nulls, doesn't log errors, and relies on exceptions for flow control. You wouldn't even have known about the error if I didn't modify your code to log the error (the try..except returned false)
I really wanted to reply ...
"Fixed. From now on, when you come across those easily found bugs, go head and fix it, write a test, and move on. Don't send a condescending email to me, my boss, your boss, all the DBAs, and the entire fracking order processing team. Thanks."
But..I thanked him for finding and letting me know...we're a team..blah blah blah..
Frack..people suck.1 -
Rolled out a new application I built almost entirely by myself 2 days ago... But my dev group is understaffed and has a project manager who is literally the most clueless person I have ever met, so as a result, we don't have a functional/useful dev/test/prod framework and no standards for how to deploy apps. So my past 2 days were comprised of fixing bugs in the live system that could probably have been caught if I had the time and resources to get everything thoroughly tested. It's stable now, but damn our management for being generally idiots. Our motto appears to be "Fuck it, we'll do it live"1
-
TL;DR: When picking vendors to outsource work to, vet them really well.
Backstory:
Got a large redesign project that involves rebuilding a website's main navigation (accessibility reasons).
Project is too big just for our dev team to handle with our workload so we got to bring a 3rd party vendor to help us. We do this often so no big deal.
But, this time the twist was Senior Management already had retained hours with a dev shop so they want us to use them for project. Okay...
It begins:
Have our scope / discovery meeting about the changes and our expected DevOps workflow.
Devs work Local and push changes to our Github, that kicks off the build and we test on Dev, then it goes to Staging for more testing & PM review. Once ready we can push to prod, or whenever needed. All is agreed, everyone was happy.
Emailed the vendors' project manager to ask for their devs Github accounts so we can add them to the project. Got no reply for 3 days.
4th day, I get back "Who sets up the Github accounts?"
fuck me. they've never used Github before but in our scope meeting 4 days ago you said Github was fine...??
Whatever, fuck it. I'll make the accounts and add them.
Added 4 devs to the repo and setup new branch. 40min later get an email that they can't setup dev environment now, the dev doesn't know how to setup our CMS locally, "not working for some reason."
So, they ask for permission to develop on our STAGING server.. "because it's already setup"... they want to actively dev on our staging where we get PM/Senior Management approvals?
We have dev, staging, production instances and you want to dev in staging, not dev?... nay nay good sir.
This is whom senior management wants us to use, already paid for via retainer no less. They are a major dev shop and they're useless...
😢😭
Cant wait for today's progress checkup meeting. 😐😐
/rant1 -
It works locally, it works in Dev, it works in Test, but fails to deploy in UAT. Is it a data issue? I don't know, I don't have permissions to see the UAT database. Literally all I know is that this API is returning 500 instead of what it's supposed to return, but only sometimes.
Guess I'll sit here all day and try to solve the problem telepathically as there is literally no way of troubleshooting other than scrolling through the code and hoping that a cartoon lightbulb appears above my head.2 -
I'm the lead dev on this team. The project is split into multiple separate modules to comply with separation of concerns, and so new devs don't need the whole fucking codebase (risking them running away with everything) to contribute to the project as a whole.
So we don't need a fucking config file to enable and disable features.
So we don't need to upload a 500mb monolith every time we want to test a change.
So we can test old fucking versions of modules without merging it back into the entire codebase.
What did this fucking dev do? He was having one small issue with Maven. One. It wasn't updating his local snapshots to the correct Artifactory version.
He decided, instead of trying to fucking fix it: HEY, LETS IGNORE THE LEAD DEV'S DEMAND TO KEEP THEM SEPARATE. IM GOING TO MERGE THEM INTO ONE MODULE FOR SOME FUCKING REASON.
I refuse to continue working with this dev if he's going to sidestep my demands and undermine my authority. He wants to go it alone? Be my fucking guest. I'm not touching his shitty single-codebase monolithic monstrosity.
If this is going to be a regular fucking occurrence, he can eat a dick and choke on it.2 -
Hmm. This code needs refactoring.
*recodes on Local and uploads*
Works on my branch.
*git push origin master and merge*
Works on Dev.
*deploy to Test*
Works on Test.
*deploy to Live*
Doesn't work.
*compares Live to Test, Dev, and Local*
No f$@%^%%$# difference!?!!
*quits development and lives under a bridge*5 -
TLDR;
How much do you earn for your skill set in your country vs your cost of living?
BONUS;
See how much I & others earn.
Recently I became aware of just how massive the gap in developers earnings are between countries. I'd love to calculate a fixed score for income vs cost of living.
I know this stuff is sensitive to some so if you prefer just post your score (avg income p/m after tax / cost of living).
I'm not shy so I'll go first:
MY RATES
Normal Rate (Long term): $23
Consulting / Short term: $30-$74
Pen Test: $1500 once off.
Pen Test Fixes: consulting rate.
Simple work/websites: min $400+
Family & Friends: Dev friends are usually free (when mutually beneficial). Family and others can fuck off, even if they can pay (I pass their info to dev friends with fair warning).
GENERAL INFO
Experience: 9 years
Country: South Africa
Developer rareness in country: Very Rare (+-90 job openings per job seeker).
Middle class wage in country: $1550 p/m (can afford a new car, decent apartment & some luxuries like beer/eating out).
Employment type: Permanent though I can and do freelance occasionally.
Client Locality: Mostly local.
Developer Type: Web Developer (True web dev - I do anything web related from custom HTTP servers to sockets, services, advanced browser api's, apps & more).
STACKS / SKILLSETS
I'M PROFICIENT IN:
python, JavaScript, ASP classic, bash, php, html, css, sql, msql, elastic search, REST, SOAP, DOM, IIS, apache
I DABBLE WITH:
ASP.net, C++, ruby, GO, nginx, tesseract
MY SPECIALTIES:
application architecture, automation, integrations, db's, real time data, advanced browser apps/extensions (webRTC, canvas etc).
SUMMARY
Avg income p/m after tax: $2250
Cost of living (car+rent+food): $1200
Score: 1.85
*Note: For integrity when calculating my cost of living I excluded debt repayments and only kept my necessities which are transport, food & shelter.
I really hope you guy's post your results, it would be great to get an idea of which is really the worst / best country to be a developer in.20 -
The disconnect between the hiring process and the actual job in software development is mind boggling.
They give you an online test in the first step. You can't open a new tab otherwise that's considered cheating.
Holy crap, it doesn't work like that in the actual job. Googling things is a SKILL every dev should possess.
I've started telling hiring managers I'm not interested anymore in the job the second they pass me an online test.
I created a YouTube channel for this exact reason. Go watch me code on camera so you get to know my coding skills better otherwise go fuck yourself.3 -
So my first dev job has ended up as fucking dat entry after one of the contractors got bored and left.
I’m an SQL Developer (at least that is my job title) and all I do is fuck around with exchange rates in spreadsheets.
The only “proper” development work they gave me hasn’t even been applied to the test server yet (should have been done over a month ago)
And the project they gave me to look into migrating from sourcesafe to GitLab has ground to a halt.
I’ve been here 4 months and I want to quit already, that must be a record (for me at least)
I was keen an full of energy, willing to do some work from home etc. But a little piece of me dies every time i open Excel3 -
Product Management thought of automating an entire legacy product so they funded undisclosed amount to program management who in turn hired >20 contract devs managed by architects and dev managers with zero functional or technical knowledge of product and who in turn went ahead automating the product in selenium, end result of which was an useless automation framework with lot of browser specific dependencies and whuch could run only on one setup environment and migrating test cases to another environment and running is almost impossible and tyrannical to configure. The automation test cases are highly disorganized with all generic setup, DB configurations and business case test data mixed up in same config files and which need to be rewriten every time ported from one environment to other.To add misery to my woes as a dev working in that product I was told to utilize that framework and enhance the quality of my code by writing inline automation Cases for the same. I am left speechless thoughtless and emotionless after that decision.2
-
First dev job is my current one.
I'm a software engineer in test, writing automated UI tests for web and mobile apps.
Its pretty great. I work from home with flexible hours. I have a boss but he doesnt manage my dev team, he just checks in to make sure I'm getting support, training and have all my questions answered. My dev team is myself and 2 other people, both of which are cool, and all the work is dev-driven.
Might just stay here until retirement, that sounds easy.2 -
That frustrating moment when you ask a Yes/No question and you get a full warstory and a conclusion to that story that doesn't answer the question and leaving you wondering why instead.
I just asked permission if I should implement this new feature on Dev/Test environment. Not gonna ask again next time. -
I hate dev politics...
PM: Hey there is a weird error happening when I upload this file on production, but it works on our test environments.
Me: After looking at this error, I don't find any issues with the code, but this variable is set when the application is first loaded, I bet it wasn't loaded correctly our last deployment and we just need to reload the application.
Senior Dev: We need to output all of the errors and figure out where this error is coming from. Dump out all the errors on everything in production!!
Me: That's dumb... the code works on test... it's not the code.. it's the application.
Senior dev: %$*^$>&÷^> $
Me: Hey I have an idea! If test works... I can go ahead and deploy last week's changes to prod and dump those errors you were talking about!!
Senior Dev: OK
Me: *runs Jenkins job the deploys the new code and restarts the application*
PM: YAY you fixed it!!
Senior Dev: Did you sump put those errors like I said.
Me: Nope didn't touch a thing... I just deployed my irrelevant changes to that error and reloaded the application.2 -
Well! Hello everyone!
I am PokerJack. (Not a jAsE account)
Well, that's the name of my first Python Program. ~\_(-_-)_/~
Not a dev, would like to be one.
I work at Pornhub as a Consultant.
@rutee07 is my subordinate.
@devTea is my assistant
@Root - Dev Lead
@grumpyoldaf - Boss
@irene - Girlfriend
@jAsE - Heard about him, never found out who.
Btw, @rutee07 send me the test logins for all Pornhub Premium accounts. Immediately!!20 -
Works in production?
Yes: Copy changes to dev and test.
No: Start humming and walk away from the computer. -
!dev. Test/Fixing this monster because my dad's mother refuses to use a newer laptop even if i just give it to her.6
-
Thanks, AfterShip.com, for working flawlessly while the system I was building was in dev/test mode and for the first few days in live mode, then completely crapping the bed the first day I needed you to work with real tracking data with the live system. You were the ONE thing that was working consistently well, and you had to go and ruin it.4
-
>be me
>some months ago
>apply for a node.js job, send them my resume with links to my git repos
>get an interview, they tell me they appreciate my additional android dev experience cause they be working on an app.
>think to myself "oh nice, imma get this job!"
>"Anon, we gonna test you, ok?"
>"okay no problem"
>I prepare for both node and android but mostly node
>test day arrives, I'm hyped
>test is actually to make a maps android app in 8 hours
>wat?!
>do it anyway, achieving some functionalities
>a couple of weeks after
>I email them, asking news
>they basically say "oh we sent you a message on skype to tell we continued with another person as a backend dev because they had a better android app"
>log into skype
>0 messages
>mfw pic related6 -
// Stupid JSON
// Tale of back-end ember api from hell
// Background: I'm an android dev attempting to integrate // with an emberjs / rails back-end
slack conversation:
me 3:51pm: @backend-dev: Is there something of in the documentation for the update call on model x? I formed the payload per the docs like so
{
"valueA": true,
"valueB": false
}
and the call returns success 200 but the data isn't being updated when fetching again.
----------------------------------------------------------------------------------------
backend-dev 4:00pm: the model doesn't look updated for the user are you sure you made the call?
----------------------------------------------------------------------------------------
me 4:01pm: Pretty sure here's my payload and a screen grab of the successful request in postman <screenshot attached>
----------------------------------------------------------------------------------------
backend-dev 4:05pm: well i just created a new user on the website and it worked perfectly your code must be wrong
----------------------------------------------------------------------------------------
me 4:07pm: i can test some more to see if i get any different responses
----------------------------------------------------------------------------------------
backend-dev 4:15pm: ahhhhhh... I think it's expecting the string "true", not true
----------------------------------------------------------------------------------------
me 4:16: but the fetch call returns the json value as a boolean true/false
----------------------------------------------------------------------------------------
backend-dev 4:18pm: thats a feature, the flexible type system allows us to handle all sorts of data transformations. android must be limited and wonky.
----------------------------------------------------------------------------------------
me 4:19pm: java is a statically typed language....
// crickets for ten minutes
me 4:30pm: i'll just write a transform on the model when i send an update call to perform toString() on the boolean values
----------------------------------------------------------------------------------------
backend-dev 4:35: great! told you it wasn't my documentation!
// face palm forever4 -
We are 3-4 days away from deployment to production. We are still bug fixing. But one coworkers decided this is the time to make a fuss about the way everything is set up. He doesn't like the dev database. So he knocks it over.. and while so doing it, he doesn't inform the team. And when I ask if something else is gonna knock over? No answer! (And something broke down too..)
Now we have issues to test our bugfixes. The whole thing took me half a day finding out and made me distracted with frustration, and not just for me. Most bugs could've been done in that half a day!
I so wanna punch the guy xD but no, I gotta save face, pfff!2 -
The craziest thing happened today
I havemy environment studies test today so spent the last night studying so now even after 3 cups of coffee everything feels like third person. So in the metro i am browsing dev rant and so zoned that i miss my stop by three stops!!
Guess climate change is indeed affecting ourselves -
So I got in contact with a recruiter who said they have a possible job for me. The catch is it's in c# (I am a python java dev) and that there is a assessment test for the language to test for competency. I told the recruiter that's fine but I would need a week to highlight the main differences between the two languages and at least do a couple of educational programs for my learning sake. All was fine and that was the plan.
The next day the recruiter notifies me that the test is being called off on account of the company being swarmed. So the recruiter then proposes another similar test (in c#) the recruiter will use to measure my skills and that the recruiter will send the test via email that same day. Later that day I check my email and don't see the test. So I message the recruiter and never get a response. Next day comes and I decide to give the recruiter a call; no response. I then wait until the next day and message him on linkedin that I still needed the test. Linkedin was showing he read the message, but of course didn't respond.
I told my brother about this and he said to send a message saying: "Hi [recruiters name] because of the lack of further feedback I decided to go with another opportunity. Best regards, Lane"
After I send it I get a message the next day from the recruiter saying: "Hey, sorry I haven't gotten back to you. We had to install a new phone system yesterday so it was a busy day."
"I'm going to send it to you today so that you can look at it over the weekend. "
I can't help but think the recruiter is full of shit, but I may be jumping to conclusion. I know they can have a busy schedule, but if you have time to look at a message on linkedin how long would it take to type a short message explaining what's going on? I would like to know any opinions or insights on this.10 -
Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Scrum master is asking why all of it should be tested at the same time and I'm here like this is fucking dumb. Also the tester decided to start testing with the most complex piece of work, rather than prioritising.
Starting to wonder if I'm just the outsider or whether no one understands that granularity is better.2 -
-----------Jr Dev Fucked by Sr Dev RANT------
Huge data set (300X) that looks like this :
( Primary_key, group_id,100more columns) .
Dataset to be split in records of X sized files such that all primary_key(s) of same group_id has to go in same file.
Sde2 with MS from Australia, 12 years of 'experience' generates an 'algo'. 70% Test case FAILED.
I write a bin packing algo with 100% test case pass, raises pull request to MASTER in < 1 day. Same sde2 does not approve, blocking same day release.
|-_-| What the fuck |-_-| Incompetent people getting 2x my salary with <.5x my work2 -
A newly joined developer (who was supposed to be very senior) comes and asks me how to write a test cos for some reason the person didn't know how to mock.
In Java,
(same for any other implementation which has an interface)
Writes Arraylist list =.....
Instead of List list = Arraylist...
Deployed code (another engineer from another country helped to deploy since this new senior dev didn't have access yet.
But the new senior dev didn't update relevant files in production code which brought down the site for nearly an hour. Mistake aside, the first reaction from this new senior dev is 'WHY DIDN'T THE DEV THAT WAS HELPING DIDN'T DO THE FILE UPDATE?'
This was followed by some other complaints such as our branching stragies are wrong. When in fact the new senior dev made a mistake by just making assumptions on our git branching strategies and we already advised on correct process.
Out of all these, guess this is the best part. The senior dev never tested code locally! Just wrote code, unit test and send to QA and somehow the test passed through. I learnt this when I realised this dev... has not even set up the local environment yet.
I keep saying new but this Senior dev been around like 3 months! This person is in another team within our larger team but shares same code base. I am puzzled how do you not set up your environment for 3 months. Don't you ask for help if you are stuck? I am pretty sure the env is still not setup.
Am I over reacting or is this one disgusting developer who doesn't even qualify for an intern let alone a senior dev? It's so revolting I can't even bring myself to offer help.8 -
Nobody reviews my PR into test branch
The only guy who reviews it is the new senior dev who isn't yet used to how the company works, leaves comments about useless stuff and doesn't fucking approve
Jesus fucking Christ5 -
So, we (I'm the backend guy and work with a UI dev) are building this product portfolio management tool for our client and they have a set of 250 users. The team has two point of contacts for the 250 users who maintain the master data, help users with data quality, tool guidance, reporting and other stuff. So one day one of these two support users come to me and say : Hey I'm not able to add new transactions coz a customer is missing.
We have the provision to create / maintain customers.
I check the production DB, application code, try creating the customer and then the transaction, everything works perfectly fine.
I ask the user for a screen sharing session, the user starts reproducing the error like this :
We have a 3 system landscape - Dev / Test and Prod
U : Logs into the test system url, creates the customer.
U : Points out the toast saying customer creation is successful.
U : opens a new tab, opens the production system, tries creating the transaction, searches for the customer and says " see !! cant find the customer here ! the master data management apps never work !! "
FML?. -
*laughing maniacally*
Okidoky you lil fucker where you've been hiding...
*streaming tcpdump via SSH to other box, feeding tshark with input filters*
Finally finding a request with an ominous dissector warning about headers...
Not finding anything with silversearcher / ag in the project...
*getting even more pissed causr I've been looking for lil fucker since 2 days*
*generating possible splits of the header name, piping to silversearcher*
*I/O looks like clusterfuck*
Common, it are just dozen gigabytes of text, don't choke just because you have to suck on all the sucking projects this company owns... Don't drown now, lil bukkake princess.
*half an hour later*
Oh... Interesting. Bukkake princess survived and even spilled the tea.
Someone was trying to be overly "eager" to avoid magic numbers...
They concatenated a header name out of several const vars which stem from a static class with like... 300? 400? vars of which I can make no fucking sense at all.
Class literally looks like the most braindamaged thing one could imagine.
And yes... Coming back to the network error I'm debugging since 2 days as it is occuring at erratic intervals and noone knew of course why...
One of the devs changed the const value of one of the variables to have UTF 8 characters. For "cleaner meaning".
Sometimes I just want to electrocute people ...
The reason this didn't pop up all the time was because the test system triggered one call with the header - whenever said dev pushed changes...
And yeah. Test failures can be ignored.
Why bother? Just continue meddling in shit.
I'm glad for the dev that I'm in home office... :@
TLDR: Dev changed const value without thinking, ignoring test failures and I had the fun of debunking for 2 days a mysterious HAProxy failure due to HTTP header validation... -
- why did you enter test data text value with this <script> html? Don't do that. Use normal text
this is something I've never expected to hear from a php/react dev.... I'm truly disappointed. I really am.
On top of that he refused to follow my recommendations to google: "xss". Another teammate had to google for him and drop a link.
Just when I was about to like working with this guy.... :(5 -
My company insists on working in one production environment to save time and every time I try to convince them to set up a work flow with a dev and test environment, they tell me we don't have the time...
Even after I set one up anyway as I'm scared shitless to touch production. They tell me it's faster doing it all in one environment.
They launch an update. Site buggy as hell and doesn't load 90% of the content...
Sigh....4 -
Just got my Linux dev environment set up, even got an alias working that would launch all the software I needed to test my code. Then today decided to change primary drives. At least I know how to set it back up next time, right?2
-
Well, that's how much it costs to hire a senior developer. I think I'll just go back to being a junior dev :-D.2
-
!dev
Re-watching old episodes of mythbusters. S2E1, they test "better to walk or run in the rain"
Their method totally pissed me off.
They had cotton suits on their body and measured the weight difference before and after.
Except the cotton suits DIDN'T GO ON THEIR HEAD.
Where is most of the rain going to fall when walking slowly and the water source is directly above your head? Head and shoulders.
So of course their findings were that you got more wet when running, as some of the water got on their belly instead of their head.
Can't find anyone talking about it online so had to rant about it here. So fucking stupid7 -
Anyone else like... REALLY bad at algorithms and logic stuff?
I just hate them so much.
Tell me to build something and gg done. But all these tests for jobs freak me out.
Like. It probably ends up being something simple and when it's explained I know what to do but at first I just instantly shut down and can't think.5 -
So... I take over this one ticket to test... the ticket mentions some visual component popping up when a button is clicked. It says there is a success and a failure message. The title of the story also mentions another functionality.
I start testing and some fellow QA asks me why I'm testing in this environment. Turns out, three people are sharing one environment and three different things are deployed...
I ask the dev whats going on because I heard there are multiple people deploying stuff...
He just tells me "oh, my changes are deployed I just checked".
I tell him that it's not about that but about communication and testing one thing at the time. Then I tell him, that I wouldn't test until his stuff is the only stuff there.
Some time later he hits me up again, now with the env to himself.
I test and quickly I see, that there is only the positive message even when I make sure that the backend is not reachable. I tell the dev what I found and he tells me "oh no, it's just the implementation of the popup thing, it's just frontend for now"...
I tell him, that the ticket should say so.
No answer for like 1-2 hours. Then I get an "ok".
End of the day.
Next day I come in and the fellow QA tells me, that the dev asked him to test the ticket.
I ask him if he changed anything about the scope of the ticket, he says no...
I'm like "ok... know what... begin testing and then tell him what I already told him".
So he's testing and then tells him again to update the scope.
Later in the daily the the dev's update is besically "they won't test my ticket..."
It would have taken him like 1 fucking minute to update the ticket...
The whole QA team was always trying to being helpful and even when the tickets where sometimes not 100% clear we always made it work... but now we are more and more going towards "MR does not meet ticketdescription, fix it" and "I don't care if its just a small thing... fix it and then come back to me"...
Seriously frustrating some times...2 -
You're not a real dev unless you've made so many changes in your code without testing, that you're too afraid to actually test it.4
-
Me: Open Jira. See 8 point story skip QA column and move into Done.
Ask dev why it didn’t go through QA.
Teammate: Oh, did they want to test this?
Commence argument that **all** stories need to go through QA. -
UI bug is found to only occur in Firefox.
Director sends mass email telling dev & qa to only test using IE11. -
We take over development of a live customer facing system and PM agrees date for our first code deployment with client CIO
Me: The dev and staging environments don't have any test data currently as the old agency screwed it up
PM: Well you better load some
Me: There isn't any... It'll take 10 days to copy prod db due to hosting provider SLAs, leaving 1 week for SIT, UAT and performance testing (assuming they don't screw up)
PM: Well the date is set, 1 week will be enough for testing2 -
Way back in high school there was a school wide competition to see who would represent the school at the bigger competition (I dunno, regional or something). Halfway during the test I was on the third out of four tasks while pretty much everyone else was on the first one. The teacher saw this, looked at what I did and said to everyone "He is already on task 3, does everyone agree he represents the school?"
Everybody said yes immediately.
:) The dev equivalent of a K.O. win, felt pretty badass :D -
Programming has taught me
1. Importance of patience, friends and family and yeh StackOverflow too...
2. Importance of small contributions towards dev community.
3. How smaller things can make big changes.
4. Helping others and getting help if you get stuck.
5. Anyone can code, but very few can build robust solutions. Project not just coding but it needs preparation and planning too.
6. Importance of reading documentations, writing test cases, debugger programs.
7. You can learn things even if you have no idea about it. It just takes your interest. -
Client's Devs Yesterday: "We are ready for a production test, and should be ready to go live in 1 week."
Today after successful test: "We need 6 weeks of production before going live"
How can you be so far off on your timelines? A solo dev has done this same flow in like three weeks. It has already been three months...1 -
"Here customer, have the username, password, and URL of our developer's CI environment! You can test all of your features there. "
" Devs: Please don't make any changes to dev code that would cause the CI system to run."
That's not how this works. That's not how any of this works.2 -
TL;DR: working too fast is as worse as working too slow
3 months ago the team leader left.
Sincee then, me and another dev are sharing his responsibillities.
Me and him used to do a lot of testing.
(In our team, the devs test and CR each other)
Now that he left, I often find myself sitting without anything to do - because I did all the available tasks and no one tested them or gave feedback.
Sitting with nothing to do feels aweful.
My manager sits behind me, so i cant sit on devRant or Twitter without feeling bad about it.4 -
A dev I'm working with sends me an Android build for me to test, along with the following caption that put a smile on my face.
G'day,
Here's a new build that should have addressed most of the issues from your previous testing, as well as almost certainly creating countless others -
Story time;
Major project, multi million budget, huge business and IT coordination, board level status updates, meeting started back in March 2018 for a Go Live of Aug 2019.
Based on draft requirements (and experience) I request the test environment be built for half of the work. Turns out that no one told Server Eng and they are out of space in both dev and prod until Q2 of 2019. We went from Green to Red because a Service Request.5 -
To my dev manager: hold on... you are annoyed that one of our high profile customers found a bug in our software after upgrading to production because they didn’t test that feature in staging?? Did I hear that right? Yeah, let’s blame our customers for bugs that we introduced and that we clearly didn’t test during QA... that’s what we’re all about over here...8
-
Build pipelines are awesome. What's not awesome is forgetting the 'pipeline' bit.
Sure, let's have each TeamCity job in the 'pipeline' build the deployable from different places! You must manually merge your code from dev to test to release.
What's that? The functionality working in dev isn't there in production? I wonder how that happened. -
Finally made my node production server stable enough that I could focus on writing tests*. I start by setting up docker, mocking cognito, preparing the database and everything. Reading up on Node test suites and following a short tut to set up my first unit test. Didn't go smoothly, but it's local and there are no deadlines so who cares. 4 days later, first assert.equal(1+1, 2) passes and I'm happy.
I start writing all sorts of tests, installing everything required into "devDependancies," and getting the joy of having some tests pass on first try with all asserts set up, feels good!
I decide to make a small update to production, so I add a test, run and see it fail, implement the feature, re-run and, it passes!
I push the feature to develop, test it, and it works as intended. Merge that to master and subsequently to one of my ec2 production servers**, and lo and behold, production server is on a bootloop claiming it "Cannot find module `graphql`". But how? I didn't change any production dependencies, and my package lock json is committed so wth?
I google the issue, but can't find anything relevant. The only thing that I could guess was that some dependencies (including graphql) were referenced*** in both, prod and dev, and were omitted when installed on a prod NODE_ENV, but googling that specific issue yielded no results, and I would have thought npm would be clever enough to see that and would always install those dependencies (spoiler: it didn't for me).
With reduced production capacity (having one server down) I decided to npm uninstall all dev dependencies anyway and see what happens. Aaaaand it works.....
So now I have a working production server, but broken local tests, and I'm not sure why npm is behaving like this...
* Yes I see the irony.
** No staging because $$$, also this is a personal project.
*** I am not directly referencing the same thing twice, it's probably a subdependency somewhere.2 -
I need a bit of advice, I'm looking to rent a dedicated server for dev and test small projects and maybe host a site in the future but mainly a box I can access from everywhere and constantly online
I checked out ovh and server4you but I wanted real experience from a community I can trust, any recommendations?9 -
Small chaotic startup that never grew up (15 years atm).
Hosts/maintains a number of apps/sites for various customers.
At some point, someone decides that a CMS would be usefull to maintain the content across all products. Forgoing all sense, reason and the very notion of "additional maintenance and dev" it is decided that one should be built in-house.
Fast forward a number of years.
Ops performs routine maintenance on prod-servers. A java-patch accidently knocks out one of the pillars a 3rd party lib the CMS uses for storing images. CMS basically burst in to flames causing a.... significant incident.
Enter yours truly to fix the mess.
Spend a few days replacing the affected 3rd party lib. Run tests on CMS in test and staging environments. Apply java-patch. All seems fine.
When speaking to frontenders and app-devs, a significant hurdle present itself:
All test/staging instances of all websites/apps/etc ALL USE PRODUCTION CMS. Hardcoded. No way around.
There is -no- way to properly test and verify the functionality of any changes made to the home-brewed CMS.
My patch did indeed work in the end.
But did the company learn anything? Did they listen to my reasoning, pleading or even anguished screams for sanity?
No.6 -
Hello all,
I am .NET dev for a while now and web development was mostly my area of expertise. Lately, i got a bit bored with all this and as a passionate gamer, i wanted to try out game development in unreal engine. Naturally i had big plans and went for big PC game but soon realized what enormous task that is. That's why I decided to test myself with mobile games first. Here is the link to my first game created :) https://play.google.com/store/apps/...
If anyone is interested in checking this out i would like to hear your comments and remarks.1 -
So I'm currently "assigned" a task in which I need to fix a slow query problem, which isn't a big deal. The biggest problem is that the original team of this project haven't got any means to develop things on your local machine. Looking at their docs and scripts, it seems like everything is deployed to a dev server. But whilst looking for details for this server, I found out that the network team have decommissioned the server!
So my dilemma right now is that I can't test any of my fixes on anywhere besides staging, or possibly production! Inheriting projects is the bloody worst!5 -
FML having to take on and support a python test framework that looks like it was written by a junior C embedded dev without a mentor.
- Imports everywhere in the code
- No abstraction or OOP
- sys.path.append fest (broken imports of course)
- Global variables fest
- No docstrings
- No readme
- Somehow mixed with a jUnit test framework as well
- Uses Windows environment variables profusely
- Pycharm has a stroke when I open files from this project5 -
So I got reprimanded for some error on a site. I proved that this was a back end problem and that this has nothing to do with me (I'm just a front end dev). Didn't get a single apology, the dev who broke the thing got off scot free and now i have to work overtime while they publish the changes to test them
-
It's more of a QA rant....
A Website takes address information via POST. Since Selenium can not do POST properly devs said: "no worries, we will make the site accept addresses via GET url parameters"
Me:"Why not make a simple page with input fields that just behaves like the site calling our site via POST?"
Devs:"Nah we don't need that. Will be fine. We will ensure that POST service works via unit test."
Come release week... Dev:"Guys, POST isn't working, IT Analyst tested with the other site..."
Dev1:"Why did QA not test this earlier?"
Dev2:"He wanted to, we told him that we would unit test this. He fucking knew it. He fucking knew it so don't blame him!"
Me: :34 -
Not a true dev rant but still thought I'd share:
Systems team installed new software product I've been asked to setup and test. Within 15 minutes of getting into the software I've already had to open two support tickets with the vendor. Fast forward two hours and I'm putting in a third support ticket. SMH.2 -
PM: Can you help out writing a test suite for feature X? Really high priority!
Me: Ok, give me a day or so.
I get it done, and setup in CI-tool to test on the feature branch.
*Next day*
PM: It doesn't work! Can you have a look?
Me: Uhm yeah.
Only broken on feature branch of course.
Dev working on feature X: Ok pushed a potential fix, can you run test suite again?
PM: Yes, can you get on that asap?
CAN YOU RUN YOUR OWN FUCKING TESTS?
(╯°□°)╯︵ ┻━┻ -
I was refactoring a 4000 lines JavaScript file, turning whatever I could into components. It was a pretty old project that I ended up being one of the few wizards to actually know how most of it works.
At one point, I noticed that login into a user account redirected us to the dev-test server, even when working on a local Docker container.
I never quite understood the issue, but ended up having the bug mysteriously disappear.
Until it came back two months later, then disappeared again.
At one point, all of the dev team on the project (four developers, me included, and one project manager) was investigating the issue, and we never figured out how or why this was happening.
Just Symfony routes shenanigans I guess.15 -
Chrome likes to count teleporting goats, Android tests if the user is a monkey. I like to put "void fish(object look)" in my code and throw the fish where ever I wanna test something.
What are some interesting functions you've added to your code? Has another dev caught your function yet? (mine hasn't been caught yet, yay!)3 -
I've recently done 2 interviews in the past 2 weeks, I did 3 stages for the first one and failed the last stage. I felt devastated. I did the 2nd one Which had written and oral, I feel like I failed oral,results are yet to come out. I have 2 interviews next week and I have no energy to prepare. I feel lost and tired of preparation.2
-
So my peers are making a hybrid android app and I'm managing the back end, at the start of the project I told them to publish it to the play store to test if it will pass any rules ( I assume there are automatic inspection or whatever) we are near the launching fase and we don't even have a dev account there yet...
-
I finish my internship in dev the next week and my supervisor wants to hire me as a Business Analyst, for that I have to pass some tests in an assessment center.. I hope I will success it ! 👊undefined internship analysis analytics analyst business dev businessanalyst developer fun team test1
-
Trying to convince the class that test-driven development + DTSTTMPW ("do the simplest thing that might possibly work") + pair programming is the way to go, our software dev prof had us split in groups of two that would each get a turn to
1. add a unit test
2. edit the code so it passes the test
3. commit the change
The goal was to write a java class that converts integers to roman numerals.
Each group had only 2 minutes before the prof made them revert their changes.
After 45 minutes the code was just 10 lines of this:
if ( n == 1 )
return "I";
else if ( n == 2 )
return "II";
else if ( n == 3 ) ... -
Helping out a team, I was documenting some code/processes when I came across several classes that was logging a lot of, IMO, 'junk' that was unnecessary (and I knew wasn't being used in any Splunk alerts/reports)
I offer a refactoring suggestion, simplifying the data being logged, moving the duplicate code to a central location, maybe saving 10~20 lines of code. Didn't think it was a big deal because they were already actively working on the code and it was all new code (nothing deployed to production yet). Sent the suggestion to the lead developer and he responds:
Dev: "Yes, the changes looks fine, but not in scope of the project. Any out of scope work will need to be suggested at the end of the project, reviewed by the team, the project manager and approved by the vice president."
"Out of scope"? Logging data to Splunk needs a vice president's approval? WTF?
YOU PROBABLY HAVE THE PROJECT OPEN IN VISUAL STUDIO RIGHT NOW!!!
Along with the documentation the lead dev said they didn't have time to do, I send his boss and the dev team my suggested changes (before-after screen shots of the code) and offered to do the 2 minutes worth of work (again, this was new code, nothing in production and zero side affects to anything).
I even offered to create the splunk reporting/alerting against the data being logged (another item they said they would not have time to do)
About a minute later the lead dev responds..
Dev: "Those changes look good. I'll have Jake make those changes and we can test the logging when we deploy to dev on Monday. Thanks!"
Of course you will...fracking ass hat.
I'll bet my Battlestar Galactica DVD box set he was going to make the changes himself, brag to his boss how he refactored the code, saving X lines of code..blah blah blah to help *me* with documenting the logging portion. -
In recent time my anger comes from a junior dev who keeps saying he's got no time to test and breaks working code leading to others getting the blame and the team leader not addressing the problem.
In the past it was micro managing managers who thought they knew how to make a UI best, and also that one project where they gave a client carte blanche on changes to avoid legal trouble. Nothing more infuriating than multiple people telling you how to change things over and over while you're being passed around in their power struggle.1 -
Why the fuck is gradle so horrible.
I literally have no idea why anyone would ever use this thing (other than being forced too because somehow the rest of the world is using it).
Every plugin has an arbitrary DSL that you have to magically know by piecing together enough snippets. At that point, no one is actually intuiting anything based on the beauty of the DSL, every build is a frankenstein of different snippets that were pasted from different versions of gradle blog posts or SO posts.
And if you do get it o work then the DSL changes, or it isn't compatible with another plugin.
I just want to write a fucking integration test in Kotlin. Can I just add an `integrationTest` task in `tasks` right next to `tasks.test`? No, obviously it goes in the `kotlin jvm() compilations` section, DUH.
The first thing anyone in the universe should have asked is "how is this better than literally hand writing a makefile"? At least then I would be able to see the commands that it ran.
Now I'm googling how to make the new jvm-test-suite plugin work when you're using the Kotlin plugin but every single result on Google for `jvm-test-suite kotlin` just returns the docs for jvm-test-suite (whose snippets obviously didn't work in my project) because those doc pages have "Kotlin" written above each of the gradle snippets.
Please just end this.
Oh and dev rant sucks too. It thinks anything separated by dots in a url.2 -
Is it sad that I look forward to the weekend so that I can actually write some code rather than:
- Helping clients that can’t / won’t read docs
- Explaining to test colleagues that we need repro steps and can’t fix a bug based on “I was doing something and it crashed”
- Writing any regular expressions for another dev where it’s more complicated than ^[A-Z0-9]*$
- Wading through legacy VBA that’s littered with GoTo, global variables (even i, j and k for loops are fucking global!) and all the other fucking lazy shortcuts that save you 10 seconds at dev time and cost you (which ends up meaning me) hours in subsequent debugging.
I love writing code, and I think I’m pretty good at it, so can I please just get on with it?
Fellow ranters, please tell me I’m not alone in this. -
New android dev joiners... Never Ever... I am saying.. never ever update the test devices in the office...!!! 😣😣
-
!dev?
Colleges now require proof of vaccination but admins are worried about the spread of fake vaccine cards
https://apnews.com/article/...
My mindblowing solution: require students to submit a covid antibody test result instead.
You can't spoof the lab test result number and it can be easily verified by calling the lab...
Can even create a site for that...
isTestValid.com
Worried about privacy... Have labs upload a hash of the data...
And user submit their hash...
Clearly nobody asked a dev for they're input... again3 -
Dev: [does some weird code to make test pass]
Me: this won't work. Literally the documentation says what you did won't work once we move towards our end goal architecture.
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
.... One Sprint later nothing works...
Dev: [does some weird code to make test pass]
Me: no. You need to solve underlying problem.
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
.... One Sprint later nothing works...
Me: please stahp
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
Me: WTF man do your fucking job
Scrum Master: stahp lowering our velocity
Me: wut? 😒2 -
life as the only dev at work:
boss: so the new system is finished now right?
me: its finished enough for people to log in and test it
boss: so its finished?
me: .... suuure -
Going back to a project from a few months ago, a fellow dev has committed 'test this' comments with my name...
Hitting up git blame shows my tests were written 2 weeks before! If you're gonna be passive aggressive, at least do it right :/ -
This week the QA is on vacation, so we, the developers, are testing our own code (I test my partner's code and he tests mine).
For those who are QA, I have a question: If our boss omitted something on the description of how the code has to be made, for example, filtering data from database, and one of those filters are needed but the boss forgot to tell us and, at the time of making the tests, the QA and de dev team notice this... the change that has to be made should be marked as a bug? or how would you mark it?1 -
target env: tomcat 8 on linux
devs local env: uses springboot 1.5
deployment time....
me: hey it does not work as expected.
dev: but it works on my local machine.
me: have you tried testing it with standalone tomcat maybe integrate it on intellij or containerize perhaps?
dev: (refused to test on standalone tomcat) it’s useless and it doesnt makes sense coz both are the same.
me: fuck let’s deploy your laptop on
all environments.
geezzzz :-| -
I'm in a situation at work where management and even the team I'm on, does not want to create a test suite, because:
1. It takes time to get decent code coverage. Time that could be spend doing new features
2. My team doesn't like to test.
We're now in a situation where we break something every single fucking time we relase and the manager just ignore that it's now a common occurrence. It it literally just a matter of time before the entire fucking backend will shit itself over poorly maintenanced code (who has time to do refactoring anyway) and poorly tested flow.
It annoys me greatly that a developer with many years of experience fails to see and understand that just doing test by hand, screws us over so badly.
As a junior dev, i would like to know, how are your team dealing with testing?
Because we're clearly not...9 -
As my first dev job, I took over role of solo programmer maintaining all kinds of custom-made software used by local ISP. It was about 10 years ago.
My first question was where can I find test environment and repo. Apparently there was none and I should learn and develop on production.
My sin was to quickly give up on setting up both test and repo.
My second sin was to continue using the same copy&paste PHTML with register_globals enabled, building over it without attempting to refactor it with templates. I did not use globals in any new code at least.
And I suppose my third sin was that I was playing games when I was done with my tasks. I could have used that time to refactor a bit.
But I think in the end I was absolved from them since I was the only one suffering from this. I stayed with company until it got sold and helped migrate data over (along with myself). -
Weblogic Server won't start, broken build was auto-deployed. How does a broken build even get deployed? 🙄
Told "till the server is fixed work on your next-release bugs". Sure, can investigate, maybe even code fixes, but with a broken dev environment how do we test anything?
" Hmm..Oh yeah, right" 🤔 -
!dev
So my (public) health insurance should cover a test I'd like to make. But if I don't want to call a bunch of clinics every week for months only to get an appointment a year later eventually I'll have to pay myself (to get an appointment in a few months instead). -
What do people think of automated code generator frameworks such as Yeoman and Plop? Any experiences to share using those or similar frameworks?
I like the idea of automation, it means code will be consistent (especially across teams), and it means less boilerplate writing that potentially breaks thought processes.
But then does it just waste time? It's something extra to develop, test and debug. Further most of dev time is reading, thinking and modifying.2 -
I fucking hate the way we have test in our company. They're worse than useless. They test internals but don't test the actual fucking behavior. I just broke the dev branch with a stupid mistake - because of course one of the core behaviors of our app is not tested. But I had to fix tests in three places just because I removed a useless util in favor of using a built-in JS feature.2
-
"Oh I knew they'd say that it's why I didn't get them to test it "
Did these words really just come out of your mouth? Who the fuck left you in charge of planning this shit?
Some team manager requested dev work it got approved and done standard. However they knew from the get go their team would rip it apart so when it came to the testing phase did he get his team to use it?
No he pulled fucking random people from other teams who don't use this feature at all in their day to day to test and sign it off.
Sod your vision mate. Our team just lost two months of work your team's productivity has dropped because you had a picture of how things should be but didn't want to be told no. And for a fucking valid reason your method is shit.
Don't think he'll be left in charge of a project anytime soon. -
!rant. Doing some great new stuff at work to make our dev team's live easier. Finding out how to use Docker for our automated test setup, that's killing 2 birds with 1 stone.4
-
Working for friends that want to launch a start-up, providing them with what sounds like reasonable advices to me e.g 'maybe test your concept with some leads before asking me to develop the website', 'focus only on the main 2-3 features so we could launch quicker as I am solo dev on this' and 'once set, don't change everything every morning as I cannot make progress on the site if you keep asking me to code X versions of your fucking landing page (that they don't use)' and the only response I got goes like : "okay okay, BUT we've decided to do it this way, no need to test, customer will love it for sure' SURE ! But I am the only one to have a job and sleeping 3 hours to code your shit at night, while your lazy asses remain peacefully waiting for it to become 'the new Amazon' !3
-
Wanted to get to bed early tonight, but ended up wasting two hours after I moved code from my development machine over to a test system and it was failing. After adding all kinds of logging to figure out where it was failing on the test machine i realized i fixed am error in an input file on my dev machine, but that error in the input fine was still there on the test machine. Another night with little sleep and tomorrow is Monday. 😭
-
While I haven't been officially hired for any UI dev jobs, there was one front-end position I was going for where the hiring manager viewed my programming test for the application process and just sort of gave me a "sorry, we're choosing not to move forward with you" email even though my code was simple and refractored. When I thanked him for the opportunity and asked for feedback he just kinda disappeared without a trace.
I understand that time is money and maybe they just didn't want to spend the time responding, but is this kinda thing normal?1 -
I need help for a dev test.
So the company that I work at is hiring a couple of new devs and they’ve put me in charge for test in order to see if the applicants are any good.
When I was hired there were no tests so I don’t have that many ideas for a good one.
Have you guys any good recommendations for a test or what it could consist of?
I’m thinking of having multiple small tests so if one misunderstands the task it’s not the whole test they fail. Would that be a good idea or not?
It’s for senior and junior web developer.
Any idea is greatly appreciated 😀5 -
So my phone is currently in the service center. I am using company test device to get by.
Software tester consultant at work brought home the iPhone test device that I wanted to use. It's been gone for a few days.
One day he returned it to the office and then it's my turn to use it. Peeked at iMessage. Turns out he gave this to his wife/gf/whatever.
A message thread reads:
Gf: Are you hanging out with devs?
Bitch QA: No, would never hang out with people under me.
Bith gf: as should be
I am not under you dick. I'm the project lead, you are under me. it's just that I help devs so I dev too.
I won't let you stay long in this company bitch with the way you think of devs. You are a tester, you work for devs bitch.
I remember that quote, you can judge a man not by how he treats his colleagues but by how he treats those below him.
And bitch I am judging you to be dick. You won't get what you want here, you won't abuse devs.9 -
The time that I felt most like a Dev badass was when I had introduced an E2E test framework and added a bunch of helper classes to it so that our QA team could pick it up and write automated tests for the manual tests they had been doing for years.
Sure, the whole department got laid off after that because we had gotten a new CTO and all of my work was essentially for naught, but it made a lot of people enjoy showing up to work for the first time in a long time, and that was what mattered most to me -
Last week we were only one step ahead of going in production mode with the angular web app i coded a half year long. Sounds good right?
Yeah this morning my boss said in the dev Meeting, blazer is now in preview mode, let's do it with this tech, so our full stack is in c#...
He is not a web dev. He want to step back from coding in the near future, but yeah let's use fucking Blazer 😥
For the rest of the day, i started with a Blazer Test Project.. great start into the short week.
How about your start?6 -
Dumb mistake from when I was still working:
My work laptop’s SSD went haywire, and I/O would spike every 10 minutes or so for ~50 ms. The hardware guy said he could replace the SSD right away, or I could endure it for a few weeks and get a new laptop instead. Obviously, I agreed to wait. The stutter noticeably affected screen rendering, but I didn’t notice any other issues. Little did I know that every time it happened, all input was ignored (as in: not queued). Normally it wouldn’t matter, because hitting a random ~50 ms window is hard. How-the-f×ck-ever…
A few days later — without getting into “why” — I was forced to apply a patch in production. So I opened an SSH session to prod in one terminal, spun up a dev environment in another, copied the database schema from prod to dev, and made sure to test everything. No issues, so I jumped to prod, applied the patch, restarted services, jumped back to dev, and cleaned up the now-unnecessary database. Only to discover that my “jumped back to dev” keystroke didn’t register.16 -
Now i am given a task to refactor some piece of Predicate code and then update the unit test so it can be compatible and work with new data
WHAT. Is the Fucking point of unit tests if you have to modify them to adapt to new code anyways???
Unit tests exist just so u can stroke ur sausage??? Just so u can give ur ego an orgasm to tell others "hey look at me how good code i wrote that even unit tests are passing!" ???
I always found unit tests sketchy. almost as if its useless and unnecessary. I still get why they are used (some other dev working on feature 2 might break my shit and unit test can save the day) but if thats the only reason then that doesnt seem like a strong enough reason for me
By now im talking about java!
No wonder i have never seen a single nextjs developer ever write a single unit test. Those people have evolved beyond unit testing just as the nextjs technology itself!
This is why nextjs is the future of web and the Big Daddy Dick King 👑 of technology!8 -
A peace of work to be done within 2 weeks for 3 devs
1 dev gets pulled off the team, the other decides now is a good time to take a 2 week holiday
So am the only one left and because the designs weren't even ready for the first week i only had a week to do it, i managed to finish it with some defect obviously, and testing oh yes the testing non, non whatsoever. Only test i had were snapshots. Other than that, nothing. So the demo seemed to please everyone and the whole team got praised for some gr8 work, work that was estimated for 3 but done by one and hah no testing...yet1 -
Test functions that are longer than a screen and requires a team of scientists and archeologists to try and decipher WTF they were trying to test and why they might be breaking...
Extract method -> give reasonable name -> save sanity of next dev to try and work out wtf is going on -
How do you feel when you built like 90% of a project, all the main logic and then you hang out over to another dev to basically clean it up for you?
Like optimize some queries, build the frontend, test it with the users.5 -
Don' you just love it when your project leader's superior (who is not involved in development or know a thing about the dev process whatsoever) barges in and asks you to port a project originally targeted for Oculus (and so, very graphiclly heavy) to Android in less than an hour? Obviously when it's not done on time, has performance issues or randomly crashes on a different API it's the dev's fault, not the shitty decision making behind the managers. (btw the company doesnt even have android devices for us devs to test on, we HAVE to borrow them from other colleagues). FML!!!!2
-
!rant
This situation, when you are working as external employee in a company that needs you to test safety-critical systems.
You wait months for "THE" (internal) test tool you have to use to implement your specified tests.
Finally , you meet with the responsible dev guy to let him setup everything.
Me: Hi, I'm here for setting up the test tool for project XY
Dev: Eh? No one (manger) ordered the tool for project XY!
Me: -
I don't program for days on end. It takes a few weeks and then I fell good about it again. Sometimes I wonder if I even like programming. I do well in college, but I've never had a job as a dev (aside from student "research" positions). I'm worried that I'll just burn out and get fired or quit and lose interest. Maybe I already have? Can't think of any side projects to develop either, they all seem out of reach. Still figuring out how to cope with it. The test grades don't do it for me anymore.1
-
So this is the most idiotic thing I have ever done!
Was resolving an issue in a module in our application on "Test" Instance, instead of uploading file to "Test" I was uploading to "Dev" and I was wondering for the last 2 hours why the hell changes are not working!!!
I need a break, Thank god its half day today... its a rest day now 🙈2 -
Is QA bad at all companies or just mine? We ask QA to test changes from a list of changes. They come back with existing bugs outside the scope of what they were testing. Waste our time talking about irrelevant and out of scope bugs, then when corrected they respond "what would you like me to test?" Then I try to refrain from snapping and say "test the original items on the list like we originally asked you too... Agh. I really don't like working with our QA. They slow everything down, they cause delays because they don't grasp things. And it wastes our dev time, we talk about the same things over and over. Ugh.2
-
While showing the rest service demo a senior 10+ years dev ran into session issues in chrome. I asked him to open private/incognito. He opened ie,edge, closed all chrome, tried back, nothing. Had no clue whatsoever.
At last I asked him to do ctrl shift n in chrome & dark chrome opened up where he could use the test accounts to validate the bugs. He is still confused what happened4 -
What are staging systems for?
In my opinion (and of my dev co-workers): that everyone can test the software before it’s being deployed to production.
PM (at least based on how they act): that we devs test our software. They will test it when it’s live.
Today: cookie banner was missing, and the page has been on staging for around 3 months and it already has been live for 2 weeks.
No. One. Noticed. That. On. Stage.
Ridiculous.4 -
Somewhat dev related (behavioral interview)? Just thought it was funny.
https://webtoons.com/en/comedy/... -
Using a library that is a wrapper around an API, seems to work fine and I can connect to the api with my credentials.
Cue me, a responsible dev, wanting to use Dependency Inversion using the library's interfaces so that I can mock them easily in tests.
var test lib.IObjectManager = lib.ObjectManager{}
Error: Return type of method 'GetA' is A and should be 'B' according to the interface!
Error: Return type of method 'GetE' is *E and should be 'E' according to the interface!
Clearly nobody ever tried to use that interface :/ -
Job Interviews and technical tests...
Why when interviewing for full stack Angular(typescript ) / C# do they expect devs to be as good at C# as a 100% dedicated C# dev.
Why do they expect them to be as good as a 100% dedicated jQuery/pure javascript dev when 50% of the job is for Angular/typescript. WTF?
Full stack devs typically are constantly jumping around between tech stacks so they're always "working it out"
You hire a generalist because you want a generalist. Don't interview and test them like they're 2 specialists combined into 1.2 -
Question: How would you reimagine the dev interview process, trying to make it efficient to find ingenious freshers?
I'm gonna be hiring full MERN stack dev freshers soon. I hate coding interviews, and I just want to test their ingenuity and problem solving, not if they can code a textbook algorithm.
Plan so far was to ask them questions like: "What happens when you like a link in the browser" to gauge how deep they could track a request and understand the internet infrastructure.
And make them audit gpt generated react code, and optimize it.
What're your thoughts, folks?8 -
I have the image of every member of this community to be some top shot dev who's frustrated because others can't keep up. You get that image from the types of rant you see...
It might be the case that the guy who posted a rant about his manager being useless, and the rant getting 100+ ++ is someone who would have never written a test case in his life!!! (in my opinion that's more bad than a shit manager)5 -
I worked as an backend dev the last 2 years and was maintaining and connecting external APIs to our system. If one of these did not work properly or their test system went down I needed half a fucking day closing all JIRA issues named "EXTERNAL system not reachable" . Who needs speaking error messages anyways...
-
This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...
Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Dev: yes
Infra Guy: u trying to get set of specific folder for set of specific components?
Dev: yes
Infra Guy: bash script with cp or mv will not work for you?
Dev: no
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Dev: (((((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place3 -
Two years without working on web dev. Planning to build a website.
Any frameworks that i should test?8 -
A dev decided to overwrite the master branch with his code saying its better. That it fixes the major bugs that all of us couldn't solve.
Against my better judgement of firing him, I decided to test it.
Firing up the testing site, we made test databases to use and we went to house.
In the middle of testing, I noticed the test DBs weren't being changed. While everyone was still testing, I looked at the code. It wasn't made to test on any databases, it was specifically designed for the actual production server.
However the damage was done. In a secret dashboard in the code, someone sent instructions to drop the tables, effectively ruining the production server.
We had the dev go to an offline backup site that only went online every 10 minutes a day to make new backups. So we shut down the production server, setup a maintenance page. I get my ass chewed out again, and we were sitting ducks.
I don't think the dev had enough punishment, so I grabbed his laptop and made a full backup of his data, and locked the SSD in a safe.
I downloaded a Windows 98 and put it on a flash drive. And installed it all on his SSD. The dev is now a proud (pirate) owner of Windows 98.
He came back and started balling on his desk. We all looked at him with a pity, but he deserved it.
I'll give him the drive on Monday.
Do you think he learned his lesson?7 -
So last week there was a meeting at my workplace. In short the meeting concluded that me and 3 other devs gonna develop a fairly complicated system. I was happy to test my skills after 2 years of bug fixing in already working systems. Yesterday I found out that other people gonna do it with an other technology and I'm stuck with bug fixing for God knows how long...
Ps: feedback shows I'm not a bad dev.7 -
PO writes a story. We groom it. Point it. Do the work. Finish the work. Dev test it. Push it to test. Tester find a weird edge case. Talks to me. I agree it’s weird. I talk to PO and the PM in the standup. PO realizes the whole business flow doesn’t make any sense. Changes the AC. Asks us to change/redo shit. 2 days until the end of the sprint.
I guess I’m working this weekend. Not that I have to go anywhere 🤷🏽♂️4 -
i have experience in mobile dev for 3 years,today i got interview for coding test,it have 10 question,i cant answer question 1 so it stuck there until time out.the question is so fcking simple but because i more focus on framework and only have basic in kotlin/dart so i really like dumb people when interview,the 3 years experience is gone just like noting,even i forget toString use () ( so toString() ) because usually vscode give suggest the method
-
Recently I had the "pleasure" to participate in a recruitment process for a web developer internship position.
First of all, a nice lady calls me to confirm everything and sets up a meeting. She mentions about a qualification test and gives me several technologies like python, c#. I was confused but we explained everything and she knew I was not interested in these technologies since I didn't apply for python or c# dev.
Later on I go to their company building to take the test. I get the test, I overview all tasks - 80% of the test was composed of OOP and C#. OOP - this I can understand but fucking C#? Seriously wtf? I wrote the test the way I was able to do it and at the end the guy says it was deliberate to put other technologies so that he could check how would we find ourselves in a situation like this.
Honestly, I felt like the whole process was a big joke for them. I wasted time going there just to see that I'm taking the test that includes the things posted in the job offer only in 20%.
Fuck them. -
I spent hours setting up Laravel Valet on Ubuntu (virtual hosts with a custom TLD) e.g myproject.dev
I just found out why it was not working. Because fucking Google bought 100+ domains in the .dev gTLD and added them in Google Chrome Hosts as well. Now they redirect the url automatically to HTTPS.
Any ideas on a new test development TLD?
I was thinking .fuckgoogle but that's too long7 -
I have an app I have developed that uses concurrency. My dev env allows me to select different targets. One of those targets is WebAssembly. So I got it configured and decided to test my app. It immediately failed on compile due to the concurrency module missing. I later found that for my dev env concurrency for webassembly is experimental.
So concurrency is a thing for webassembly, but the support on my dev env end is not there yet.
Is threading difficult in webassembly?2 -
I've been working as a web dev intern for my college's IT department for about three weeks now. Knowing that I have the access to the cms, file server and database... Muhahahahahahahahahaha😈 but I guess I will be a good boy and only screw around in my test environment.
-
Recently had an issue where we forgot to deploy some API updates on live when we pushed an app version live (we test on dev/staging)
Does anyone have any experience in mitigating this risk? Can't do a final test on live since that has permanent side-effects (e.g. Automated emails getting sent to other users)2 -
Released the product to customers without realising someone had pre-filled a production test accounted login at the login screen. Obviously it was used for testing purposes and the dev forgot to remove it before committing.
I loled when I found out about it, and some customers started to login and made transactions.
When I checked the commit history... It was under my name :/2 -
Just pushed the last commit about a work they asked me in the last job interview. Please wish me good luck!2
-
Recently we've checked /sprint in HipChat to test batching of sprint status messages. For testing we wrote what first poped into our minds.
One Dev wrote /sprint We're on schedule
Another wrote /sprint Everything is broken, help
How different tests and first thoughts about progress sometimes can be?1 -
Just did an elixir job interview for tsg global, 10 hr test, got the email of fuck you email. Do not fuck with this company they will scam you out of your time i should have spent my 10 hrs wiser lesson learned, im going to be a homeless elixir dev with 20 yrs exp. All cuz parasitic companiess like this. I submitted a prod ready solution that was most likely what they wanted built and i did fir free cuz i dont wanna be homeless. I hate life.2
-
!rant,
Belonging to the last 3 of the intake procedure, tomorrow a final test and then im a php dev maybe WOHOO -
Was using an open source piece of software for data storage and visualisation to work with the loggers my company makes. When importing old data for historical views, some of the csv imports would fail without any specific error messages.
It took me a couple of hours but after looking at their csv parser and making my own little one to test with, I eventually found out that it was all down to the way datatime (I think it was?) in java deals with DST, which apparently was to just fuck shit up.
Anyhow, a few simple lines added into the parser later and it all works just fine.
Was super proud of that one as it was the first time I actually looked somewhat good in front of my senior dev. -
What would be some good interview questions for a software QA candidate? as a dev myself, I've mainly interviewed other devs. I have a sense of what makes a good QA candidate, but I'm seeing a lot of QA CVs don't have development experience on them.
Background: In my group at work it's manual QA right now and we could use someone to also help lay down standards, which I could turn into requirements for test frameworks.
Had one interview already but I don't think it went that well, so I'd like to be more prepared.4 -
Unit testing with NSubstitute and Autofac
For the most part, I find it a lot simpler than SimpleInject (hmm) and Moq, which I have used previously.
But there are still some of those 'Oh, for fucks sake!'-gotchas.
I was trying to test a class today where I wanted to substitute all other methods in the class than the one I wanted to test == an actual unit test.
I had previously found out how to do this:
1. Make sure the methods that should be substituted are internal to allow substitution.
2. Substitute class with Substitute.ForPartsOf<T>(args)
3. Set up methods that should not be called with instance.When(a => a.Method()).DoNotCallBase()
This way, you can unit test a class properly and only call the method that you want to test, and also control the return values of the other methods if needed.
So as I said, I have used this before to great effect. But today I just could NOT get it to work! I checked and rechecked everything but the test code kept calling the implementations of the substituted methods!
I even called over another dev for help, but he couldn't see the problem either.
Aargh!
I scoured the internet, but everyone just told me what I already knew: follow the 3 steps, and all is well. Not so!
I ALMOST considered doing the test improperly, as in, increasing the scope beyond that of the method I wanted to test.
But then it hit me... My project was missing this line in AssemblyInfo.cs:
[assembly: InternalsVisibleTo("DynamicProxyGenAssembly2")]
I always add a line to make internals visible to the test project, but I had forgotten that NSubstitute needs this line as well to work properly.
Sometimes when a test fails it will tell you that you are missing this line. And sometimes it just doesn't work.
Maybe I will remember this in the future now. Maybe 😅 -
Devs from company that develop/modify a service for us say "you can test on <env>".
Description of how to test: scattered across multiple tickets, comments and slack messages in multiple conversations...
Oh and please... Could you not directly merge 20+ branches directly to the dev branch without testing...
So much going wrong with this project... Already a month overdue on the first release... -
!rant && dev
Before I dig deep and pick the minds on S/O, I'm trying to test an app (Cordova) on my wife's phone (Samsung/Android 7) - the feature I'm testing works fine on mine (Huawei/Android 8).
Where it seems to be faulty is making a WebSocket connection to my server - is there any known issues people are aware of? Recent security updates or something?
I'd jump straight on to USB debugging, but last time I tried to do this on Samsung, it simply failed to show up as a known device - tried loads of drivers...1 -
Conversation with fellow dev this morning:
Him: What are the chances of putting an API for this in to staging?
Me: I'm working on it now.
Him: Good stuff, so if I check this other one, it should go through?
Me: Yes, it should.
Him: I'll test it now, because "should" === "shudder"
Me: "should" == "shudder", but "should" !== "shudder" 😉
Him: Shud up 😆 -
We are building a cloud iot environment currently for one of our customers. I'm kind of the head of the cloud backend. Well first the customer needed the product a month earlier. Then today on my last day before vacation, they wanted to test theire devices in our dev environment. Have they ever heard of read only friday? And why do people still fuck up json payload in 2020
-
In the middle of a deployment call and the dev wants to "add a feature" on the fly (what could go wrong right!?). Next thing I here on our phone call is the client saying "great idea let's add that feature now! I'll wait to test!" Wait... WHAT THE FUCK is the client doing on this deployment call?!1
-
Whats the fucking purpose of our companys dev test and prod env. Dev always only has a single instance. Sometimes clustered services run as cluster on test. Producing headaches because the clustering behaviour couldnt be seen on a single instance and Prod lacks all the nice deployment tools off dev/test. Fuck thinking you could dev then test and prod without any major reconfiguration and headaches. And all because the Storage costs is RETARDEDLY expensive because the backup EVERYTHING with ridiculess overkill. That results in headaches when requesting new servers. Took an old Workstation from the shelves and made it my vm slave so at least i could reliably deploy to test.. Fuck this process
-
Congratulated a Dev at my company after he had finished all the functional testing...
Until he mentioned that he just needs to tweak the test to work with the new code now.. -
Having some lazy scrum team members and it is getting out of hand. For the past 1 week or so we have one dev who's daily standup written report is: regression. In our test case summary I can't even find her name, which means she is not doing anything.
Same goes for two of our new QA's who joined like 2 months ago. We have like 20 ready for QA tickets pending, but QA is saying that they are doing regression. Yet when I check how many cases they actually covered, it's something that even I as a dev during my first weeks in the company would have completed in a halfday. Right now we have one senior QA guy who is doing all the heavy lifting and I want to change that.
Wondering how to politely call out their bs during standup? It's kinda annoying seeing them covering their lazyness with "regression" for two sprints in a row now :)3 -
Me: Assigned to do some NoSQL injections test cases in December on Jira by product owner.
After asking him about it, he said it can be vague and it’s only for developers to get an idea. I also have this restriction where I can’t really keep actually data or databases in our test sample application, so I could only mock mongodb. Product owner says just mongo is fine.
I do it. Now it’s January, product owner away for a month we so director is managing it. She then schedules me to talk to database team. I show them the very simple test cases which essentially just inject payloads I found online into different parameters specified in test case. They say if that’s it. I say yes. They say what’s the point of this. I said that it’s probably to test your database clients and ensure they’re rejecting bad Malicious input? They then keep asking but I’m just the dev and tell them the product owner is away. Then the guy calls my test case essentially useless and the others agree. Then they tell me to do it for other databases which I can’t mock like couchbase even tho my PO said it’s fine for mongo only.
Am I just being silly here? I am pretty new to working in a dev environment so please feel free to be blunt.4 -
!dev && dev_workflow
Hey guys, what are your favorite truly wireless headphones?
For context:
- my OSes: Android (phone), MacOS (laptop), iOS (tablet).
- my getting in love with wireless audio story: I have been using some Chinese ones off AliExpress just to test out the truly wireless waters, their sound quality and pairing experience especially on Android is pretty shit but the ability to forget that you have headphones in your ears and just listen to music obstruction-free is 🔥 but they are now dying so I am looking for a replacement.5 -
In my current role, it takes 10 min to build and test a backend change. Front-end dev server is also painfully slow. It sometimes takes minutes for angular dev server to upload changes.
What am I supposed to do during these scattered idle time. Everything seems painfully slow1 -
How to set the up a stagging environment for a github branch in heroku.
Lets say i have a master branch and a dev branch. All the changes and updates first pushed to dev branch and after successful review and test in goes to master branch.
But the issue is as i'm following the gitflow of keeping the master branch always deployable.since my heroku app is linked to the master branch, when i try to test the dev branch in production environment of heroku,sometimes it breaks for some error.and at that time the sites goes down untill i redeploy the master branch as it's the stable version .So how do i test a branch in heroku production environment while also keeping the the site active with master branch. it that makes any sense 🤡 plz help3 -
IE Edge is supposed to be the browser to hate as a dev. However over here for my new temporary PC it isnt installed at all. Windows 10 WTF?! I need this shitty browser for test purposes1
-
Team lead gave me a task, fix a script he made to update 28k+ lines that wasn't working (he was busy with other stuff)
So I fixed and tested it in our dev environment, which had about 10 lines to use as test
Worked well, but a single select getting 1 column in a table is taking more than 40 secs, I need this select to run for every line (I tried making it get all data at once but it was getting duplicated entries)
The damn table doesn't have index, I think this will be the longest script I've ever made 😅😅😅 -
I need to change how payments are applied to invoices.
ApplyPolicyPayments() looks promising! Make changes to the method to look at the bills in order of the invoice due dates.
Run a test on the DEV environment, and the system is still exhibiting the same bug.
At this point, I wrote a quick logging plugin that I could attach to the DLL and start telling me what is going on.
Turns out, payments are actually applied in a method named BalancePolicy(). So what does ApplyPolicyPayments() do? It DOES apply payments to bills, but then just doesn't save the work. Having it commit the transactions breaks the billing system. FML. -
I know unit tests and TDD get a bad wrap but I think they’re both great. The problem is people don’t think about what they’re actually coding.
Today I uncovered a unit test with 100 asserts in it.
And half of them are in a loop.
😳
If unit tests weren’t a thing then the dev who wrote this would still be a shit dev.4 -
I read this rant about IE (https://www.devrant.io/rants/514347) but could not relate to it (I use Linux MS suckers!) So I thought I'd post a browser rant of my own, and this time it is about Chrome (or Blink since it also affects Opera). Whenever I start typing localhost Chrome suggests "localhost" but when I click this suggestion it takes me to a Google search result when all I really wanted was to test a webapp on my dev box. This is very annoying every time.
-
Have so many hats squeezed on that i think my blood supply has been cut off from my ... uh what's that called... you know, cpu's but for humans. Something with a b ...
-
Context: I am leaving my company to work at a data science lab in another one.
My senior dev (with PO hat): we need to gather data from prod to check test coverage. You will like it as you will be data scientist hehehe (actually not funny). You will have to analyze the features, and find relations between them to be able to compare with the existing tests
Me: oh cool, we can use ML to do that!
Him: Nope, we need to di it in the next 3 weeks so we need to do it manually.
Me:... I have quit for something.... -
My previous job was Engineer ( Ops part of DevOps), supporting the devs with VMs, configurations, dev and test environments, CI maintenance, DBA, DB-dev and such, it was sexy.
In my current company, I have no technical role, but today's task: build a small webpage in sharepoint in HTML.
And the perv part is: it's still bettet than having no Technical task at all...2 -
Why is it acceptable for dev think it's ok to skip testing? WHY?
Today i was told that a co-worker had good enough judgment when it comes to CSS if it will break in other browsers other than chrome. I'd accept that if they knew the browsers inside out and read all the release docs but no, not them. Even more so when it's not their field of expertise.
After working for 2+ years at the some company, with a QA team, it's become evident no one does any proper testing, even the friking QA team!
I'm close to define the supported browsers as "What ever the developer used at the time of build".
Am I really the only Dev to test in at least 2 other browsers? -
When the fuck did valet go from .dev to .test. Fucked me over bug time. Needed up breaking dnsmasq and had to rest the whole system. Sys noob. I can program though 😂
-
HOW to document business logic in code?
background:
I'm a frontend dev for admin system of our company. Often times I code things like: if user choose this product type and that settings then I show some other input field to input. I deal with mostly forms and show/hide UI for user. And after some time nor did user/PM/test or myself remember the logic of what should show or why something do not show.
So I want something to be able to let me write code and business logic along the way.(I'm not asking for API docs or function docs like JSDoc)
Great Thanks
Related topics:
And In terms of this, I would also like to build something to centralize PM's business DOC with developers API/dev Doc and also things like how to test for our test team and etc... basically a unified place to document everything, I think scenarios like these inside companies should exists so I would like to know how other company do this.9 -
Looking into devcontainers, trying to avoid having to install every little piece of 'dev tool' into my system, so i can savely test rust.
The CLI to manage devcontainers in the standards requires yarn and nodejs to be installed, and further more is another little piece of 'dev tool'. nodejs literally destroyed my system multiple times, and is the whole reason why i am cautious about installing random tools in my system in the first place.
I feel so alone in this world sometimes.5 -
A young new dev was working on his first ticket, about a bug during parsing of an uploaded excel file. Our issue was that if the file contained an empty line, all remaining rows were ignored. So the task included extending our tests to cover this case. After 2 weeks (!), his merge request comes in. His idea (without ever asking for help) was to parse the whole file (in some cases huge) in the production code a second time, just to count the rows (!!) and save the count in a public static int field, which was verified in his new test.2
-
So, I’m currently a software tester (please don’t hate me) who is looking to move into development. I’ve been teaching myself programming and have been applying for junior dev jobs.
But it’s been tough, places I’ve been applying for want candidates who have had at least 1 year experience developing in a previous role.
I’ve had an interview for a junior role, but they wanted someone with more experience (and it was my first technical interview so I may have made a few mistakes)
I don’t want to be testing software manually forever (seriously, the manual regression test pack where I work is 1000+ test cases), I find programming more interesting and fun.
What can I do devRant?
Onwards and upwards with the applications. 👍4 -
Just got tested on Angular 4 stuff for a remote dev positions.
I fucking hate lazy recruiters that test you on old sh*t.2 -
Gotta love it when your untouched code worked just hours ago locally and now you have no idea why everything breaks, what has gone wrong and how to fix it ... but it's stable remotely on dev/test/live. Project runs on localhost + vpn on company servers. I can dynamically change the parts that shall be compiled locally and the rest will be loaded from the company servers.
Fucking great.6 -
Whenever the test is to see what clarifying questions they'll ask.
Give a dev in an interview setting a vague task that needs refining before it can be meaningfully attempted, and 95% of them will just plough in and start designing / writing code.
FWIW, I don't personally like these sorts of questions in interviews, as the situation is very different to reality (and therefore I don't believe it's a true reflection of what questions a user may ask in a work environment.) They are *very* common however, and a lot of devs don't seem to be aware. -
Worst:
Working on a C# project that took ages (to the point it burnt me out) not long after dealing with a relatively simple static site project that ended up incomplete because one of the team members couldn't be arsed in providing the info needed.
Best:
Working on a project where I get to put my UI/UX, software architecture and fullstack dev skills to the test on a problem I have may benefit others, as I started a new job that pays well. -
This more how I got back into dev.
I made a mistake and got out of dev for a year or so. What hooked me back in was hearing our C# lead missing that no applicants were passing his C# screening test. I'd never written a line of C# in my life but I had done C++ and Java, so I gave it a go, and apart from one small issue, he said my attempt was the best he'd seen in that recruitment drive. So I started picking up tickets and the rest is history.
The one small issue was doing `if (something == false)` instead of `if (!something)`. Where I work now the C# style guide actually recommends the former! -
Upgrading my tech skills.. Once again I feel my personal my personal dev environment and told are much more up-to-date than what I use at work.... Though the book Kim reading is on TDD and was written 3 years ago.
Maybe I should read another on in cloud services and ML... but don't have any motivation for these topics.
I need TDD for work because now we're emphasizing unit test coverage...
I usually only use manual functional tests to verify the final outputs as either the testing framework is broken (JS) or I don't have time to relearn the frameworks for the particular language...
Anyway got off topic... So questions after:
1. Do you ever feel your technologically always more ahead than what you do at work and essentially you bring skills to the job but you don't learn much out of it?
2. How do you test? I actually got into a bit of a argument/discussion with my colleagues about how to implement unit tests. Apparently there are 2 ways to test? Black box vs WhiteBox. She said she tests only Public methods using mock inputs, dependencies. She read online and seems there is an opinion that should only test public functions and if you can't then your app is designed incorrectly, not separated enough.
For me I test the private functions individually (WhiteBox/Java reflection) because the public one is like generateReport and as a whole is like a Pachinko machine, too many unique paths that would need a test case for.
So thoughts? Yes sorry for turning it into a remake I guess...24 -
What are opinions out there on security theatre?
Should developers have access to aws secrets?
Should dev test and prod be on separate vpcs or all in one vpc.
I have worked at banks where this was strictly not allowed.
Can’t wait to hear responses on this one….11 -
Calling QA/ Test managers for help !
Im a junior dev at a company where im slowly transitioning into also being our test lead. I just got my ISTQB foundation and im starting to write out the test strategy for our company.
Currently we’r doing alot of reactice testing, and to implement more proactive testing i wanted to implement a risk strategy as well.
Problem is that i feel this strategy takes too much time for our organization (doing risk analysis for each story we’r implementing just isnt possivle) , and we don’t have time for me actinh as a full time Test manager while also doing software dev tasks.
Question is: what good proactive strategies can we implement that doesnt require too much time investment - or could we use risk strategy only for specific stories implemented / custom orders / etc and stick with a reactive strategy solely ?
Later this yesr ill be sent on ISTQB test manager course to better qualify my position but until then id really want to get a test strategy somewhat implemented
Any help is MUCH appriciated!10 -
I've got a dev server where I run some test sites in WP using EasyEngine, because I want to get accustomed to WP in Docker.
It asked me to update, and I was like "sure". Now whenever I want to setup a website I get "easyengine couldn't create username"
I figured ok I'll use WordOps, which requires migrating from EasyEngine to it. I was like sure, and next thing I know the "migrated" websites that it was supposed to properly migrate automatically are down, and I can't get an SSL issues for my new site.
All threads on both issues don't help.
It was supposed to be a 5 minute job and it turned into 3 hours trying to troubleshoot. Now I'll spin up a DigitalOcean server and install a quick WP site.
Fuck both EasyEngine and WordOps <3
I thought EasyEngine would be cool but seeing the very limited community activity it's not worth the risk even having it in a dev environment. -
Got jQuery machine test 3 hours later.test includes plugin development and menu generation from json. I am an angular dev. Should I go through anything else other than official docs and ancient youtube videos?1