The real way struct fields should be organized. So satisfying 😍

My First name, is also my Last name.

So it gets kinda akward whenever i fill out a form and when the lady at the booth notices i have the same names on both the First and Last name fields.

She points and explains to me which is which and everybody looks at me like im some 6 year old hahaha.

Oh the F12 reveals so much cringe

When you see a web service API accepting a SQL query in one of its JSON fields and the evil starts growing within you..

DROP ALL DATABASES

Just because you can!

Client: Please remove the address inputs from the inquiry form. Our marketing strategist said that more people will fill out the form if there are less input fields.

Me: But you are required by law to include the address in the generated inquiry PDFs!

Client: Can you remove the fields and still include the address in the PDF somehow?

Me: No. How would the website know the users address without asking for it.

Client: Okay. Wait! Can we change the form to just one large input where the user has to enter everything at once? That is even less inputs so more users would do it, right?

Me:...

When I turn off my laptop and the mouse starts blinking because it is trying to connect to the host I imagine a young boy in the fields shouting "Papa? Daddy where are you? [Crying] Papaaa"

Certified enganeers!
Spaghetti masters!!
Those who dev in prod!!!
Push to master!!!
The "it's a feature" assholes!
The Madman Muntz misers!

The computer science and engineering fields are filled to the brim with fakers, phony's and Python Lords. I try to fight them every time but they outnumber me. Apparently money is more attractive than expressing your own passion.

Stupid annoying client want me to add 2 new fields on a form. Ok I said, my estimation is that I need 2 days to make the changes on form, database and all the scripts that posting and getting data, plus testing. His reply was, come one do you really want 48 hours to just add 2 fields, its sooo easy!!!! WTF dude... if it is sooo easy why are you fucking bother me??? Do it your self!!!!

It would be pretty fucking cool if you listed what information is needed in the fields you fucking cock sucker.

> 3 hour long mandatory online cybersecurity training
> Preaches that the company is very secure and the only risk of being “hacked” is if employees post company data on social media
> oksure.tar.gz
> Bored out of my mine
> Open dev console
> JSON continually getting sent to backend
> Simple structure and human readable fields including {complete: false}
> Open postman
> {complete: true}
> Send
> 200 response
> Refresh page
> Course complete
> :’ )

Muppets.

Bad things should happen to people who put spaces in table names and fields.

Game Development,
Because it merges together so many interesting fields so well. It has a ton of physics, a lot of art and design, psychology, philosophy, storytelling, music ...
And it really gives you the possibility to make anything work to your rules. The only limit there is is the limits of logic and your hardware.

I'm freelancing and there was a guy who needed help with JavaFX. He gave me code only to his view class so I don't steal the rest... It was around 5k lines and it was full of compilation errors because of missing classes. While checking the code I realised something is really wrong with his model classes. So I asked maybe he could send me this one model class that was suspicious. So he did and it was around 10k lines long and had around 200 fields... ALL OF THEM FUCKING STRINGS except 3. You know what the rest of 3 were? 2 Lists of strings and a boolean... It was his "main" model class, he was using it for everything. It had setters for all fields and empty default constructor, so he would just instantiate the object and would set the fields that he wanted to use. Need new functionality? Just add 5more String fields and set them!

Something I probably shouldn't talk about:

One of the projects at work has a specific path you can visit. The """security""" is that nobody should know the path. But I can guaran-fucking-tee you it's not difficult to guess.

On this page, ***without a login***, you can view some user information. Well, you can view all of it, but only certain fields.

And if you perform a specific action on this page, you can get their password, plaintext.

This project is not mine. But learning all of this made me super uneasy. I had to share it.

You motherfucking piece of shit application form...

I was filling a long form in a tab and I had another part of that form open in another tab.

They fucking logged me out of the 2nd tab and didn't notify or prevent me from filling up hundreds of fields in the 1st tab.

Now I have to fill them up again.

Fuck you and your stupid form. Die in hell you fucking stupid cunt.

I created an app that would let people in software development and general I.T related fields to bitch about shit and just rant about stuff.

But two glorious assholes stole it from me. So no startup.

Finding a bug as a developer: "Fuck..." *start working on an undocumented hotfix that breaks other parts of the application"

Finding a bug as a tester: "Yeah, right.." *start writing a comprehensive report including all possible failure scenarios and how world famine will increase and men develop boobs if this bug is shipped into production"

Finding a bug as a PM: "Well, the other parts work, right ?" *click randomly on nearby buttons and input fields to "check" if everything is all right. Ditch said report from tester*

So I just created this Registration GUI (part of a bigger app) for my uni project and was demonstrating how good the app was to all my friends.

Suddenly someone came and said let me verify this. I said go on with a doubtful mind. Obviously I had some verification for all the fields in the GUI but I was closely watching him.

He signed up with this email: " @ . "

😞

Hey Root, we have a high priority ticket for you! It's adding some columns to a report. Should be simple. Details are in the ticket.

First: reports are some of the most boring, drool-inducing drudgery i have ever worked on.

Second: Specs for these reports are a nightmare since everything is ... very indirectly tested, and the specs are everywhere but where you'd expect them to be, so it's a lot of spelunking and trial/error. It's also slow as beans.

Anyway. The ticket's details are in ... not the worst engrish i've ever seen, but it's bad enough that i have no idea what they're asking despite (thus far) five attempts at deciphering it. There's also a numbered list of "fields" to add, so you'd think it would be straightforward. It is not. Half the list is crossed out, and half of the remaining items are feature requests (in yet more engrish), not columns to add. Also, one of the actual fields is impossible as the data it's asking for is not recorded anywhere.

yeah...

I cringe every time I see this person's name as the reporter because it's always the same. and honestly, there are more of these engrish people every month, and believe me: it isn't just a language barrier...

Me: here's the code.

Sr: allright, looks fairly ok. Just change all *FIELD* modifiers to protected rather than private.

Me: what? Why???

Sr: bcz that's the code style we've adopted.

Me: srsly? If so.. Where do you use private fields then?

Sr: nowhere. We use either protected or public so we could extend any class we want

JavaScript classes don't need private fields. JavaScript doesn't even need classes.

STOP TRYING TO TURN JAVASCRIPT INTO JAVA.

YOU CANNOT parse CSV by just splitting the string by commas.

YOU CANNOT generate CSV by just outputting the raw values separated by commas.

CSV is not the magical parseless data format. You need to read fields in quotations, and newlines inside of fields shouldn't prematurely end the row.

Do it fucking right holy shit.

Currently, a classmate and I are working on our technical thesis.
It is all about industry 4.0, IIoT, big data and stuff.
This week, we presented our interim results to our supervisor. He is very pleased with our work and made the following suggestion:
He thinks it would be awesome to publish our work on our own GitHub repository and make it open source because he is convinced that this thesis is able to kind of "set a new standard" in some specific fields of using big data analysis in production processes.

I guess I'm kind of proud :)

Just took a new role...

Production database filled with tables like the following :/

SELECT TOP (1000) [ID]
,[Field1]
,[Field2]
,[Field3]
,[Field4]
,[Field5]
,[Field6]
,[Field7]
,[Field8]
,[Field9]
,[Field10]
,[Field11]
,[Field12]
,[CapID]
,[Car_Manufacturer]
,[Car_Range]
,[Car_Derivative]
,[Field17]
,[Field18]
,[Field19]
,[Car_Model]
,[Field21]
,[Field22]
,[Field23]
FROM [****].[dbo].[****]

This isn't even the worst, there's a table with 250+ fields that should be broken out into 10-15 tables. The code is far, far worse.

Don't think I'll be here too long.

We had a sprint where we removed some fields from the signup page, in order not to "scare users off" with the amount of information requested. Quite a few changes in frontend and backend alike.

Only now in the final day of the sprint (where we're supposed to deploy the changes) do we realize some of that information is actually required by the payment processor, and likely for very predictable *legal* reasons which I even questioned during planning.

When I see two fields, one for username and one for password, I expect I can fill them out immediately subsequently with only a tab in between. While typing my password I DON'T want to get sent to a page where I can enter my password only: I was entering it already! Sometimes I even make it until I pressed the enter key that was supposed to log me in, but then I'm kindly requested to reenter my password. At that moment I not-so-kindly think: FUCK YOU Microsoft, you should know better. Even when logging into Visual Studio for fack sake

Started work on redeveloping a module for our system, I look at the database document and see two fields, one for date and one for time. Both are full date time and the data is stored like so:
Date I want to store: 2016-04-09 05:54:00
Date: 2016-04-09 00:00:00
Time: 1899-01-01 05:54:00

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.

Our team is developing a online e-commerce application. Since the owner uses Last Pass and doesn't like the extension icon in input fields, he asks the developer team to install the extension and ensure Last Pass was disabled for all input fields, password and usernames included, across the site. It was unacceptable to ask him to disable it though the extension menu.

Fucking hell with the password fields.
Why in the fucking hell you can't tell me what's the max characters count? Why I have to deal with auto-truncated passwords after the fact?
Go eat exquisite shit, peasant punks, pussy cutters.

Once upon a time, in a proprietary e-commerce framework used by few hundred sites...

I just took over a project where the previous developer stored password in two separate fields.

password & password_visible

First was encrypted and used for authentication. Second was plaintext password and was shown in the admin panel.

Hope to meet this god someday, I'd sure ask why the hell did he use encrypted password for authentication anyway. 😂

This rings true even if the customer is internal. Built a feature and provided documentation on how to use it and one of the end users still used it wrong.

It was a simple validation process too. Input the member ID then click validate, the app then checks if the person is in the system and fills in some other fields and does some other backend stuff. How could you get that wrong?! 🤔

FUCK ME!!

For a job, I have to create a form with more than 20 fields!! FUCK!!

The most shitty part is that I need to gather all the shit users fill in (if they even fill it in) and place in a shitty e-mail and send that to the client!! FUCK!!

Visions of a better life and fields of endless flowers

Today in the office, a co-worker and me had a synchronised rant. Both sitting at each our desks, and independently of each other, he suddenly cursed "I hate text fields" while I burst out "network, piece of shit!"

Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.

Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!

PayPal always making me laugh. A photo I tweeted some years ago...
Translation:
Placeholder: (Optional)
Validation: This field is mandatory

Client: "We're not ready to be finished with the project but I don't want to pay you any more money to meet the terms of the contract we both signed, even though all my must-have changes led to more costs just like you had warned me they would."

Me: "Don't make any more changes, plez."

Client: "Imma make another change."

Me: "No. Stahp. Don't."

Client: "I added four new fields and probably a ton more business rules I don't care to understand."

Me: "Kill me. Just put this gun to my head and kill me."

Client: "That's not in our contract!"

Can you guess where the form fields are?

It's the grey area.

Not, not that one, the other grey area.

Don't you just love it when you ask Hibernate to fetch some data from DB and it does that for you.?And also updates a few more tables on its way. And inserts a few more rows. And updates another couple of fields..

Isn't that just amazing? I mean.. What could be more satisfying than getting an "ORA-00001: unique constraint (some.constraint) violated" while issuing a FUCKING **GET** METHOD?

ARGH. The moment you realise the previous developer centralised ALL of the current software around a M$ access dBase. WTF. Same dude also stores day of year, week of year, month number and year as seperate fields in a MySQL dBase. Alongside a datetime stamp. OMFG!!!!

Memory just came up from reading another rant about static keyword I wanted to share. Involved a network programming assignment in Java back in my heyday.

Fellow student was told that a static member was shared between every object in a class and decided that they could use that to implement network communication (i.e. if they ran the same java program on different machines, they'd be able to communicate by reading to and writing from the same static fields).

Have a memory of sitting in corner of lab overhearing tutor lose their mind trying to (unsuccessfully) explain why this didn't work.

One of my classmates was working on a login form, and the fucker handtyped a 100+ character email validation regex but forgot to add a check to make sure no fields were blank.

It was funny when I was able to create an account with no username, breaking his website, and even funnier when I told him html forms have a built-in email pattern

So, part of my job is working with SQL. Not my favorite technology to work with. But the tables have mostly non-descript fields, multiple schemas in the same table, and encoded relationships spanning multiple tables. Yes, the database from hell! On top of that, there is very little documentation on this mess. -- And my boss wants me to write queries against a combination of these tables to make sure the program is working. RIGHT...

dev "no no no, you're overengineering it. You just need one class for that"
Me "but ... Those are different object that share a common interface. The internal logic is not the same, only their output is. You know ... That's the purpose of interfaces"
Him "no no, as i said, you don't need that. Listen, you can put ALL the fields and methods in a single class and then you can use a switch with different cases .."

Something I've noticed over my many jobs. "Professional" means entirely different things at different jobs, and doesn't follow fields either. That is, "Professional" in one field is understandably different from another, but businesses inside the same field also have different definitions of it.

It's almost as if "Professional" is just a euphemism for saying "we expect you to act a certain way, but are being passive aggressive about it so we can't be called out for it".

Working with a developer from another company, nominally called Jo. I had a programming session with Jo today.

Sometimes it's hard to succinctly describe an individual developers level of aptitude in highly technical fields to outsiders because it often requires a lot of context relating to the problem being solved and their attempts to solve it.

In this case I think it could be pretty accurately summarised in this little anecdote: there was a 10 second pause in our work today while Jo was trying to figure out how to type '<'

Witch hunting:

I just spent the last 90 trying to fix a visual bug with the UI

I made a functional component to render pretty forms with minimal information in React
Turns out some random ass fields were not rendering with their respective lower borders

Refactored the shit out of the components
Actually got them to follow a strict styling

Two cups of coffee later it clicked: everything was perfectly functional, I just have a shitty small monitor and tried zooming in
WOULD YOU LOOK AT THAT, IT'S THE FUCKING BORDER I WAS LOOKING FOR ALL ALONG!

Don't be like me: check les differents view ports

The worst was an open source project I tried to look at.

It was written in Turbo Pascal.

I am not sure, never really got so far, but it looked like it was one single class with hundreds of methods and hundreds of instance fields for data.

Almost no data objects, if it needed for example 4 sets of 6 variables it had 24 instance fields and in some instances 4 different sets of methods for accessing said variables.

Around there I stopped looking ;)

A team at school spent 3-4months on an eStore web app, for selling items. The title was "Securing your eStore".

When they were done with their presentation, the examinator asked: "But... You haven't said a thing about the security part."

"Oh, sure we did, as we showed you, we added validation on the email address and credit card text fields etc. If you press the Pay button here, you will get an alert()-dialog telling you which fields are invalid..."

Fucking hate my job 😡
I joined as nodejs dev at a mnc 3months ago involved in banking software in which i dont have any domain knowledge.. first 10 days I was told to go through fucking udemy nodejs and graphql tutorial (wtf) which i already have experience with before joining.. after that my reporting manager gives me task to resolve fields and gave me shitty jira story link to read.. that shit story link had no explanation about the fields and what the database it is, then she says to use some shitty sdk which is built internally by shiity devloper which had no documentation and have to follow other module which was again written by that sr. Dev... They hav fucked up the graphql and nodejs and entire stack and also till date no one has ever given any explanation about the domain and the fields and database schema.. this manager refuses to share knowledge about the domain now how the fuck i resolve the graphql schema which was again written by non technical b.a.. all they have used is latest technology in a shitty way with no standards to to follow .. no dataloading no caching no batching.. use shitty sdk which does not give access to dbconn and fucking tightly coupling expressjs which when i start consumes crazy 400Mb of memory .. these fucking seniors devs + the fucking b.a having 12+. Yrs exp each have fucked the entire codebase... Each day killing my passion for app development.. fuckkk ... Dunno what to do now

Galois Fields 😍

wrote some JS to make sure that eForm fields which are hidden/disabled via checkboxes are nullified before the form submission. Checking the request and the fields are definitely empty. But the tester says the data is still appearing in the DB. So i am moving immediately to Nepal where i intend to live as a goat.

!rant
Question time for you very few Salesforce devs out there, yea I know there’s some.

Seeing as Google is not my friend today, I’m trying to get SOQL to return null valued fields back to a rest api, something this hunk of shit won’t do, and short of looping back through all the records and injecting these fields back in, I’m at a loss... any advise is welcome 🤯

So I wanted to spread a struct in another struct to fill fields with the value `None`. Not what I expected when I googled "Rust spread into"..

Fun issue

Swedish client is unable to enter a currency conversion rate in a field and submit. 'Not a float' well we can clearly see that it is a float when he does it (0.5 for example), not an issue for us though.

Reproducing was a nightmare, eventually it boiled down to the fact that the framework we were using had automatic locale checks. Now because our numeric fields are actually weird text fields (front end nonsense), it was converting the period to be a comma (Swedish people would write 0,5 normally). And if you actually entered 0,5 the range check (0.01-1000) failed because it couldn't parse the comma (no locale check on that one)

Godamn facepalm. Really confused the hell out of us when we saw the error, had to go diving through library code. To top this off, locale checks are supposed to be disabled as of about 2 years ago

In revenge against our oppressor :PHP: on slack is now an alias for the shit emoji

Client: I just want a very basic modification, something a skilled developer could do in a couple hours.

Me: sounds great, can I look at your requirements?

*sees user-defined fields, workflows, navigation, roles, styling, customization everywhere*

D:

When I started programming ~5 years ago.

Teacher: OK, C++ classes and structs have 3 access modifiers: private, public and protected.
Private fields can't be accessed out of the current class.
Me thinking: wow, that's cool, but how can it be? I have to research.

I went to home and wrote a class with one variable with its set and get functionality.
Then I opened Cheat engine) and tried to access and change the variable. When I succeeded, I started hating this world of programming.

After some time I understood that it's wonderful cause it's up to you.

In a way, it's a bit unfair on those in other fields that we get paid so well for doing something we love.

Longest I've worked without rest + why?

Over 24 hours. Why?

In our old system, the database had fields, for example, a customer like Total97, Total98, etc. to store values by year (or some date-specific value).

Every January 1, we had to add fields to accommodate the upcoming year and make the appropriate code changes to handle the new fields.

One year the UPS shipping rates changed and users didn't want to 'lose' the old rates, so they wanted new fields added (Rate98, Rate99, etc) so they could compare old vs. new. That required a complete re-write of most of the underlying applications because users wanted to see the difference on any/all applications that displayed a shipping rate. I'll throw in asking 'why?' was often answered with "because we pay you to do what we say". Luckily, we had already gotten to work on a lot of this before January 1st, so we were, for the most part, ready.

January 1st rolls around (we had to be in the office at 3:00AM), work thru changes, spend some time testing, and be done before noon. That didn't happen. The accounting system was a system that wasn't in (and had never been) in scope, and when we flipped the switch, one of the accountants comes into the office:
E: "Guys? None of our Excel spreadsheets are working. They are critical to integration with the accounting software"
Us: "What? Why would you be using Excel to integrate with the software instead of their portal?"
E: "We could never figure it out, so we had a consultant write VBA scripts to do the work."
Us: "OK, a lot of fields changed, but shouldn't be a big deal. How many spreadsheets are we talking about?"
E: "Hundreds. We have a separate spreadsheet for every integration point. The consulting company said it scalable, whatever that means."
Us: "What?! Why we just know hearing about this!?"
E: "Don't worry, the consultant said making changes would be easy, let me show you, just open the spreadsheet..click here..<click><click><click>...ignore that error, it always happens...click that <click><click><click>.."
Us: "Oh good lord, this is going to take hours"
E: "Ha! Probably. All this computer stuff is your job and I've got a family to get to. Later"
Us: "Hey 'VP of IS', can we go home and fix these spreadsheets as-needed this week?"
VP-IS: "Let me check with 'VP-FS'"
<few minutes later>
VP-IS: "No, he said Excel is critical to running their department. We stay until Excel is fixed."
Us: "No, no...its these spreadsheets. I doubt FS needs all of them tomorrow morning."
VP-IS: "That's what I said. Spreadsheets, Excel, same thing. I'll order the pizza. Who likes pepperoni!?"

At least he didn't cheap out on the pizza (only 4 of us and he ordered 6 large, extra pepperoni from one of the best pizza places in town)

One problem after another and we didn't get done until almost 6:00AM. Then...

VP-IS: "Great job guys. I've scheduled a meeting at 8:00AM to review what we did so we can document the process for next year. You've got a couple of hours. Feel free to get some breakfast and come back, or eat the left over pizza in the breakroom fridge. There is a lot left"
Us: "Um...sorry...we're going home."
VP-IS: "WHAT!!...OK...fine. I'll schedule the meeting for 12"
Us: "No...we're going home. We'll see you tomorrow."

As a web designer/developer I hate this recent trend of very light gray text fields on forms that have a white background. I don't want to have to peer at my screen for objects. My vision is average, so why would a client want this?

That moment when code reuse makes you reuse reused code and you actually reuse a BUG.

You decide to go for code reusing when your boss asks: "Can you add an edit popup besides that 'add customer' popup button?". You do some little tweaks to the "new customer" code and it allows that to save over an existing entry, cool.

However, after a lot of time spent on reviewing the resulting PR, turns out there was a dormant bug on the code you reused, and it woke up with its new use.

That code was a bad copy-pasta from another, bigger form, which included a whole bunch of optional fields. As it was only used to save new entries, those now missing fields were simply being saved as empty. But as you reused that to save existing entries, you were now cleaning up all those optional fields without noticing.

To the front end dev that 'finished' his part of a web form with a Hundred pluss fields. You left every id, name, and label-for as 'first-name'.

I know it saves you time to copy paste and only change what's visible on the page, but FUUUUUUCK YOU!

Client is setting up Google Suite, needs me to create a TXT record. She sends me a screenshot of the record that needs to be created, so I ask her to copy/paste the record values .... she copy and pastes the URL and sends that to me. I ask again for her to copy the values in the fields on the page and send them to me ... she sends me another screenshot. How do these people get through a day?

One of our clients IT team is lazy as fuck they slack too much, it took them 2 weeks just to respond our email (We already sent like 2-3 reminders in between).

Client:"We fucking pay you and it's still not ready, how much time it will take?"
Us: Just respond to that email ffs so we can proceed.
Client: Oh, there was an Email? we will have a look into that.

Even after, it took them 4days to send fields which were meant to be sent like 2weeks before.
(in between 4days we had called them just for the fields again and even after the fucking call they send that fucking fields after one reminder)

And of course, still, the blame game is on us.

If you're using the adwaita-dark gtk theme, you may have noticed that the text entry fields on lots and lots of sites make your text almost impossible to read, using firefox. You can fix that by creating/editing the, "widget.content.gtk-theme-override" key(in about:config), setting it to "Adwaita" and restarting firefox.

C might be a pain to write, but holy cow does it run circles around python from a performance perspective. Easy to forget in fields like data science, where python is the default

It's one of the rare fields where you get to be both creative and functional. Whatever you want to happen on the screen you can make it happen. You can really put yourself into whatever you are making. Maybe you can't do that and make a ton of money at work. Maybe you can't do that and release a product everyone will love. But you can do it. You can put power in people's hands. You can embed parts of yourself, your philosophy, your thoughts, your wishes, etc. into software and spread it all over the world very quickly. I like that about it

Fuck Captcha. Seriously. Am I blind to that shit or are you supposed to fail entering that goddamn letter soup like 5 times before getting it right? Of course you have to re-enter your form fields every time you fail because you don't deserve better, you illiterate fuck.

Maybe not exactly what would happen, but not wrong either. At the end of the day, these two fields are different.

Google, will you ever manage to fix YouTube so it actually doesn't fucking break every day?
This "feature" where the page doesn't reload when I click reload is neat until I want to, you know, reload to see new content. Or reload because you failed to load a single video thumbnail. But no, you managed to combine the shit of both worlds and give me a loading progress bar and then don't change anything.

Also YouTube is the prime example why you don't try to reinvent text input fields. I can't remember a single instance in the last 5 years where the comment fields didn't have at least one weird bug.

Why do tech companies build the shittiest websites?

Pulled into an 'emergency' meeting with a group of web designers deeply concerned a particular service wasn't going to meet all their requirements.
DevA: "For each page, Its going to be A LOT of work to retrieve all the data and store it's state. Every page load will require a round trip to the service."
DevB: "Yes, we aren't sure how the service should be changed to do what we need."
Mgr: "What is it not doing now? Doesn't the service already returns all the necessary data?"
DevA: "Well...um...its all the boolean fields. Some may be defaulted from the database or false because the user unchecked the box. We have to know which is which"
Me: "Why? Are you doing anything different in the UI? Checkbox will be true or false. What or who set that value is irrelevant"
DevC: "Well, it matters if the user didn't fill out all other other values."
Me: "How so?"
DevA: "Its matters because the values in the other fields. Its going to be A TON of work to figure out."
<mgr goes to the white board>
Mgr: "Lets map this out...what fields are you needing to trigger the state on?"
DevA: "Um...uh...the 'Approved' field...and um...'OK to Contact' field"
Mgr: "Just those two?"
DevA: "Yea..um...there are other fields, but whether or not to show the edit box depends on those two."
Me: "The service already returns data, you only have two fields to check? I don't see a need to change the service at all."
DevA: "Returning all that data, we are going have a serious scaling problem. We'll be hitting the service A LOT. All that javascript could cause performance problems too"
Me: "How much data are we talking about? Name, address, couple of booleans?"
DevA: "I have to serialize the data. All that logic is going to be reeeaaallly complicated. It might be better if the service returned only the data I need."
Me: "$64,000 question, how often is this feature going to be used on the web site? Maybe once? Few hundred a week?"
Mgr: "We have no idea. A lot of the data will be pre-populated and we're only sending out a few thousand invitations. More around the holidays...but honestly, not very many."
Me: "Changing that service only for this particular area of the web site isn't going to happen. Changing the UI is the only course of action."
DevA: "Oh frack I can't wait until this project is over."

DevA...how the funck do still have a job here? You wasted about half-hour of my time with your cry-baby crap. Where is my hammer...no...no..don't go there...ahhh...thanks devrant. Prison sentence diverted.

PM - "can you add this word to the application? You have 4 weeks"

PM - "can you strip the database, refill it with new fields and implement it so that it works across a wide range of companies? You have 1 hour"

my vision about life changed as I started learning about algorithms and programming, which I consider as an advantage, tho I can't help but wonder if people in different fields feel the same.
it also feels like I over-think since then, a constant need to analyze things which is overwhelming sometimes.

We just got a new web dev with 10+ years experience with the goal of helping out our rather inexperienced small team.

His first PR was for a rather large form with 30+ fields.

He. used. a. <table/>......To layout the entire thing! With inline floats no less!

How the f do you spend the last 10 years not bothering to pickup any modern css?

I FUCKING love it when I try to understand how to simply fucking connect to my server via SSH, and seeing tutorials from cocksuckers that just screen some form fields without telling where I can find them, and juping from steps to steps like I'm in your fucking head

CAN'T YOU WRITE SOMETHING THAT WOULD MAKE SENSE, YOU FUCKING MORON???

Working on a legacy app and couldn't find in the DB, fields for description, status, title, and assigned user.

I found them.

They were in the fields: User1, User2, User3, and User4.

How the hell does that happen?

I'm a C++ dev, but last month I was working in the vegetable fields to help my young brother and his business. And right now I'm going to sleep outdoor after my birthday party looking at the stars.
Free spirit is a good point dealing with free languages like C++ you know :D
Sweet dreams btw :p

I wish I could declare variables IRL so I wouldn't have to repeat myself 6 times in a row before being acknowledged. Yes, the client left these fields empty, that's why the form returned an error as it should have. No, it's not the code's fault. For once.

When a client asks you to make a form.... With 6 input fields and about 9 output fields.

Cheers buddy, I'll just make the rest up shall I?!?

FFS!

Why do some developers cut corners and add 20 extra fields just in case the customer wants to add extra data? What happens when the customer needs 21 fields. Just spend slightly more time and implement a custom field system that can extend to any amount of data it's not that difficult and you won't have to add a new field every time a customer needs more then you expected.

-Applying for internship
-the "previous work/employee records" field is their
-can't leave it blank
-so did this "------" for its various fields of work position, start date of job, and date of job, salary, etc.
-warning says "can't leave that field empty"
HOW THE FUCK ONE APPLIES TO AN INTERNSHIP WITH WORK EXPERIENCE WHEN THERE IS NONE ?

If Skype 4 Business could stop changing the control names for their input fields, randomly, that'd be great.

Of course, the variable for fields should be called "flds", those 2 bytes saved will help us so much! For a small price of this shit being not really readable anymore. Is it "floods"? "fleeds"?

Reporting is not fun..

Scenario 1:
* A user says they need to export certain data from our system..
* Developer W makes report called "Foo detail report"

Scenario 2:
* A user says they need this report to also show some extra fields
* Developer X makes a new report called "Foo detail report (extra fields)"

Scenario 3:
* A user says they need this report to be run with a different search criteria
* Developer Y makes a new report called "Foo detail report (extra fields) by bar"

Scenario 4:
* A user says they need this report show data grouped in a different way
* Developer Z makes a new report called "Foo detail report (extra fields) by bar- new grouping"

The above scenarios happened over and over for several years in no particular order...

Current Day:
* Some users have certain reports they use and rely on but we don't know which ones
* Nobody really knows what all of the reports do or what is the difference between them without looking at the sql
* If we want to change data structures we have many reports to update
* I have a request from a user to add an extra column to one of the reports

Couple years ago I was asked to add couple of simple features to a piece of code on clients server. I thought it was simple process until I got the code and noticed that the variables were named like int1, int2, int3... etc. Also same logic in the database.
Needless to say I spent too much time to figure out what those variables and db fields contained. Also the whole code was copy paste code from the web.

I just created a users table and added everything except two important fields:
1. FirstName
2. LastName
I only found out when I started working on my service T_T

I'm sorry, I have sinned :(

coolest bug our team had was not a actually a bug but a feature that is misused and abused.

tldr: its a feature that became a bug

we have an app that has a "test print" feature to test the printer and the format of the document to be printed. it has the word TEST for fields and all that.
it became a bug when suddenly, the users use that feature to print documents, instead of using the app with the business rules and all, and just manually strike off the TEST words with a pen.
the feature became a bug because it has become a security risk.

Export data from a database that you've not modeled is a problem (sometimes), I just realized that this DB has two tables to storage cities, the main difference is the id, the other fields are the same in both tables, I hate that kind of people....

Today I deleted a lot of stuff
Fields, methods, classes, files, even database tables

And for a change, it was all on purpose 😁

Feels good to refactor stuff and clear out the cruft!

TLDR; I was editing the wrong file, let's go to bed.

We have this huge system that receives data from an API endpoint, does a whole bunch of stuff, going through three other servers, and then via some calculation based on the data received from the UI, and data received from the endpoint, it finally sends the calculated fields to the UI via websocket.

Poor me sitting for over 4 hours debugging and changing values in the logic file trying to understand why one of the fields ends up being null.

Of course every change needs a reboot to all the 4 servers involved, and a hard refresh of the UI.

I even tried to search for the word null in that file, but to no avail.

After scattering hundreds of console logs, and pulling my hair out, I found out that I am editing the wrong file.

I guess it's time for some sleep.

Meetings would be better without people.

I mean I like the IDEA of meetings...

Honestly I'm the type of person who if I could would schedule lots of meetings to make sure we're all on the same page, and to be sure the thing is going to do the thing everyone wants / get their perspective, etc. I really want to KNOW what the folks who are going to use this thing need / want / what works best for them.

On the other hand I know that meetings are often more like:

Me: "Ok let's so here's our data, now tell me what fields they want to edit and so forth."

People: "All of them."

Me: "Uh, no you don't want that or they'll break everything ... X, Y and Z require those fields for A, B, and C to work."

Me: "Let's go field by field and you tell me if they need to edit it, and why."

People: "Yeah this first one they have to be able to change this one."

Me: "Wait no, that's the primary key for that table, I don't know why that's on this list but no you can't change that."

People: "Yeah we have to be able to change that."

Me: "No, you can't, do you even know what that number IS?"

People: "Um... no ..."

(╯°□°)╯︵ ┻━┻

How the actual fuck? Today I found another page where I can't sign up because the fields do not recognize when I typed in them in firefox.
One of those sites is to change passw of university account.
Guess what browser they recommend...

Can we all just agree to stop actively imagining progressively harder to parse CSV formatting options? For fucks sake I’ve had to build in tolerance for quoted and unquoted data, combined data and split data, ways to split the data and recombine it, compare every data point, filter some data, only add data, only remove data, base data updates on non Boolean fields in the file, set end point matching based on arbitrary fields, column number matching, header matching, manipulate malformed urls and reassemble the file with proper ones, it goes the fuck on. CSV’s should just be simple and not hard to format. Why does everyone want to try so fucking hard to do bizarro shit?!

I worked with this hack of a backend dev that was too lazy to add a complex(ish) object to our CMS tool. His solution?

One giant-ass text box with the label "put JSON here".

If tech people were using it I wouldn't mind, but our poor content managers have no idea what json is. Plus like... no examples, no schema... they would have to change shit then go look at the website to see if it worked. Fucking asshole.

Plus.. I mean SHIT, MAN! This was in a Node.js tool... if you have the Json parser you could just GENERATE the respective form fields. DO YOUR JOB

Our company hired a "Human resource consulting" to help with our internal processes and policies. Yesterday they showed us an Excel that we should fill when we travel to attend meetings, events, courses, etc.

This spreadsheet... OH, THIS SPREADSHEET... you should've seen that.

Most of the "labels" of the "fields" were writen with terms that we do not use in our daily basis. The fields were ambiguous. You shout put a number on the Transportation quantity (ex.: 5) but have no space to describe which transport you will use (bus, metro, uber... so... 5 what?). When we asked which name shoud go on the field "superior" (director, pm, scrum master...) the woman from this consulting said "oh, I don't believe you're asking about this" (and since then, she became more rude by the end of the meeting).

We care for quality in our apps, and UI/UX is a big thing in our company. The last thing we want is need to read a f*#1n manual to fill a spreadsheet. Make it intuitive and you will not need an hour and a half to explain how to fill this obsolete form.

It's sad to think that this person was hired to improve our company, but did not bother to understand the company's culture (and values, and terms) first.

Remember, the more "cutting edge" and "thousands of clients" a company has is inversely related to the quality of documentation they have on their APIs and software solutions.

I don't give a fuck about your pretty examples, show me which FIELDS can take which VALUES. It's that simple. Instead, I'm wasting your company's and my own time by spamming support for what should be basic questions clearly outlined in the documentation.

One of my collegues:(C#)

A(him): i need to do a helper to transform 2 fields from a class that are DateTimeOffset to another offset. I want to create a new class that do that and to instantiate where i need it.
B(me): use extensions, they are nicer and they fit better in this case. Also if you want to use a helper just make a static function.
A: it's too complicated
B: Why?
A: Nevermind..

FUCK OFF!

So you may have noticed that I'm making a way to create devRant Webhooks (see last rant), but now I need you help:

What Webhooks would/could you need?
What does it do?
What additional fields does it need (for example for specific tags)?
What data does it send?

Thanks in advance!

I study Computer Science. At school we have a little project group that help others students in different fields with their computer problems.

A guy came and he says that he tried to removed the jack from the audio jack - he broke it for whatever reason - with a stick with hot glue on it's tip saying he saw this on Youtube. The glue got stuck in the jack... We had to buy a new headphone jack card for his laptop.

When you hit the rock bottom, remember that at the very least you're better than those who use * in SQL selects bc they're too lazy to specify the fields they need.

First time developing an Android app using Android Studio. I wanted to see how it is to make a mobile app. It's very simple, doesn't wow with design and calculates price discounts. First time using Java too, which was cool. Biggest annoyance? Making fields and buttons "responsive" to different screen sizes!

Currently working on a Selenium script to do my timesheet for me. It's been 30 minutes and it still doesn't work because I'm having trouble selecting the input fields correctly (the ID's are dynamic and keep changing!)

It takes me 30 seconds to do it manually.

I wasn't hired to do a dev's job (handled sales) but they asked me to help the non-HQ end with sorting transaction records (a country's worth) for an audit.

Asked HQ if they could send the data they took so I wouldn't need to request the data. We get told sure, you can have it. Waits for a month. Nothing. Apparently, they've forgotten.

Asks for data again. They churn it out in 24 hours. Badly Parsed. Apparently they just put a mask of a UI and stored all fields as one entire string (with no separators). The horror!

Ended up wasting most of a week simply fixing the parsing by brute force since we had no time.

Good news(?): We ended up training the front desk people to ending their fields with semi-colons to force backend into a possibly parsed state.

Father of my IT director. He was good with VB6. Now he is abusing MS Dynamics by using it to just host custom html forms and his DB main working table (which just mimics the fields of the CRM entity he has created is edging on 300 fields. He reuses same entity for 10 different non related "applications" (custom html forms... just CRUD) so majority of rows in that table use up to 30 fields...

Bunyan

Bunyan is a simple and fast JSON logging library for node.js services

Server logs should be structured. JSON's a good format. Let's do that. A log record is one line of JSON.stringify'd output. Let's also specify some common names for the requisite and common fields for a log record.

What is it with the rising trend of password fields allowing you to see your password, and (worse than that) often having it as unmasked by default?!

Who woke up one day and said "Damn, you know what would be a great idea? Unmasking the password field, so everyone can see it! Why didn't we think of that before?!"

Dahh.

In all seriousness, the best part of being a dev is that you learn something new every day. That serves me personally as motivation. There are so many fields of study that embody what a dev is, and because of this, there are a LOT of things that you can do and create. On the other hand, the worst part of being a dev is the fact that we can't do it forever.

Have plenty of rants with enough ++ but I haven't requested stickers yet. Because i don't want to put them on something that i will end up throw away anyway. Besides from my gf, there is notting I'm attached to.

In this electronic age i which there was something more useful.
Example :
- email forward for nick@devrant.io
- custom profile fields
- ..

Just don't see the fuss over stickers. Maybe when i was 12 but that's 2 decades ago. But then again. If there were no rewards, it wouldn't really make a difference for me.

You know something is wrong when chocolate-doom, a full game (actually 4) with custom software rendering engine compiles in 12s, while your stupid Webapp with a few input fields and backend calls take over 1m to build 😒😒

marquetting department: i need a new for on the website its urgent drop everithing else
dev: sure can you give me the text and the fields that should be on the form?
....1 week later
dev: do you havr the info
marketing: can you have ot online today
dev: yes just get me that content
1week later
.... you know where im going with this

Saw lots of regret posts about being in dev field. Then why bother living that way?

Not like engineering, medicine or business management fields, I believe programming needs passion similar to art related careers like acting, music and painting etc. So if you don't have any passion for programming, you won't be successful or satisfy at all.

That doesn't mean it is all good and happy days for every passionate programmers. We sure have ****ed up days (probably more than other fields.) Seriously that's why we have devrants. No? But it doesn't reach to the point of regret to me.

Here our national programming language is probably PHP. The pays are lower than your part-time fast food chain workers. The internet speed is in kbs with 2 digits most of the places. Government doesn't give a crap about IT. No IP copyright laws and so on. I probably would earn more and live better if I were not running this IT business.

But hell yeah I never regret at all.

Java rant...

If public field declaration is so so bad, why can't all class fields in java just be private by default? And make it a pain in the ass to expose it as public?

I can't actually remember a time declared a class field as public, it is muscle memory now... Private bla Bla Bla, return, private bla Bla, return...

To create an abstraction simple enough to make complex business logic challenges solvable for non programmers.

The issue I see today is programmers solving problems they don't understand as well as the user. I think two ways might be taken:
- Programmers specialize in other fields and solve problems there
- Other professionals create their own software

Both will happen in the future (IMHO) and I want to help the second happening.

Note: Excel does this really well, but I think we can so quite better today.

Is it me or is Software Development basically just Web Development?

I don't hate web development, in fact, I'm learning to become a web dev myself, but everywhere I look, everyone is a web developer.

When looking for a job all the requirements describe skills that are commonly associated with a web developer role despite the title saying Software Developer, all the developer communities I visit are filled with web developers and web dev topics, any topics pertaining to other fields of software development are close to non-existent, and when I go looking into resources for learning the Web Development courses and paths are much more well-supported than other fields.

At first, I was thinking of becoming an Android dev than maybe later learn some web dev but it looks like it would be a better idea to become a web developer since it would be much easier to ingratiate myself into the communities, find resources, communicate with other developers, find a job and I could even use the web dev skills to make mobile apps or apps outside of the web.

Should I stick with Web Dev or continue learning Android?

I "failed" a SQL question once because I didn't use GROUP BY; I informed the interviewer that it wasn't needed because all the fields in the SELECT were aggregates and based on the WHERE clause I knew exactly what was being aggregated so there was no reason to echo the data value back. I continued that if there was a business or design reason for the echo then yes, the GROUP BY would be required.

I was told to build a logging app for one of the work streams on my project. The lead briefly brainstormed about the data fields they'd need to log and told me to go make it.

I am handing off the app and they ask me what they are supposed to put in each field.

Me: oh [team lead] just told me to put in these fields, but you guys are going to use it so why don't you tell me which fields you need and I can change it easily.

They refuse to tell me how to build the app they're going to use and will definitely complain about it not doing what they want later.

GitLab, why do you don't want to have my money? I just wanted to pay for GitLab Bronze to enable Pull Mirroring. The problem is that I cannot register for billing without having a company. GitLab, I am a single private person. I am not a company! Why do I have to fill out these form fields? So if you don't want to have my money, then you will not get it.

API provider: include a signature based on these fields in this order. DO NOT ENCODE IT!

Implementation works a while, then..

*a wild apostrophe appears*

Signature no longer works.

API Provider: "oh, yeah we escape those."

Arrghhghghghhhghvhxmchsoxnsoxnwl

Not only is it a poor design for signing payloads, the documentation is shockingly poor in it.
Even the implementation example (which is supposedly from their code) doesn't account for any type of escaping or encoding.

Before anyone asks, I can't into details about the implementation.

Dev-tip of the day:

Always make sure that your database table fields are long enough to hold the entire third-party API client reference ID, so that the last three characters won’t be cut off..

I’ve been “crying” here while debugging for the last hour because my API function and everything else worked, but the result wasn’t showing up in the third-party application (their API returned a 200), but when I tested it with their API sandbox application, it did show up..

Googling how to electromagnetically shield a espruino project from neodymium magnets over lunch, and that leads on a trail of manipulating and directing em fields...

"What are you doing? That doesn't look anything like a binary tree structure in Java... What the hell is all that?"

"Uhm... Personal research?"

IT teach giving a speech that our MS excel exams are shit and we have no logic and that we suck at math. I mean, yeah it's true that I suck at math and I've never used excel before coz I never had to but ffs I code during nights and I love it, also there are so many fields, saying that you'll be just a part-time waiter... If you have the attitude to solve a problem that you care enough about you'll get there eventually. Sucking at something doesn't mean you suck at everything, everyone has their strengths and weaknesses.

I feel i need to be specialized in something coz everyone can code now... like u have machine learning engineers and devops/cybersecurity but im not really into either. What other sub fields are there?

Having a complete front end and back end application where the frontend is designed to look as simple as possible.

A new potential customer wants to have our app and listens to a designer bragging that its just replacing 2 fields.

After a while our manager comes by and mentioned that everything needs to be done within a few weeks....

All devs lose their mind since in the backend we need to have like 8 external sources to connect and hundreds of business rules to implement.

How a single designer ruined the year for 7 devs....

"Reflective" programming...

In almost every other language:
1. obj.GetType().GetProperties()
or
for k, v in pairs(obj) do something end
or
fieldnames(typeof(obj))
or
Object.entries(obj)

2. Enjoy.

In C++: 💀
1. Use the extern keyword to trick compilers into believing some fake objects of your chosen type actually exist.

2. Use the famous C++ type loophole or structured binding to extract fields from your fake objects.

3. Figure out a way to suppress those annoying compiler warnings that were generated because of your how much of a bad practice your code is.

4. Extract type and field names from strings generated by compiler magic (__PRETTY_FUNCTION__, __FUNCSIG__) or from the extremely new feature std::source_location (people hate you because their Windows XP compilers can't handle your code)

5. Realize your code still does not work for classes that have private or protected fields.

6. Decide it's time to become a language lawyer and make OOPers angry by breaking encapsulation and stealing private fields from their classes using explicit template instantiation

7. Realize your code will never work outside of MSVC, GCC or CLANG and will always be reliant on undefined behaviors.

8. Live forever in doubt and fear that new changes to the compiler magic you abused will one day break your code.

9. SUFFER IN HELL as you start getting 5000 lines worth of template errors after switching to a new compiler.

Question about google crawler (?)

So, got a question, hopefully you have an answer.

I have a personal website that went up about 2 months ago that has a contact form.

Today I got two emails sent to me. This is the way I have coded it up.

But take a look at the name and message fields. I wonder if this is a google crawler submitting the form by any chance. I also got another email around the same time where the message and name field are reversed.

Anyone else experience this?

Demo

Backend Team : No one want to listen to technical details. A short 2 min demo what we have done.
Shareholders : Have you done anything?

Frontend Team : half an hour demo of validators and fields that sum values from other fields
Shareholders: Wow that is awesome, great job, nice to see, great value, lot of progress.

I love learning by doing.

Building MVPs and prototypes is the best way. Even better if you have a chance to show and share them in front of an audience (peer pressure can be good!).

Share the lessons you've learned and what you've done wrong, it will help many more people than just yourself.

I've been working for an eLearning company for the last 4 years (CloudAcademy.com) and I'm in love with the idea of learning something new every day. And not just coding. Code is "only" a tool to solve problems, and learning something about those problems and fields will make you a better developer.

I'm such a fucking idiot

I'm setting up an api and to prevent unwanted fields or circular dependencies from showing up I define what fields should appear in a few serialization yaml files.

These files define what fields should appear in a given context. The default context for every field is to always show the id, and only a call to /posts will give you all the fields of the posts for example. This means that if you retrieve a comment with a linked post, the post will only show up as an id, but the comment will have all its fields.

I've been struggling with a stupid problem for 2 hours, I could verify that the yaml files were loaded in, all entities had such a file and the configuration was exactly according to the docs.

Guess why my api calls still caused circular errors?

Because I forgot to do the $view->setContext$this->defaultContext); call that determines what context should be used for the response.

FUCK ME WHY DID IT TAKE SO FUCKING LONG TO FIGURE THAT OUT OMG

Google you say? Ofcourse I hunted google results! But I was unknowingly part of an XY problem and was looking for what the problem wasn't >:(

At least it works now, ugh

So after multiple hours of wrestling with Jira I finally managed to autofill fields in the service desk. How? By installing a plugin to show message boxes and injecting JavaScript through it, what else?

Fucking wonderful piece of crap :)

Next up: automatically capture errors triggered by employees with Sentry and raise Jira requests. "A button didn't work" isn't enough god damn it.

website: fill in all fields
user: john doe
kill blood, texas, 751454, usa
me: when the website says street name, we meant the name of your faking street!

My code works.
Well, it should, but not like this.
I've set some datas to a nested form,  saved by a variable named 'stat1', however the code won't work unless I use a variable named 'fields'. Not 'stat1'. I'm only 24 years old and I already feel too old for this shit.

Customer asks us to add an exception report to a file upload process, to show which users failed to be added, and why.

File has 4 fields per record: id, first name, last name, and email.

Customer: "some of these records aren't uploading, and when I look at the new report, it says 'email required' for those users. I don't understand. Does that mean they can't be uploaded without an email?"

Some dev makes a claim that a Serialization library won't serialize a field unless it's public

I don't know the library details after but first reaction was "that has to be BS...."

Then I just do a Google search and yes I'm right.

And of course, in my head I go...why the fuck do these ppl not know how to use Google or just RTFM.....

Or use their brains.... If need for serialization required making all fields public that violates the most basic OOP principles...

This is just funny more then anything 😂

This guy has been fucking up non stop!

He did something incredible, we gave him precise EXACT instructions you couldn’t mistake them

What does he do? Everything wrong.

Granted what he does, works, but... it will take me hours to do what I want to do with the data, if he did it the right way, minutes!

All I wanted was all the active products for this company and their links on the site. He creates an export I can convert to google xml shopping.

What does he do? create over a 100 export buttons one for each supplier so it’s right but it’s all products for that supplier in one file.

So I can do my bit if I just combine 100 files together 😂

It’s funny because there’s already an export that does the exact thing we want just without all the right fields. This is what we asked.

He just needed to duplicate that and add more fields 😂 we think he’s doing it on purpose to be a dick 😂 no one can be that dumb.

I’m laughing cause it’s fucking ridiculous. He’s gonna get fired soon, and he knows it.

Payment gateways are such a big pain to implement. Docs say that they will return values A,B,C but what you end up recieving is X,Y,Z.
And don't get me started on the webhooks, man they return values completely different values from the api end points and with no reference what so ever to the fields returned by them.

Wish i could get the documentation writer's address and may be the dev as well!!

So I spent 2 hours trying to debug my HTML form with data pulled from database. I kept updating the data in the database but the forms weren't changing. Then it finally struck me, Firefox fucking caches form fields on page reload. I use to think this was a convinient feature but now it's just a pain in the ass.

The double-edged sword of teamwork. I'm an indie Game dev, so I have no choice but to work with others of completely different fields. I enjoy it and I get a lot of motivation seeing things done and learning many new disciplines, but team projects have so many downsides when you have to handle everything from programming to cinematography that someone else was meant to do.

My final team uni project I even had to do our music composing cause our sound effects guy did almost nothing in 6 months (he wrote 6 midi notes in 2 weeks at one point).

Calling in all Vue devs here! (Possibly any SPA dev actually)

We're building these fancy live-edit fields for our app. It syncs with the database with every keypress (with a debounce, ofc). Now, we're having a global Vuex module to keep track of the applications sync state. Using this module, we can prevent the user from leaving the page if there is data that hasn't been synced. Though, I think I'm doing something wrong here, and not strictly adhering to the "single source of truth"-principle.

When a user has finished typing, a request is made through Axios. When the response arrives, the field issuing the request updates it's display accoring to the response. However, there is also an Axios interceptor which updates the global state to reflect the latest response. Is this wrong? Should the fields themselves emit the mutation to the store? Or is it okay to use an interceptor since they're running down the same call stack?

I think my biggest worry here is that the interceptor and the field will interpret the response differently...

Help is appreciated :D (and thanks for taking the time)

I have working on a new website for a client that interfaces with their internal systems, meaning we must collect the data fields required by the client. A look over the designs reveals such huge inconsistencies in the data input that we may as well not have bothered designing it.

Is there any benefit of having custom input field dialogs, eg. for date and time? Should I be using just the HTML5 tags as-is (only styling the field itself), or create custom dialogs (creating custom javascript dialogs on top of basic text fields)?

Fun fact: If you ever want to see the password you are typing or view the contents of a password field in a form, just pull up the web inspector. You can change the input type from "password" to "text" with no ill effects upon submission.

The lesson? When populating password fields, put junk values in there instead. Will present the right appearance, and doesn't risk exposing something that should be stored as a salted hash anyway.

I was making software for a small handheld RFID scanner that would read specific fields from the tags. Somehow one of the fields always missed the first byte. Given that I was new to working with C I thought it was my lack of skills in the language. Spent days searching my methods, trying to find my mistake. After day two I found out I was given the wrong address to read from, and that I had just wasted two days.

Been using LastPass for a couple of years, but I'm looking for an alternative because good lord how slow its become. Suggestions?

Needs to be cross-platform/browser and be able to autofill user credentials, don't care about form fields.

I just had the most confusing error ever where clang ast randomly replaced classes with just int in type signatures

...wat? I guess the class only has one int field so maybe there's a cpp rule that requires replacing classes with their only field or something?

But when I add other fields it doesn't change. Even if the class has no int fields, it's still replaced by int in the ast

....

Yeah turns out I had the definitions in the wrong order and clang just uses int for unknown types instead of... you know maybe raising a fucking error

Thanks clang...

When backend is slow to add fields of data, and product manager is after you, the frontend dev to add the new feature.

Work wants me to scroll to invalid fields after validation on a form. Is there actually a use case for that? Because it sounds terrible.

I'm finally gonna try to organize my dotfiles and get my linux work environment somewhat organized

what tiling WM and terminal based editor will I meme myself into oh boy