It happened.

I wrote "you're missing a tab in your python code" as an answer on StackOverflow.

I was downvoted AND told that I wasn't correct: it was missing 4 spaces and not a tab, according to the python guidelines.

Now, I haven't read them, but my Richard Hendrix fucking intensifies.

Fuck spaces. And if python guidelines talk about spaces, fuck python guidelines too!

Okay i'm done - YOU FUCKING ANDROID STUDIO MORONS. Being at a high level in C++, I tried to do some android coding. THERE ARE FUCKING NO GOOD TUTORIALS, NO GOOD DOCS, HECK, THE SELF GENERATED CODE OF THE IDE IS WRONG: WHAT THE FUCK IS GOING ON YOU FUCKING MORONS?
oh wait, let me first import android.widgets.rant;
or was it android.widgets.devrant.rant; or was it android.dr.rant.RantManager;?

Oh wait, I know lets search the docs?
OH WAIT THE DOCUMENTATION DOESNT HAVE THAT.
NOW HOW ABOUT I JUST TRY THE EXAMPLE CODE? WELL UH-UH! YOU HAVE TO FIND OUT YOURSELF WHAT TO IMPORT IN ORDER FOR IT TO WORK. ALSO, WHAT FUCKING UP WITH THAT PERMISSION SYSTEM? ITS SO BADLY DOCUMENTED!!!

Oh wait, I'm sure that I have to change something in this file... or was it that other file?

GOD
how dare they have style and design guidelines?
MORONS!

I will resort to implement my app idea in godot, idc anymore... I don't want to burn out because I used the "official high standard" tech.

it definitely isn't high standard and definitely not good. Thank you morons@google

THANK YOU FOR NOTHING

A FRAMEWORK WHERE I NEED 2 DAYS TO FIGURE OUT TO ADD EVENT LISTENERS TO MY THINGS IS DEFINITELY NOT ONE I'D LIKE TO USE.

also, whats up with

AudioRecord (int audioSource, int samplerateInHz, int channelConfig, int audioFormat, int bufferSizeInBytes);

ARE WE BACK IN THE C ERA? CAN'T YOU BE BOTHERED TO IMPLEMENT SOME SIMPLE FUCKING ENUMS????

WHATS THE POINT OF AN OOP LANGUAGE IF YOU ARE GOING TO USE IT LIKE C?

Oh wait I found a tutorial ... First trigger: "java scripts". Second trigger: this guy LITTERALLY ONLY TEACHES YOU HOW TO PLACE WIDGETS ON THE CANVAS. THANKS FOR NOTHING SHERLOCK!

Oh btw: did you know that android studio gives the best error messages?
"Error: illegal start of expression"
NO ERROR MESSAGE - NOTHING!
YOU BETTER USE THE IDE OR YOU GO HOME YOU FUCKER!!!

Oh and btw: if you want to read the best documentation - the code itself YOU GOTTA AGREE TO OR TERMS OF SERVICE!!!! WE DONT WANT ANYBODY TO BECOME SUCCESSFUL WITHOUT US KNOWING!!!!!

THANK YOU GOOGLE FOR NOTHING!
YOU FUCKERS!

thanks godot for *atleast* existing. You are the... last pick i'd pick, but :shrug:, I have experienced android studio now.

If anybody has any advice on what to use instead, please go ahead. And you better not tell me how good you are at android studio. I DONT CARE ABOUT WHAT YOU CAN IMPLEMENT IN ANDROID STUDIO. I JUST WANT SOMETHING THAT IS USABLE WITHOUT HAVING TO BE EXTRA CAREFUL WHEN DOING *ANYTHING*!!!!

fuckers.

Senior development manager in my org posted a rant in slack about how all our issues with app development are from

“Constantly moving goalposts from version to version of Xcode”

It took me a few minutes to calm myself down and not reply. So I’ll vent here to myself as a form of therapy instead.

Reality Check:
- You frequently discuss the fact that you don’t like following any of apples standards or app development guidelines. Bit rich to say the goalposts are moving when you have your back to them.

- We have a custom everything (navigation stack handler, table view like control etc). There’s nothing in these that can’t be done with the native ones. All that wasted dev time is on you guys.

- Last week a guy held a session about all the memory leaks he found in these custom libraries/controls. Again, your teams don’t know the basic fundamentals of the language or programming in general really. Not sure how that’s apples fault.

- Your “great emphasis on unit testing” has gotten us 21% coverage on iOS and an Android team recently said to us “yeah looks like the tests won’t compile. Well we haven’t touched them in like a year. Just ignore them”. Stability of the app is definitely on you and the team.

- Having half the app in react-native and half in native (split between objective-c and swift) is making nobodies life easier.

- The company forces us to use a custom built CI/CD solution that regularly runs out of memory, reports false negatives and has no specific mobile features built in. Did apple force this on us too?

- Shut the fuck up

"Can you work on this ticket? It's kind of urgent."

-- "OK"

"And could you please not refactor? Just get this done."

-- "Why? What's the issue?"

"The logic is complex. We should not break it."

-- "Erm, that's what the tests are for. So yes, if the need arises, I'll refactor. The tests are my guidelines if the logic breaks or not."

There's a reason we create tests. So let's not hinder code base improvements by some random fear that stuff might break.

If breaks due to refactoring, we'll fix it by adding a valid test case during and then fixing the bug.

If my refactoring does not break the tests, I'll assume the code base is stable.

If your code is untested, then we have a complete different problem.

Don't know if anyone else saw this on Twitter but this is actual text from Apple's updated app submission guidelines lol

Sooooo me and the lead dev got placed in the wrong job classification at work.

Without sounding too mean, we are placed under the same descriptor and pay scale reserved for secretaries, janitors and the people that do maintenance at work(we work for a college as developers) whilst our cowormer who manages the cms got the correct classification.

The manager went apeshit because the guidelines state that:

Making software products
Administration of dbs
Server maintenance and troubleshooting
Security (network)

And a lot of shit is covered on the exemption list and it is things that we do by a wide fucking margin. The classification would technically prohibit us from developing software and the whole it dptmnt went apeshit over it since he(lead developer) refuses (rightfully so) to touch anything and do basically nothing other than generate reports.

Its a fun situation. While we both got a substantial raise in salary(go figure) we also got demoted at the same time.

There is a department in IT which deals with the databases for other major applications, their title is "programmers" yet for some reason me and the lead end up writing all the sql code that they ever need. They make waaaaay more money than me and the lead do, even in the correct classification.

Resolution: manager is working with the head of the department to correct this blasphemy WHILE asking for a higher pay than even the "programmers"

I love this woman. She has balls man. When the president of the school paraded around the office asking for an update on a high priority app she said that I am being gracious enough to work on it even though i am not supposed to. The fucking prick asked if i could speed it up to where she said that most of my work I do it on my off time, which by law is now something that I cannot do for the school and that she does not expect any of her devs to do jack shit unless shit gets fixed quick. With the correct pay.

Naturally, the president did not like such predicament and thus urged the HR department(which is globally hated now since they fucked up everyone's classification) to fix it.

Dunno if I will get above the pay that she requested. But seeing that royal ammount of LADY BALLS really means something to me. Which is why i would not trade that woman for a job at any of my dream workplaces.

Meanwhile, the level of stress placed my 12 years of service diabetic lead dev at the hospital. Fuck the hr department for real, fuck the vps of the school that fucked this up royally and fuck people in this city in general. I really care for my team, and the lead dev is one of my best friends and a good developer, this shit will not fucking go unnoticed and the HR department is now in low priority level for the software that we build for them

Still. I am amazed to have a manager that actually looks out for us instead of putting a nice face for the pricks that screwed us over.

I have been working since I was 16, went through the Army, am 27 now and it is the first time that I have seen such manager.

She can't read this, but she knows how much I appreciate her.

Try to click quickly on this button multiple times and the play store will crash. If you implement this sort button on your own app this will crash too. #google_guidelines 😡

Why is the ternary operator such a hated thing? I constantly hear people saying it's less readable, confusing, etc.

I think it's a beautiful, useful, and important operator and I use it constantly wherever readability won't be much affected.

How can you justify a repetitive if/else structure over a ternary, given that you're sure you're not going to put anything else in the ifs?

Whatever happened to DRY?
Whatever happened to KISS?

If those guidelines are what you code by, what's the excuse not to use it?

Because you can't read it as well? Familiarity breeds comprehension and legibility, my dudes.

The reason why hiring a Recruiter in Software/Web Development industry is a waste of time and money.
- A real story from 2 years ago.

**few minutes of recruiter reading my resume, skills and whatnot**

Recruiter: Okay sir, we are looking for people skilled in C# for our app development and Java for our business software envirnoment. Which one are you interested in.

Me: C#.

Recruiter: I see, well.. I'm afraid we already have someone for the seat.. *checks resume again*.. maybe you would be interested in Java?

Me: Not really, why is that if I may ask?

Recruiter: Well, says here you have experience in Javascript

Me: *trying not to cringe* Yes, but I didn't see any Javascript related job available.

Recruiter: Correct me if I'm wrong, but isn't "Java" just short for Javascript?

Me: No, just like C# isn't short for C and C++

Recruiter: *oops* then I think we do have a free spot for you.

TL;DR - the guy had guidelines but no field-specific knowledge.. I only feel sorry for the other guy who thought he got the job lol.

Shower Thought :
I wonder, in the future, since people is easily offended by everything, variable naming would be such a concern it'll be seriously implemented in the compiler, and be like
"Error at 16:1 NamingConventionError : 'fuckThis' is not linear with our guidelines"

- WE NEED TO KNOW THE VERSION OF THE SYSTEM THIS INSTANT!
"what? version? wtf are you talking about"
- THE CLIENT HAS I.T. GUIDELINES TO STRICT CONTROL THE VERSION OF EACH SOFTWARE VENDOR'S SYSTEMS!
"We are not a 'software vendor', we provide them consulting on logistics!"
- THEY USE OUR WEBSITE! THIS MAKES US A SOFTWARE VENDOR!
"Wouldn't that make 'google' their vendor too?"
- IM SURE THEY STRICTLY CONTROL GOOGLE'S VERSION TOO!
"I'm pretty sure they don't. But, whatever, that do answers the question of what they want. Some paperwork jockey wants a meaningless number to fill a form, let's give'em one"

I just had someone make an API endpoint where they can ask "the version", and it is just the number of commits in our production branch. For lols, we even 0-fill and split every three magnitude orders with a dot, so we're in version 0.012.345 or something.
Major version upgrade every million commits!

Fuck those guideline-parrots who are unaware that words sometimes have meaning, and sometimes not.

Screaming at a coworker?
The INTJ in me has prevented that pretty well in almost every critical devSituation.
BUT one time in the past, I was really close to a level 9001 scream:
This fucker, despite having been told about code formatting guidelines and DRY/KISS multiple times, had the balls to commit such utterly crappy and unreadable code that I almost bursted.
He quickly realized his mistake after I reset the repo to before his push, disabled his Gitlab account and wrote him a simple email containing the text:
"IF YOU EVER COMMIT SUCH SHIT AGAIN, THERE WILL BE UNFORESEEN CONSEQUENCES. GFYS."
After a peaceful coffee and a croissant I decided to re-enable his account. He did good after that.

I fucking want to skin alive my engineering senior director and VP.

Fucking piece of shit people. Looking at their faces from behind the screen, I can sense them stink doneky balls.

They have made my life hell.

The entire tech architecture is absolute shit in nature and engineers cannot even build a single blue colour button without creating a major fuss about it.

Every single aspect of product is built kept in my only the engineer persona. Everyone else can go and suck a racoon's dick.

And they have no concept of tech debt. They just keep building and building stuff. And then build some more.

Entire engineering org is in rush to ship shit at the end of sprint and if they don't then VP and Director are pissed. So to keep those two half witted donkeys happy, these people ship garbage. And all they comment is "cool, very cool".

And hence, entire fucking product is built because it's cool irrespective of whether it solves a problem or not.

A single user role authorisation or authentication is so fucking complex that it would take an eternity for even a developer to figure what's happening.

Fucking toxic human wastes.

There's a company wide mandate to use a certain tech stack, design guidelines, and a vision that all teams have to align. But these faggots are going in opposite direction to do what they feel like and forcing everyone else to ignore all other engagements or alignments with other teams.

These two people should be skinned alive in town square during noon and then left there until they dehydrate entirely. Fucking baboons.

I am so fucking pissed with such mindset.

I'm not sure whether to cry or to burn everything to the ground.
I'm stuck in a rotten, over aged corporate that will one day choke on all the documents and formalism they require. Which is something I'm generally fine with. Each to their own.
But ever since I handed in my resignation they have been fucking me like I have never been gang raped before.
(A little context: I work for a midsize financial institute. Which at least in Germany are full of legacy projects and are regulated as all hell.)
So some fuckwits decided that since the regulator slapped us hard 2 years ago that we need to make up a new standard of documentation that has to be used for all IT-documentation there ever was and ever will be.
So the upper management (the before mention dumb-dumbs) choose some consultant company and locked them up together with the brightest stars (read biggest slime balls) of the IT department in an ivory tower and told them to pull some out the ass.
And one year later (early November last year) they got the shit they ordered. Gilden shit, only the most sparkly and non-sensical bullcrap you could imagine.
But they only looked at it and deemed it good. Now the guys actually in charge of the the applications got served the dish. And guess what they found out when started to dig into? Nothing but contradictions, non-final thoughts and all of that held together by web of retarded, unusable guidelines. But they ate it, they cursed but they swallowed forced by disciplinary punishments waiting should they misbehave.
The only one emerging fact was: All previous documentation was completely invalidated.
But now the mighty lords in the ivory tower guided by the never failing hand of the higher management had the greatest idea of them all. They needed someone to check all the documentation till the end of this year but since they blew all of their budget on useless wankers ( oh, ofc I meant "highly qualified external help") they now preyed on the lowest in the food chain. Which is where this story goes full circle and comes back to me.
I was the lowest rank on the food chain, a student that just handed in his resignation.
I was the first to be locked up in the basement, my co-student followed shortly after.
And now I'm going to spend my last 2 months looking at checklists that we had to pull out of the slime's ass and validating hundreds of thousands of pages of documentation. We get grinded up in the endless hate coming from the guys that we need to tease and are held in position by a wall of sheer idiocy on the side of the rule makers.
Today I cried when I had to tell someone that his magnificent documentation was not standard conform and had thus no longer any meaning or right to exist.
Thanks you for those that made it this far down. I hope you never have to feel my pain.

I love how the Keybase Linux client installs itself straight into /keybase. Unix directory structure guidelines? Oh no, those don't apply to us. And after uninstalling the application they don't even remove the directory. Leaving dirt and not even having the courtesy to clean it up. Their engineers sure are one of a kind.

Also, remember that EFAIL case? I received an email from them at the time, stating some stuff that was about as consistent as their respect for Unix directory structure guidelines. Overtyping straight from said email here:

[…] and our filesystem all do not use PGP.
> whatever that means.

The only time you'll ever use PGP encryption in Keybase is when you're sitting there thinking "Oh, I really want to use legacy PGP encryption."
> Legacy encryption.. yeah right. Just as legacy as Vim is, isn't it?

You have PGP as part of your cryptographic identity.
> OH REALLY?! NO SHIT!!! I ACTIVELY USED 3 OS'S AND FAILED ON 2 BECAUSE OF YOUR SHITTY CLIENT, JUST TO UPLOAD MY FUCKING PUBLIC KEY!!!

You'll want to remove your PGP key from your Keybase identity.
> Hmm, yeah you might want to do so. Not because EFAIL or anything, just because Keybase clearly is a total failure on all levels.

Written quickly,
the Keybase team
> Well that's fucking clear. Could've taken some time to think before hitting "Send" though.

Don't get me wrong, I love the initiatives like this with all my heart, and greatly encourage secure messaging that leverages PGP. But when the implementation sucks this much, I start to ask myself questions about whether I should really trust this thing with my private conversations. Luckily I refrained from uploading my private key to their servers, otherwise I would've been really fucked.

You wanted to hear more about my "glorious" teacher. I deliver. So get a cup of tea, take a seat and prepare for insanity.
As I already told in a comment my programming teacher is one special snowflake who lives in his personal bubble. We have final exams in less than a month and he spents at least half a lesson talking about vanishing bees and missing plants from his garden. Other topics he likes to talk about (and tries to turn every freaking conversation into at least one of these):
1. Other students and their stupidity
2. Diesel scandal
3. His sick wife
4. "Why does noone read newspapers anymore?"
5. Why he can't teach Java but really really really wants to and everyone hates him and forces him to do C#.

Even if I try to interrupt him he'll go on until he thinks we gained some "common knowledge" - this is how he justifies these topics.

Everytime he introduced us to a new command he compared it to Java and sometimes he even falsely corrects code because he confuses them.
We are only 6 people including me (another story for another time) and he is not able to help everyone during a 90min lesson. He normally sticks with one person for at least one hour and just talks to them or even do their tasks. This is really annoying if you have a simple question. He won't answer you until he's finished whatever he's doing.

Most of the time he doesn't seem to understand what he's talking about/trying to teach us. He's muttering statements from our textbook to himself switching halfway through to another sentence while drawing not decipherable shit on the blackboard.

Another gem are his "guidelines" for classtests. We are allowed to use any command we know. Except the ones we learned not in class. And the ones he doesn't like. And the ones he doesn't want to exist. And of course not the ones which make you're life easier. So basically we are bound to use his favourite commands or we won't get a good grade. Example: use an array. List is not allowed. Never.
He has some weird fetish with arrays.

I once presented him perfectly fine code I wrote in my freetime and asked what some warnings meant. (Was because of different Visual studio versions as I learned later.) He scolded me for using things he didn't taught us yet and ranted about how I'm pressuring him into rushing these things now - I never wanted to show this to my classmates nor was this anything else than a project for fun and learning something new. (FYI the "new stuff" where classes and objects because i was tired of kilometers of spaghetti code). His rant went on a good 20minutes and - obviously - he didn't answer my question. I asked my fiance that evening and he explained it to me.
This should it be for this time. I'm sure I have more stories to tell for another time!
Thank you for reading. ^^

Currently developing an android app that is a clone for an existing iOS app. Sadly all the PMs and POs (the P-M/O fraction) at this firm are somehow iPhone users.
So every time we implement stuff according to android guidelines some PMO comes around and asks: "why doesn't this look/work/smell like in iOS?"
Somedays I feel like crying...

Telling the customer that they are breaching guidelines.

"This cannot be against the guidelines. We always did it that way"
...
Ehm. You did what?

So the CEO tells me our new release needs to be compliant with new guidelines. I say sure, I draft up a few small changes and send them to my PM. He calls an impromptu meeting with the UI team and I explain my changes. They don't like them. They then proceed to draft and redesign a new UI based on these new requirements, I tell them that they are overthinking everything and remind them of the rules of KISS. 45 minutes of me silently waiting and an entire 4x8 whiteboard of designs, I tell them this is an entire redesign and that we will never make our end of the year deadline. PM goes silent for a minute, then responds "yeah I guess your right, let's just implement your original changes"

So we send a quote out to a client to update his website to make it compliant with the new privacy guidelines: SSL encryption, removing external libraries, removing Facebook Plug-ins, all that stuff. We didn't get a response.

On Monday, he called in a panic. "The website does not work, fix immediately!"

I check out the server, what do I see? An SSL cert installed the Friday before... Client decided to do it himself, on a Friday, without testing. He broke something, but cannot tell me exactly what he did.

And somehow he thinks all that is my fault :D

Long rant...

*Designer Posted image of newly designed layout for our app on trello.

Dev 1 (me, being the junior, on ios) : so... What's the size for x, Y, z, a, B, C?

She: it's 9 for the small text, 10 for sub title, 12 for main title.

*shows her the design on app
Dev 1: seems too small

She: just make it to look not small.

Dafug?

*finishes the app layout for that screen.
*working on next screen

Dev 1: your new design is for the screen of 1920x1080. But our supported screen size starts from 320 width. So there'll be text overlapping each other and ui might screw up.

She: uh.. Just... Put those that will overlap to the next line.

*shrugs
Dev 1: ok
=======
2 days later
Dev 2 (senior, working on Android)
Dev 2: so... What's the colour for x, Y, z

*Dev 1 laughs on the inside because of the struggles we have with her.

Dev 1 to Dev 2: is it common for her not to follow the design guidelines?

Dev 2: yeah man.. We just have to adapt her design into our app guidelines.

*sigh

Dev 2: there's a new icon here on this screen, so you wanna change the icon? Can I have the icon file?

She: oh.. No.. Use back the old one, because I just copy and paste.

Dev 1: so... This progress bar of yours, doesn't show its background colour, because you filled it already. So what's the background colour if the bar isn't filled?

She : hmm.... Oh.. Well.. Maybe try x.. ? *doesn't look nice* how about Y? *doesn't look nice* how about...

Me : why not you try in your computer first instead of me changing it here by code, it's much faster this way.

*seriously, wth?

Dev 1 and 2: there's additional text in your new design, what is it for?

She : oh.. No no. I copied extra due to copy and paste. Just ignore it.

Dev 1 and 2: what's the spacing gap between x and Y? And how about the size of the box?

She : oh.. I just estimate it, and for the box, not sure either, you can follow old design, because I'm just putting a box there for illustration purpose.

Mother fickle, what fuck man.

Dev 1 and 2: *flips table.
*we didn't, but.. It's freaking annoying.

This happened via mail thread today.

Boss: we need this new brilliant feature I just made up and running asap! Top priority, it has to be done well, for my reputation is on the line!

Me: *looks at the specifics* 'kay, looks easy enough, this evening max and it will be ready. I just nees some extra info about what kind of data validations (I speak no accountant) are needed, and some other details (a total of 3 questiona).

B: Sure! Remember, it needs to be perfect, as my reputation is at stake. Call me on the phone and I'll give you the details!

M: Can't you answer via mail? Thua way both me and the other devs will have clewr guidelines

B: Just call me! Why do you need it to be written down? It's faster this way!

...Fine. I'll keep asking until you're ready to give me a written answer to my questions. No way I'll take security details via phone for something you want in production this evening. No chance in Hell I'll take responsibility for "misunderstanding" what you said on the phone. Why does it always has to be like that?

Fuck Apple and its review system

So, this started in december. We wanted to publsih an app, after years of development.

Submit to review, and passes on the first try. Well, what do you know. We are on manual release option, so we can release together with the android counterpart. Well yes, but someone notices that the app name is not what was aggreed (App Name instead of AppName). Okay, should be easy, submit the same app, just the name changed. If it passed once, it will pass again, right? HAH

Rejected, because the description, why we use the device’s camera is too general. Well... its the purpose of the app... but whatever, i read the guidelines, okay, its actually documented with exapmles. BUT THEN WHY THE FUCK COULDNT YOU SAY THAT ON THE FIRST UPLOAD?

Whatever, fix it, new version, accepted, ready to release just in time.

It doesindeed roll out,but of course, we notice that the app has a giant issue, but only on specific phones. None of our test phones had this problem, but those who have, essentially cannot use our program. Nasty as it is, the fix is really easy, done in 5 minutes. Upload it asap, literally nothing changed from user point of view, except now it doesnt crash on said devices. Meanwhile 1 star reviews are arriving from these users - of course with all the right. Apple should allow this patch quickly, right? HAH

THE REAL BULLSHIT COMES NOW

With only config files changed, the same binary uploaded we get rejected? What now? Lets read it. “Metadata rejected, no need to upload new binary”.... oh fine only the store page is wrong? Easy. Read the message, what went wrong. “Referencing third party content is nit permitted on the app store” meaning that no android test device should be shown. Fine, your rules. They even send a picutre of the offending element. BUT ITS NOT EVEN ON THE STORE. THATS A SCREENSHOT OF THE APP. HOW IS THAT METADATA? I ask about this, and i get a reply, from either a bot, or a person who cant speak or read english, and only pasted a sample answer, repeating the previous message. WTF. Fine, i guess you are dumb, but since they stop replying to our queries, do the only sensible thing, re-record the offending tutorial video that actually contained an android device. This is about 2 weeks, after the first try to apply a simple patch to a broken app. And still, how did it pass the review 2 times?

Whatever, reupload again, play the waiting game for a week, when the promised average wait time is 2 days, they hit us with a message, that they want to know what patent we use in our apps core functionality. WTF WHY NOW? It didnt bother you for a month, let it release ti production and now you delay a simple patch for this? We send them what they know. Aaaaand they reply: sorry we need more time to review your app. FUUUUUUCKKK YOUUU. You are reviewing a PATCH with close to zero functional change!!! Then, this shit goes on, every week we ask about an ETA, always asking for patience... at the end it took another 3 weeks... so december 15 to jan 21 in total...

FOR. A. SINGLE. FUCKING. PATCH

Bottom line is what is infurating, apple cares that there is an android device in the tutorial video, but they dont care that a significant percentage of our users simply cannot use the app.

Im done

What. The. Actual. Fuck.

My co-workers just tried to convince me that the following is a secure password:

"ThisIsASecurePassword2018"

Just... I mean... Why? *sigh*

Their argumentation is based on the new NIST guidelines.

If they've read these guidelines CAREFULLY though... (not only the appendix) it actually states "Don't use words from the dictionary". Passwords like these should even be rejected right away.

Holy shit. Didn't know I had to vent this out before I had revisited this shit.

Storytime!

Back in May last year, I started working on a dream project (call project X) of mine. Surprisingly it's still a novel idea and shit like this doesn't exist. Made some huge incremental changes. Added all the necessary automation pipeline stuff. Added some sick ass readme with screenshots/badges/glitz/glam.

Worked my ass of for about a month or so until I got distracted by other pending projects in need of clearances. Somewhere partway in that clearance period, I receive a mail from this "GitHub user" asking me why the development of project X had suddenly stopped.

I was a bit taken aback. Firstly because my project had ZERO stars and NO user interaction. Secondly because I hadn't encountered someone with confrontation like this since my middle-school teacher asking me for my homework.

Being the good, responsible child I am, I informed them on my situation and asked them to contribute according to the guidelines and I'd be more than happy to see this becoming a joint effort by the community.

Apparently, they were quite ecstatic to learn that my development was halted. They didn't have plans to contribute. Instead they wanted me to take down the project and stop working on it entirely.

Tough luck fucko.

Their organization had been working on something similar for longer than a couple of years. A similar open-sourced project will *apparently* ruin their market impact and I can *apparently* be sued for it.

I don't know much about open-source "laws" (and I've seen laws fuck people over) but this just seems retarded. At the moment, I'm not quite sure how to continue with the project. I'll still work on it but the fact being that I started receiving threats before stars makes me question the gatekeeping capacity of toxic market conditions (I still don't blame the person entirely. It's just really hard to keep your head above the water)

This is a one off thing but somehow it has definitely hampered my drive to work on the project (combined with the sheer amount of pending project that I've dug my grave with).

On the brighter side I've got 10 anonymous stars with zero promotion. 2 new message threads with productive insights and a person who says "I'm relying on this to work out". So not everything has gone to shit.

1. Naming all variables with letters of the alphabets
2. Not indenting (screw tabs VS spaces, I could use anything here)
3. Putting all src files in one directory
4. Writing the entire code without using any functions
5. Writing code and asking me to fix linting
6. Asking why they should follow language style guidelines

So far all designers I worked with do the following:
1. Use "creativity" to come up with stuff that the system does not allow implementing, for example: Changing clock color in mobile statusbar to Blue!
2. Use "creativity" to come up with a heavily customized calendar for a windows software which requires building the control from scratch, but they explain their creativity by saying: Can't you use CSS?
3. Provide iOS only design which follows android guidelines and refuse to provide android styles for at least pages that to be handled differently on each platform, for example, we had a checkout page in an app, and they wanted the same style for both WITHOUT building custom control for it, they said: Can't you use the android custom control inside iOS
4. They design for a website and send same mockups for me to implement on mobile apps, the problem is a web page runs on a big screen when the mobile app doesn't have room for half the stuff they designed but they must look exactly the same as website !!
5. They send entire PSD with no color codes and say: You can extract icons, and colors from psd ... When they should provide them as per our request which is: SVG for Android and PDF for iOS with the color codes, but no, they are lazy!
6. They ask the team to create a page in the app which is almost production ready just so that they test different font sizes and see how it will look on the phone
7. Same as #6 for images that contain text

The list goes on, but those are by the far the ones that made me one step away from resigning, some of them made me resign...

Told juniors about coding guidelines that don't put another if-else just to fix a bug. Think through about it and see if you can come up with better solutions.

Today one bug was filed, they asked what happened, one junior said that he [my name] asked me for no if-else in code. He kinda deleted all if-else in codebase and started using same implementation for everything.

I'm standing with a WTF face.

😐

> Telegram bot
> Whatsapp bot
> Domino game in terminal (Unfinished from last year)
> Bubble shooter game using c & allegro 5 (Unfinished from last year)
> Android Notability-like app with more features
> Program that increases youtube video views
> Android animal space invaders
> Own website/portfolio
> Our company app (includes daily euro-peso exchange rates, guidelines and other stuff about the company)

ive had other ideas but i started losing them cause i wrote them in several small pieces of paper. starting to think of i'll start to have a notebook dedicated to "ideas"

This isn’t gonna be a random because I do eventually get to a Tech and YouTube related topic.

YouTube is actually killing itself with all of the dumbass rules they’re implementing. Trying to child proof or limit educational content is genuinely a shit policy. The reason so many gaming channels are switching to twitch because it doesn’t try to censor you.

But now I don’t know if you’ve heard but YouTube updated their guidelines and they’re no longer allowing content that teaches people about Hacking essentially (and I hate putting it like that but I can’t remember the exact words they used Hacking just summarizes it) which is fucking ridiculous like what the fuck else, are they gonna stop allowing lock picking videos?

YouTube has always been an amazing FREE resource for people learning Programming, Cyber Security, IT related fields, and even shit like lock picking, cooking, car stuff, and all that stuff. Even sometimes when the tutorials aren’t as detailed or helpful to me they might be exactly what someone else needed. And Cyber Security can be a difficult topic to learn for free. It’s not impossible far from it, but YouTube being there was always great. And to think that a lot of those could be taken down and all of the Security based channels could either lose all revenue or just be terminated is terrifying for everyone but more so them.

A lot of people and schools rely on YouTube for education and to learn from. It’s not like YouTube is the only resource and I understand they don’t want to be liable for teaching people that use these skills for malicious purposes but script kiddies and malicious people can easily get the same knowledge. Or pay someone to give them what they want. But that’s unfair to the people that don’t use the information maliciously.

It’s the same for the channels of different topics can’t even swear and it’s ridiculous there’s so many better options than just banning it. Like FUCK kids nowadays hear swearing from their older siblings, parents, friends, and TV it’s inevitable whether someone swears or not and YouTube is not our parents, they aren’t CBS, so stop child proofing the fucking site and let us learn. Fuck.

TLDR YouTube is banning educational hacking videos and are being retarded with rules in general

What do you do when another dev overwrites/changes your working code without telling you, only because s/he cannot understand how your code works?

And your code was working fine, mind you, no bugs or anything, and is following recommended guidelines/standards. It's just that this other dev has a different coding style and prefers to rewrite everything his/her way even if it means breaking up otherwise sound logic.

“PHP is evil” is not just a joke.

PHP is usually percieved as a language which is not so consistent and has some opinionated historical aspects but allows rapid development because it’s easy. They say PHP doesn’t focus on that “purist shit” such as concepts and “just gets things done”.

Hovewer, this is not true. PHP lures you in and lies to you promising saving time on development, but everything, and I mean EVERYTHING written in PHP is doomed to turn into a bloody mess sooner or later.

You have to be an AI to manage the growing PHP codebase and add features without breaking anything. With every feature it gets harder and harder. If you’re still a human managing a human team, you have to enforce guidelines. Automatic error preventon measures are made of code themselves so the cost of deploying them ona late stage can be ridiculous. And you never deploy them on early stage because you want to “save time”. Your people have to spend more and more time everyday checking on that guidelines. Your development process only becomes slower and slower. If you try to push things, your project will crumble to dust.

To make PHP at least decent, you have to figure out all this by yourself on an early stage. When you’re done, you spent a lot of time creating the buggy, ad-hoc, unspecified and unsupported alternative of what works out of the box in other languages. And you still code in PHP and still have all its disadvantages in your project’s DNA.

PHP is evil because it promises and never delivers. PHP is evil because it lies to you and it already fucked over so many of us.

If you want to code in PHP, do it under your pillow. Code your own silly projects.

If your project has the word “production” somewhere in its plans, PHP is not the way to go.

Amen.

My non-tech friend was looking into a degrees guidelines for N.C. State University and they recommend C++... she thought C++ was the grade she needed to average to get that degree. 😂

Feeling sick as fuck. Stayed home instead of going to work but I am already upstet about what is happening whilst I am not there.

The manager was gracious enough to task the other developers with creating the templates for one of our projects. I submitted a document before stating our design guidelines and how under no circumstances they should not use bootstrap for the design since none of them know how to manipulate the source code enough to deviate from the standard bootstrap design. The lead developer, even tho I love the dude, has an attitude against new tech. He is primarily and only a php developer still in love with just jquery and php with no real knowledge of proper design methods. He is the kind of dude that would tell you that pdo is a waste of time and that why should we create models and use oop to separate our code into manageable files.
Today I get "why should we not use bootstrap" and shit like that.

Sigh.....i really don't want to see the shitstorm waiting for me tomorrow.

Funny how our cms administrator is eager to learn the list of technologies i proposed. They both gor Programming Ruby, the pickaxe holy book of Ruby and the dude is already halfway through it while the other developer is still asking why should we even bother when we have php.

I get the idea of if it ain't broken don't fix it and being proficient with one stack and whatnot. But that idea of i dont want to learn something new is precisely what shuts down progress.

CAN SOMEONE PLEASE TELL ME HOW TO TRANSLATE PULL REQUEST TO GERMAN?

According to one of my teachers I have to translate this in a coding guideline otherwise other devs might not be able to follow the procedure...

I asked him how he would translate it and he could not give me a proper answer... describe it he said...
How the fuck does it improve my guidelines if I describe PR!!!
And if your not capable of doing it better how should I know I have to do it!

Sorry I looked at an old exam and got triggered when I saw the correction

Only if people understood the amount of effort that goes behind building a simple app.
Even if it's a simple notes app, I've to design the UI (at least 2 different activities - 1 for the list and the other for editing notes), write the code which makes it run i.e. without which the app is just a piece of empty design, think about what data
structures to use (that notes you are saving need to be stored somehow) and then club everything together and hope nothing breaks (spoiler alert: something will definitely break).

People need to understand that it's not just putting some fancy buttons and boxes around. Also, I'm not just making the app for one device. I've to make sure it works on different screen sizes, different versions of the OS (a user can't imagine how many functions need to be re written because something got deprecated in the process and I'd to switch to something different).

Also I'm not just sitting at my computer and converting coffee to code. I've to think about the flow, structure, design, navigation, backend etc. Of the app; most of my time isn't spent writing code but thinking/studying how to write the code. I also need to wait while the project is compiling/building every time I want to test it.
A function which you think is hard to implement night be really easy while something you claim is easy might be a nightmare. Oh and I didn't even mention how I need to stick to some design guidelines to make the app look consistent with the rest of the OS.
If you're wondering why a developer is spending most of his time on a browser, he isn't playing internet games or browsing reddit ( at least you better hope not), he's probably looking at the docs/stack overflow to get something to work/fix something!

Wow! That was long. Thanks!

The fact that I have to convert a 90s-ish design into a WordPress theme despite the boss trying to convince our client that WP's shit and we should do it in something else doesn't tilt me as much as it should.

But what DOES tilt me and piss me off is the fact that the shitheads told us to 'make the design better', and so I tried; I made one of their graphics responsive by only designing it with CSS (and for once, I even made it work right) because they wanted a mobile-friendly version but failed to supply a mobile-version PSD so I had to improvise and they had the balls to tell my boss that they're 'disappointed that we failed to follow the guidelines'.

Did you bitchsicles even bother to hire a proper fucking designer who would know how to fucking design a PSD to convert into HTML? There's no fucking grid, the design's all over the fucking place like your mother after a Viagra-fueled Friday night bukakke party at an old home and the colors are an eyesore like your own fucking selves if you ever bothered looking in the fucking mirror. Fuck you all to hell.

The client always goes like... I want the android app to look exactly like the ios app.... Am like you know these are two platforms with different designs guidelines

Lack of documentation on internal deployment process/tool we are forced to use, but can't migrate because the process owner won't approve it because it doesn't meet their unposted ever changing guidelines.

So recently my open source project took off and got trending on GitHub (680 starts and 225 forks). This was the first time a project of mine really gained some traction and invested more of my time and weekends to maintain this project - I wrote comprehensive docs, contributing guidelines and reviewed PRs and made sure I commented on every single one of them. Sure, it isn't easy to review 50 PRs a day after coming home from work but the excitement of seeing this project becoming trending fueled me.

First 2 weeks it was good. I would come home from work and have dinner and sit down to maintain the project. Whenever contributors would be stuck, I would help them and write comments on each PR.

But the problem started since last week. People just really want to see their contribution activity graph get populated and hence they would make stupid PRs and literally no one followed contributing guidelines - I mentioned in that that the code should adhere to Pep8 styling but no one gave a shit. Each day I would spend reviewing PR with crappy formatted code and no sign of Pep8, and even some will just file PR and add a fucking docstring to every function or add paragraph of comments. Also, the PR quality was bad with unsquashed commits amounting to 10 or 20 or even sometimes 50.

I wrote the contributing guidelines doc and in that I mentioned every source that contributors could find helpful like how to squash commits, how to file a PR and Pep8 and not to write useless comments. Seriously people, grow up!

Help. I'm drowning in spaghetti code

I've been working at a working student (15 hours/ week) at a local software company for about a month now... and with everything I learned at college I'm kind of getting eye cancer here.
We still use SVN
We don't have any coding guidelines. No checkstyle, no overview over the program. When I started there I was just giving a ticket and they said good luck.
We just have some basic RCPTT Tests inside Eclipse and most of Themen don't work in the trunk because the gui got changed...
At least we have a ticket system but it doesn't get used by most of the working students.
I found 10 other bugs while reproducing and trying to fix 1 bug.
And I've never seen Java raped so badly. Today I saw a line that started with 6 brackets because whoever wrote it wanted to cast like there was no tomorrow. I see more instanceof in one day than in my whole devlife before.
The only thing we have is two normal employees that review our code before we are allowed to commit it into the trunk.
So yeah... I'm drowning in spaghetti-code.

The feeling when you realize some people on the project are writing legacy code from scratch. Apparently it seems they've never heard of any coding standards, they think clean code and style guidelines are for the weak and single responsibility means one single method is responsible for a bunch of unbelievably diverse things. They are like the Gumbys of the dev realm but it's my brain that hurts every time I have to deal with their code.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

!Rant
Reading through MDN's accessibility guidelines and realize I've never consider how disabled people would browse on my sites. From now on,I will try to make my sites accessible as much as possible for those people too.

The penalty is death

IMHO technical dept is kind of like smoking cigarettes for some decades.

You were told that shit will hit the fan but you do not take proper action. And one day you'll realize that you fucked up (or not, also seen that).

Worked for a company in IT, where we maintained an ERP which was "in progress" for over a decade. The basic implementation was done by people with zero technical understanding. To clarify: not self coded. Software was bought. We are talking about integrating the system.

Therefore, the foundation was like a wet noodle. When I joined that company, I told them that they need to address that. I told them that things will get slower and slower and that shit will hit the fan if no proper actions taken.
Even made a list with flaws I found. With potential risk and actions to take, that could then be measured.

At that time, five people worked in said department (including me).

People did not want to listen. "Would be too expensive to rewrite stuff".

Nothing has changed about the wet noodle, but I tried to fix as many things in a working system as I could. Felt like heart surgery, because changes got implemented and "tested" in prod. No version control, no documentation, everyone implemented things like they felt (no guidelines for consistency).
A lot of small fuckups that summed up over the years.

I left the company after two years because I had the chance to land a job as a dev.

Been around two years now since I left. Now 9 people work in that department with around the same efficiency as us 5 people back then.

The new employees struggle to be productive, because things are just implemented poorly and not maintainable anymore.

Had some dialogs with them some time ago. Everything I told them would happen, actually happened. What a suprise :-|
I will not go into too much detail about all the shit that's going on there, as it would be just too much (and my morning coffe is almost finished).

I think that we all know the difference between "not beautiful, but does the job" and "oh, that will backfire - badly". And I wish that my communication skills increase so that people start listening in future.

Client is A BIG corporation
Client want an large app and has its own ui guidelines
Client sends design
Client doesn't follow its own guidelines......

Spec meeting with my client: "Accessibility is very, very important to us. We want to be sure that we meet AA guidelines, at a minimum."

Client delivers front end mockups, can do nothing. Not one single element on it is compliant - have to send it back for revisions.

The fact that they were aware of the WCAG and the AA tier guidelines, and still handed me these shitty designs is pretty impressively stupid.

I've been using the Square REST API and I spent one hour thinking there was something wrong in my code until I f** found that THEY were not following OAuth 2 guidelines, which made their workflow incompatible with the OAuth lib I was using, so I had to mark an exception for Square's OAuth from the rest of my OAuths. Specifically, RFC 6749 Section 4.2.2 and 5.1.

However, after reading OAuth 2 guidelines, I became angry at THEM instead. The parameter `expires_in` should be the "lifetime in seconds" after the response. This will always be innevitably inaccurate, since we are not taking into account the latency of the response. This is, however, not a huge problem, since the shortest token lifetimes are of an hour (like f** Microsoft Active Directory, who my cron jobs have to check every ten minutes for new access tokens). Many workflows (like Microsoft, Square, and Python's oauthlib) have opted to add the `expires_at` parameter to be more precise, which marks the time in UTC. However, there's no convention about this. oauthlib and Microsoft send the time in Unix seconds, but Square does this in ISO 8601. At this point, ISO 8601 is less ambigious. Sending a raw integer seems ambiguous. For example, JavaScript interprets integer time as Unix _milliseconds_, but Python's time library interprets it as _seconds_. It's just a matter of convention, a convention that is not there yet.

Hope this all gets solved in OAuth 2.1 pleeeaasseee

We need an open-source alternative to stack overflow. They have fucking monopolizing pieces of ratshit admins there and lame ass bots.

I HAD A FUCKING 450 REP :/ and now i have "reached my question limit"

I mean its okay of you want to keep stackoverflow clean , but straight out rejecting the new queries should be against your god damn principles, if those mofos have any!

If it is so easy to downvote and delete a question for the mods, why can't they create a trash site called dump.stackoverflow.com ? whenever a question is not following their stupid guidelines , downvote it to oblivion. After a certain limit, that question goes to dump space where it will be automatically removed after 30 days. Atleast give us 30 fucking days to gather attention of audience !

And how does a question defines someone's character that you downright ban the person from asking new questions? Is there a phd that we should be doing in our mother's womb to get qualified as legitimate question author?

"No questions are stupid" is what we usually hear in our school/college life. And that's a stretch, i agree. Some questions are definitely stupid. But "Your questions are so stupid we are removing you from the site" is the worst possible way to deal with a question asker.

Bloody assholes.

Now, can anyone tell me that if am passing a parcelable list of objects in an intent before starting a new activity, how can i retrieve it in the new activity without getting any kotlin warnings?
The compiler is saying that the data coming via intent is that of list<Type!> aka list of platform type, so how to deal with this warning?

I agree with many people on here that Front-End web development/design isn't what it used to be.

Things used to be simple: a static page. Then we decoupled design from description and we introduced CSS; nice, clean separation, more manageable - everything looks nice up to this point.

Introduce dynamic pages, introduce JavaScript. We can now change the DOM and we can make interactive, neat little webpages; cool, the web is still fun.

Years later, we start throwing backend concepts into the web and bloating it with logic because we want so much for the web to be portable and emulate the backend. This is where it starts to get ugly: come ASP, come single pages, partial pages, templates,.. The front-end now talks to a backend, okay. We start decoupling things and we let the logic be handled by the backend - fair enough.

Even later, we start decoupling the edge processes (website setup, file management, etc.) and then we introduce ugly JavaScript tools to do it. Then we introduce convoluted frameworks (Angular,..). Sometimes we find ourselves debugging the tools themselves (grunt, gulp, mapping tools,..) rather than focusing on the development itself (as per ITIL guidelines; focus on value), no matter how promising today's frameworks claim to be ("You get to focus on your business code"; yeah right, in practice it has turned out differently for me. More like "I get to focus on wasting copious amounts of time trying to figure out your tangled web").

Everything has now turned into an unfriendly, tangled web (no pun intended).

I miss the old days when creating things for the Web used to be fun, exciting and simple and it would invigorate passion, not hate.

<my cents="2"></my>

My company is (supposedly) all about collaborative work, pair programming, getting on calls and cRaCKinG tHinGs ToGEtheR. Also (and rightfully so) we’re not supposed to approve any PRs if tests weren’t created/updated.
Of course that applies to all but the old timers in the company who simply act like lone cowboys. They fall off the face of the earth for two-three days then reappear with monster PRs full of untested code.

Leave it up to the plebe then to try to make sense of the mess they’ve created, to challenge them with the fact that the PRs are lacking tests (only to be met with excuses about not having anymore time to spend on the subject).
Reprimand the plebe for not reviewing PRs thoroughly enough. Leave it up to them to fix the resulting bugs.

I’ve lost all trust in our managers, tech leads, lead devs and their guidelines and rules that only apply to others but rarely to themselves. These people that then have the audacity to criticize the tech team in it’s entirety for not being rigorous enough in its processes.
Fuck them all

In my previous company we developed a CRM web app for the company to use internally and it was in my humble opinion really easy to make sense of, but for some freaking we kept getting calls whenever someone got an error, and our default response was always to send us an email, then we will get back to you, as it was mostly stupid things they called about, for example, a customer might have to be status terminated, before you can click button A, button A would then be disabled and employees would call asking why. Apparently, people got annoyed by our response and went to the management, to get some guidelines as to when they could call the "development apartment" for help, so the management sends out some guidelines as to when they could call, write or whatever... The following was done without consulting us in any way ANY WAY AT ALL!... Because we all know management knows fucking best, and why bother asking the people that sit with it every day, and the way it was done was by saying:

If the background color on your error is red, it means the error is fatal and you can call the developers immediately, if its orange send an email and they will answer within 48 hours LIKE WTF... Seriously???. That was basically it, and honestly we had just been using colors, without much thought to it ofc red, was an error etc. But they we're not "OMG EVERYTHING IS BREAKING" alert, so we decided to use a couple of hours refactoring the color of the flash errors, and after that, we did not have many red alerts(None, yes none what so ever) We changed all the red ones to orange, and introduced some new colors. That worked for some time around 6 months or so, but then people obviously started calling again like, why even bother... So we created a simple service desk, blocked all incoming calls to our phones that were from regular employees, heard a lot of complaints about this from the employees, management was mad, we had so many meetings with those top paid management fuckers that know everything (way better than you and me), about how to handle this. As it took way too much of our time, that people couldn't bother trying simple things, or make some sense as to why a button is disabled etc. We ended up "winning", was allowed to block calls for some time, till the employees had learned to use a freaking simple service desk, it's not fucking rocket science Okay, stop being a pain in the ass... And it actually fucking worked! Most relaxing time after people got a hang of using the service desk instead of calling life was good after that... <3

Am I the only one who encounters these dickhead teachers, who live in a world, where they think that you have just their subject?

I mean that kind of professor, who shows up 30 minutes late to a lecture, sends you source code with no commetary because fuck you with a rusty fork and tells you that we have no time to write the code during the class?

The one who shows you a shitty presentation with the same code he just sent you, just cut into 72 slides and at every slide tells something like this is pretty self explanatory, x just does y and if you ask a question he gives you that deep stare, like if you really mean it seriously to waste his time, since he really really wants to go to his office sooner so he can scratch his balls?

That type of professor who tells you that as a student of CS degree you are required to put some passion to your craft and study when you arrive at home and hes there just to give you guidelines, but apparently somehow forgotten that people usually need to sleep?

That same cunt who doesnt give a shit that you have 4 more projects to finish this week, doesnt push the deadline, nor give you advice, because you had opporturnity to ask the whole time?

But still that motherfucker, who gives you test questions that he took from mouth of Satan himself and then questions your answers like Where did you get that from?

Well fuck yall who do that shit, hope that you suffocate yourself while eating bread.

Why these douches doesnt understand, that even if we arent under the Working Laws, working more than 40 hours a week isnt the best way to keep us sane or motivated.

"You have to change your password, because you've either just registred or your password doesn't comply with our guidelines anymore."

I've not made my account recently.
The question beeing: How can they know if they "should" decently hash it? 👿

Devrant guidelines update:
1. Just because you can post something doesn't mean you should.
2. Everyone should be treated fairly and with respect.
3. We should be looking for positives in people and rewarding those.
4. Share your rants in a non-polarizing way to help bring the community together.
5. Don't post anything about the word made from the first letter of the first four guidelines.

Password guidelines...

Just got an online account for an insurance:
Allowed characters for password are a-z, A-Z, 0-9.
Really?
I tried special characters, maybe they just forgot to mention them. Doesn't work, "Password not valid".

Once upon a time google gave ui guidelines....

And then forgot about them 😂

Fucking outlook, can't even render simple html.

Our company wanted a custom newsletter to send to our clients. Before vacation I dropped a few guidelines to our designer, how our newsletter should look. 640px width, common fonts for everyone to render properly, stuff like that. To my fucking surprise they managed to create the most designed newsletter I've seen. Custom font, custom letter sizings, negative row gaps, pixel to pixel image locations. After writing custom html for it and managing to get all perfectly in 3 hours, to my surprise I found out, that outlook is broken. FML
Now everything must be redesigned and simplified, just because I was naive enough to think, that all mail clients manage to render simple HTML...

This is the best example of google giving a fuck about their own guidelines.

They always ram their expectations of you making your apps fit the guidelines a 100% into you, but then they give a fuck about heir guidelines in their own software.

They use a ListView here in google contacts. It's completely outdated for a large amount of data, such as my 200 contacts. They literally push you not to use outdated techniques such as ListViews in your app. Use RecyclerViews, our completely new solution instead. ListViews are very very bad in performance.

I KNOW THIS SOUNDS PICKY, BUT THIS IS JUST AN EXAMPLE!!! THEY DON'T CARE ABOUT THEIR OWN GUIDELINES IN EVRY WAY! BEST OTHER EXAMPLE IS GOOGLE PLAY STORE. BAD PERFORMANCE 100%. BUT AT LEAST IT HAS RUCKLING ANIMATIONS.

Here is a visual representation of Angular using NgRx

I think that its quite apt ....

I couldn't post the pic that i wanted to post because i'm sure that this site has some decency guidelines and i don't want to get kicked out

My thesis supervisors gave me a set of templates and guidelines for the whole thing and argh.

they constantly assume that I've no fucking idea about academic writing despite the very good graded talks and texts I handed in in the past - granted, they probably often deal with inexperienced students.

but what they've given me.. a) the thesis template does not work, they fucked up some latex packages and b) there's a almost passive aggressive 3 page explanation on academic writing and how wo work with sources and references and they forgot the fucking references lol. There are none included and the references all go like [?].

I'm not here to underestimate the design of a government app on Android.

I hope the developer considered the UI itself as user-friendly and not the default button from android studio. he just simply copies the contents(text & images) from the government web page and paste it to its application.

He/she got paid well to make that app. well, although the information is correct for the users.

It's not much that users are even enthusiastic of the design. they simply read the guidelines inside the app and no more fancy animation.

exactly two years back I joined my current company, it is spanish company and I speak only english. each document that was there in the welcome kit was in spanish, including design and architecture documents. also coding guidelines. it was a night mare as comments in the code were also in spanish. it took me three days to come to terms with reality.

The worst part of being a dev? Working in teams.

And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.

Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!

Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project!

Fuck the design guidelines that change every fucking day. It makes Front-End an unbearable hell. I'm seriously tired of having to code stupid shit for exceptions exceptions exceptions.

Writing a feature critical for production in 2 hours of solid focus during the morning.

6 hours later it's still not in the build because:
* tech lead wants the code to move to a partial class instead of an extension method, delaying the UX review. No guidelines for this ever existed.

* after seeing the result, the UX team wants some element to be dynamic. A line. A friggin horizontal line.

* after adding the dynamic shiny frigggggin line, I try to test the feature with the server. It is still not deployed because the server guy went home. "The PR was not merged so I assumed we'll add it tomorrow".

Another day at the meat grinder.

For a long time I was of the opinion that pointer variables in C/C++ should have the asterisk immediately after the type name (e.g. int* foo).

Eventually I became convinced that it makes more sense to have it before the variable (e.g. int *foo).

Now I find routines that return pointers look weird, e.g.: void *allocate_something() so I am considering adopting the original style I used.

The only advantage of having the asterisk before the variable name I am aware of is that it is easier to remember to add an asterisk if you define more than one pointer on that line.

Anyone else find it hard to settle on code style guidelines for their own personal projects?

-- Best --
> Submitted my notice of termination for my current job
> Found a new job starting next year
> Can switch from Windows to Linux/MacOS in new job
> Got more time to work on personal projects due to the pandemic

-- Worst --
> Huge amount of software restrictions (current job) almost got several projects at work canceled. Maybe its important to say that the core business of my current workplace is auditing so there are a lot of law regulations which then apply in the softwaredevelopment process.
> New managers that do not have the slightest clue of what they're doing
> Online Teambuilding events
> Absurd amount of segmentation of tools and also different coding guidelines that are used at work. E.g. one team uses jira, another trello, another github issue tracker and so on.

Does anyone else question their career in programming from time to time?

I've been around this line of work for almost 7 years now and I still get these doubts once or twice a year.
Be it unreasonable deadlines, horrible people that I'm forced to work with or just outright incompetence.

My latest occurence of doubt was when getting assigned a task that initially didn't seem like a big deal, but it turned out to be months and months of custom work instead of going along with the standard components and design guidelines.

This was somehow missed in the estimate phase and once I got assigned to it a hard deadline was already set, to top it off the features was non-negotiable.

These kind of things really makes me feel helpless and really depressed. My work is all I have, and I don't really know what I would do if I'd change career path today.

I clearly don't understand how StackOverflow works. I posted a solution I came up with in a Q&A style, thinking it's a way for me to contribute to the community.

When I researched the challenge I needed to solve, I didn't find any elegant solutions that would have helped me achieve what I was aiming for.

One commentator said my post wasn't a real question about a real coding challenge, and wasn't compliant with SO guidelines.

Another commented that my search provider was clearly inadequate.

My submission was voted down so I just removed it with the intention of sharing it elsewhere.

It's almost as if StackOverflow resists contributions from newer users. Or, as I suggested at the outset, I clearly don't understand how to be a productive member of that community.

Fuck it, fucking fuck it.

Consulting company, been here for 2 years, had some decent projects (surprise, only those that me and my coworker started from scratch), but OMG the fuck ton amount of bizarre code I've seen is just mindblowing.

Everytime I start on a project, spend days improductive because the stack won't fucking work.

We use some frameworks, but the creators of the projects said fuck it, why would we follow the framework guidelines if I can create a supersmart way that nobody fucking understands way of doing things. I mean, It will look smarter and so nobody else can touch this shitty code.

I hate that the most praised developer is the guy that created most of this shit, and his nº 1 skill is moving Jira tickets to the correct state, tracking time (PM's love this, I hate it) and blocking my fucking merge requests because I left an extra blank line, dangling comma or whatever the fuck else, he's like a human linter.

Dude, the code is a piece of shit, my dangling comma is not going to be the problem! And if you really care that much, setup a linter or something.

Fuck this, I'm quitting this week.

Clean Code book has some good guidelines but sometimes becomes too fanatical for my taste. For example, comments in good doses are really good.

And people sho accept it as Gospel are making a mistake.

Something which is becoming a big pet bug peeve of mine... Chat bots being classed as AI...

Seriously?? Gives a response of context 2 or 3 levels deep?

Saw a news bulletin of a guy being questioned on the guidelines of putting AI in an app which builds quiz questions from Wikipedia - look out world, the robots know a lot of history!

The Google engineers building proper AI would be wetting themselves...

Hey fellas,

So, our company is taking up some consulting projects to survive this pandemic since our main business is a little down. I've been assigned to a RN project and the client company has 2 other devs. Those devs are so incompetent that they don't even know the basics of JS and RN. They don't even understand how to split code into components and make it resusable. Okay, fine they must be new devs. I get it but can't you even fucking follow the instructions and guidelines that I'm giving you!! The code is very bad with a lot of pitfalls. In the first 2 weeks I reviewed all the code they were writing and gave comments for improvements. They didn't even care to do that! Now I've given up!

Every single day looking at the codebase makes me sick and not want to touch anything. I've practically started hating the project. How do I deal with this situation? Now, we are reaching the deadline and they're piling up the work on me. Any suggestions on how to handle this?

Thanks!

P.S: This is my first actual rant!

@dfox Read about the latest update. Excited for the changes as well as the secret feature coming in the next few weeks. Also thank you for the community guidelines. Much appreciated. Have an awesome weekend.

"We have updated our ... "
Well, guess what, nobody gives a fuck!
#noFucksGiven

Put monetization on DevRant's rants and watch the downvote button disappear and comments getting the "Community Guidelines" tag.

Finnaly found some documentation and guidelines for creating Ubuntu suru icons, this took way too long to find!

Oh well, at least I can finnaly start working on some icon sets for my apps! :-D

So it's been a week since I left this company, but I still have access to all resources and stuff. I worked there on a project for 2 years, and in a week they managed to fuck up the codebase, because why follow guidelines I set up.

Ugh, hard to let go sometimes. But I know Im better of at this new job.

Now I also experienced the corporate IT - hell.
I'm an apprentice at a small but branch of a fairly big company.
We get a fuckton of guidelines from our IT-HQ, plenty of them outdated.
We can't even decide how to configure our firewalls our self, but get them preconfigured from the HQ.
They micromanage us so hard, we can't even put a switch in a room, without having to arrange that shit with them.

Fucking hate it when I have to ask someone to clean the DB of an app am working on, ON STAGING environment!! 😖

Give me the fucking access will you!!

How the fuck am I supposed to fucking keep working if these fucking clowns add mandatory peer code review and passing build gating on main repositories (which I completely agree with to be fair) but they don't fucking review pull requests at all? For fuck's sake, am I the only one that reviews them seriously and promptly in this shit ass fuck company? I follow all the recommended guidelines so don't bullshit me with "iT iS nOt FuN tO rEvIeW pUlL rEqUeStS", do your job or just remove yourself from the fucking gating process, you worthless admin ass crust.

And don't get me started on fucking builds that fail randomly because some worthless shit bucket added unstable networking tests as unittests somehow, making your pull request get auto-disapproved by peers upon failure.

I got so many pending pull requests and management won't do fuck all about it because they won't force people to do their job by fear of pushing them around and get HR complaints that I am tempted to simply give up and just start playing videogames.

"Oh yeah I made a new endpoint, and I just pushed the logic for it wherever I wanted without following any of the project's guidelines or structure. I didn't write any tests or documented it anywhere either. I kinda felt there was already an endpoint for it (there was) but I couldn't be assed looking for it in the documentation"
Die.

How much mind raped are you if you're asked to develop an iOS app completely with material design even after you inform that it's against iOS guidelines?

I’m working on a react codebase and company decided to add a new module.
Now im writing markup and css to ensure UX is smooth as designers thought of it.
Imagine my horror when I start to code and find out no matter what HTML tag i use, it’s been FUCKING OVERRIDDEN in the global stylesheet. AND STYLES HAVE BEEN OVERRIDDEN WITH !important

They’re also using Ant design as a component library. Guess what, default ant design classes have been overridden too. So i try to use ant design button or card, and bam, MAGICALLY SOME DESIGN FROM SOME SHITHOLE MODULE DECIDES TO FUCK WITH MY STYLES

On top of that, styles of parts of application has been written in SASS, some part of application uses bootstrap components some use third party components like tables and responsive grids to suit to their preferences. Some parts use handwritten css. Some parts use CSS IN JS and styled components. THE FUCK IS THIS GARBAGE!!!! THE FUCKING CODEBASE HAS A MIND OF ITS OWN!!!!!! YOU NAME A WAY TO ADD STYLES TO A COMPONENT, ITS THERE!!!
And the company’s management thought a “fractal” approach to maintain each individual view is “best” for SCALABILITY!!! HOW THE FUCK DID IT NOT CROSS YOUR DUMB MIND THAT FRACTAL APPROACH ALSO GUIDES TO HAVE ALL COMMON STUFF AT ONE PLACE!!!! THIS CODEBASE HAS DUPLICATE STYLES AND DUPLICATE CODE IN ALMOST EVERY MODULE!!!!

Not to mention every developer choosing to freely decide the way they should write their code without any guidelines.

HOW THE FUCK PEOPLE WRITE THEIR CODE WITHOUT THINKING ABOUT OTHER DEVS!!! SO BASICALLY I AM NOT ONLY CLEANING SOMEONE ELSE’S SHIT BUT ALSO TRY NOT TO SHIT IN THE PROCESS!! FML

This huge OS project, Magento, have TONS of guidelines, most about decoupling,, it has an extended MVC structure with even more layers than those 3.. All good in theory, guess what.. Guidelines is not followed..
Changing order of two blocks in the view breaks business logic.. So much for decoupling.. You would not believe how many hours I've spent debugging this..

And I can't believe I've dedicated 12 years of my professional live to this platform..

!rant
I really like the Material Design guidelines that Google has released with Android 5.0, and maybe, @dfox, you could make the status bar match a darker tint of the app's color, as this color is also used on the recents menu and on my keyboard, and it really (IMO) makes an app stand out.
Thanks!

I bought BMW recently and the engineers who designed it did a phenomenal job. The one oddity though, there are up and down arrows on the steering wheel representing next and previous, except that down is next and up is previous. It's so counter intuitive and I wish they would standardize button interfaces or produce guidelines everyone would stick to.

So, in C#, are there any tips or guidelines as to how to write "clean" multiline strings? I mean, imo it doesn't look as neat when the code looks like:

static string kindOfLongVariableName = @"First line of string.
Second line of string...";

With the first line sort of hovering on the side. What I'm used to is with Python where you can just:

variable_name = """'\
First line.
Second line.
"""

And use the '\' to escape the newline, but that obviously doesn't work in C#. Can anyone point me in a direction to start looking? The docs are a bit confusing and not very beginner friendly. :/

My last week of 2017 sucks! The function that been assigned to me has been 7 months until i doing it without any priority tasks. The bad for this, is becoming worse for the clients and they really want it until the end of 2017, so happy new year motherfuckers.

Here's the story, the function i am doing requires a heavy calculations, and i am no brainer in math, though my logical skills, hopes me up to made it quickly as possible. However i am full of workloads/to-do for the past 3 months, that i am unable to comply my documents regarding my employment!!

Much worse for this is the coding guidelines. There no fucking guidelines at all, like do what i want just to make it work, but my team lead ironically speaking that never touch that because it's already working. Dude, the server response was the real issue there and i was supposed to handle that function because your fucking json was not formatted well! Shout out to git for giving me a saving grace not to fire me.

Lastly, the leader's attitude. You're so sarcastic as fuck! Of course i won't get mad at you on personal matters, i understand. But on work, the way you communicate was not like my any mentor/prof that i ever met!! I hate my fucking work. Hope my 2018 would do my best, AND I AM GONNA MAKE MY OWN GUIDELINES ACCORDING TO YOUR ASSES!! HAPPY NEW YEAR, GODDAMNIT!!

When your IT VP starts speaking blasphemy:

"Team,
We all know what’s going on with the API. Next week we may see 6x order volumes.

We need to do everything possible to minimize the load on our prod database server.

Here are some guidelines we’re implementing immediately:

· I’m revoking most direct production SQL access. (even read only). You should be running analysis queries and data pulls out of the replication server anyway.
· No User Management activities are allowed between 9AM and 9PM EST. If you’re going to run a large amount of updates, please coordinate with a DBA to have someone monitoring.
· No checklist setup/maintenance activities are allowed at all. If this causes business impact please let me know.
· If you see are doing anything in [App Name] that’s running long, kill it and get a DBA involved.

Please keep the communication level high and stay vigilant in protecting our prod environment!"

RIP most of what I do at work.

Developing nanosatellite to be launched with foreign company.
The ICD (Interface Control Document, basically guidelines regarding design) is clear, but there are some key points we needed to ask with the launcher.

I've sent email to ask them regarding those questions

Then got a reply saying that it'll be forwarded to the engineering team.

That's it. 2 weeks in, no reply. Tried emailing them again to nudge them, no reply, resent the email the following week.
Still waiting till today.

Please reply me 😂😂😂

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

Someone raised a PR for the opensource project "fast XML parser". Since this was a major change, it was difficult to review. I asked for the purpose and requested to break it into multiple PRs, where 1 PR should have related changes only. And any good change but unnecessary change can be avoided to scheduled for later.

We had long arguments for a month or two.

I don't know why but instead of breaking the PR, the contributor keep updating his PR for every commit someone made on the original repo.

He also stopped contributing for other changes, and commenting on other issues. (Change in the behavior)

Finally after 5-6 months, I had to close the PR as it was not active, having conflicts and not as per guidelines.

Fuck antiviruses making your PC so slow that you cannot work. Need to find a way to disable it, fuck security guidelines.

It usually starts with a project, a CI pipeline, unit tests, deployment guidelines, and wait - oh crap - what am I building again?

I finally got the lstm to a training and validation loss of < 0.05 for predicting the digits of a semiprime's factors.

I used selu activation with lecun normal initialization on a dense decoder, and compiled the model with Adam as the optimizer using mean squared error.

Selu is self-normalizing, meaning it tends to mean 0 and preserves a standard deviation of one, so it eliminates the exploding/vanishing gradient problem. And I can get away with this specifically because selu *only* works on dense layers.

I chose Adam, even though this isn't a spare problem, because Adam excels on noisy problems and non-stationary objectives (definitely this), and because adam typically doesn't require a lot of hyperparameter tuning its ideal here, especially considering because I don't know what the hyperparameters should be to begin with.

I did work out some general guidelines on training quantity vs validation, etc.
The initial set wasn't huge or anything, roughly 110k pairs for training.

It converged pretty quick all things considered, and to the low loss like I mentioned, but even then the system always outputs the same result, regardless of the input, so obviously I'm doing something incorrectly.

The effectiveness of this approach for training and validation makes me question if I haven't got something wildly wrong. Still exploring though and figuring out how to get my answers back out. I'm hoping I just fucked up the output, and not the input as well.

Stop shitting on my codes sir :(

I know I didn't give you strict guidelines but pleeeeeease do not code it this poorly. These are obvious mistakes....

People in companies who make bad git commit messages beacuse they do not care... Hey, "change 1", "update" makes so much sense. And companies who do not care to have some guidelines.

Ok so my thoughts on M$ officially buying github:

Honestly idk, it’s really up to them. I hope they think it really independent because otherwise they could abuse of the power they have over devs. So no added bonuses or free Azure if you develop for uwp or that kind of shit.

But it could also help GH get even better and include more the devs and all that stuff.

Lately, M$ has been becoming a little less evil and maybe they have a little of good will. What I think we need is a motto and clear guidelines for the development of gh. A community focused openness about development.

Anyway, I’m super tired and I should be sleeping, but I’m a dev and I don’t care.

has anyone here done a proper refactoring? i mean, documenting, following some rules, etc.

i need to know the process and guidelines for refactoring, what & how to document, where to start, etc.

i am assigned to a project for a short term and my job is to do refactoring of Reactjs code. and i need to do it in a really good way.

any help would be highly appreciated.
thank you.

Let's agree on something :when asking your coworker for help, follow stack overflows guidelines, and we will all be happy. No one should guess about a certain linq that failed to filter with a "It's not working".

Sometimes I feel that as we have some rules and accessibility guidelines for 18+ when they visit any website, play a game etc., we should also think about 60+ who are not technology friendly. I've explained to many elders why they should not share their personal information on public forums like facebook or twitter, or why should they not reply a spam mail.... but :(

Had a Long discussion with stake owners and PM. Ended in despair over corporate guidelines and impossible demands from the board / CEO.
PM finally said: Fuckit, let's get a beer, i'm buying.
Best day so far this week.

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 place

Long time no rant...
Just fuck apple.
I’m working in partnership with an startup as iOS dev.
We have payments in our app since it was released couple years ago. And everything was ok. Two months ago we implemented a subscription based program that granted our user access to a few things that we need to process manually. I specified that because in apple’s guidelines states that services consumed outside app are not allowed to be sold using inapp purchase and you have to implement your own payment method.
All nice and good we used what we had already in place and the updated was approved. Same for the next 6 versions. Now we discovered a quite critical bug and fixed and submitted a new update just so apple would reject it because we are using subscription that is not implemented using their fucking store kit. So they can’t get those 30% share cut.
Fuck them fuck their echo system fuck their overpriced product. I’v just abandoned my 15” mbp mid2015 in favor of a hackintosh just because my mbp was dying from high temps. Fuck it i’m almost done with mobile development after 6 years

For fucks sake newbies, please read the guidelines of the mailing list before mindlessly sending your BS to everyone!!! Ffffs!!

All app/web layout designers, I need your help with layouts for my app. I am struggling with a very specific thing: image sizes. What are the general guidelines for touch devices and windowed programs? Should I eyeball the max width and height? What if it's on desktop and I am making the window larger / smaller?

Any help is absolutely appreciated, I had perfect success in all of what I worked on in the app until now except this. I just can't get it right.

A question on corporate reality, let me know which person is doing it right :

Person A is a young enthusiastic nd curious fresher who has joined an amazing company where there is a team of seniors above him.
They ask him to work on a project, give him some guidelines which he is able to quickly grasp and come back with an output (because he loves learning and working on it and challenges himself to do it quicker than before)

This goes on and on, the new guy is giving his 100%, but company realizes it and starts expecting more of him, his 100% is not satisfactory enough, he is expected to give his 110% . He is now feeling the pressure but still liking it (because he likes learning) even though it has started to effect his personal lifestyle. He no longer has time for friends and even codes during his nap times, but still believes that he's in his prime and its okay for him to grind wheels for a better future

-------------

Person B is a lazy ass half hearted fresher who's good with public relations. He knows he can do a work in 1 hour, but still does it in 2 hours and do it bad.
He is giving his 50% and seniors know it but still are expecting to get just 70-80% out of him because of his charming and cool personna.
He's cool, now dating office girls, actively partying and is now people's favorite and living a lavish life with equal salary as that of the person A.

Who is living their youth correctly?

You can talk for a lifetime of improvement, but what can you do when your boss sits near you and dictates his changes to the app you're working on?

Don't forget, this changes are on the opposite place of good common sense, interface guidelines (iOS and material) and TASTE.

HTML Writers Guidelines

When designing your web site you want to make the visiting experience as enjoyable as possible and at the same time make it so that if the site needs to be changed in any way, the changes are not too difficult to make. You want the look to be as appealing as possible for all browsers and also make the site accessible to users with disabilities. In order to accomplish all this there are some general guidelines when creating your HTML code.

1. The first thing that will really make your life easier is through the use of Cascading Style Sheets (CSS) - CSS is used to maintain the look of the document such as the fonts, margins and color. HTML directly on the page is not a good choice to handle these aspects because if say, the font color you are using for certain paragraphs needs to be changed from blue to red, you would have to go in and change each color tag manually. By using CSS you can designate the color for each of those paragraphs just once in the CSS file. That way if you have to change the font color from blue to red you make one change instead of the countless number of changes you might have to make, especially if your web site contains hundreds of pages. This is a big time saver and a must for all professionally designed web sites.

2. Don't use the FONT tag directly in your HTML code - This becomes a problem when using some cheap authoring tools that try to mimic what a web page should look like by using excessive FONT tags and nbsp characters. These tools end up creating web pages that are impossible to keep maintained. There is a program you can use, if you've created one of these disaster pages, called the HTML Tidy Program which you can actually download here . This will clean up your code as well as possible.

3. You want your web pages readable to people who have disabilities - People who surf the Internet depend on speech synthesizers or Braille readers to interpret the text on the page. If your HTML markup is sloppy or isn't contained in CSS the software these people use to read pages have a difficult time in interpreting these pages. You should also include descriptions for each image on your page. Also, don't use server side image maps. If you are using tables you should include a summary of the table's structure and also associate table data with the correct headers. This gives non visual browsers a chance to follow the page as they go from one cell to another. And finally, for forms, make sure you include labels for form fields.

By following just these three guidelines you give your visitors, especially disabled visitors the best chance of having an enjoyable visit to your site while at the same time making it so that if you have to make changes to your site, those changes can be made easily and quickly.

I've been hearing about material design, and wanted to check up on it. Does it specify some good UI guidelines, or is it more JavaScript framework hipe?

Their website didn't load on my browser. I guess I know what it is now

include ::rant
rant::newentry {'new-job-rant' :
ensure => latest,
location => goverment-employment-office-HQ,
job => DevOps,
content => {'
So, i've been at my new job for some time now, almost two weeks (hurray!) but boy oh boy, what a job it is!
I'm working at a goverment office charged with helping the unemployed to get a job or a new education course. I'm hored as re-enforcements for their DevOps team. I get my pay, easy transportation home<->office, coffe is adequate in quality and quantity, so no complaints there...

But the actual job is a FUCKING MENTAL CLUSTERFUCKS OF WHAT THE ACTUAL FUCK MULTIPLIED BY TEN TO THE POWER OF GOOGOL!

A few items that make my blood boil to new temperature records defying medical science:

* devs refuse to use linting, say the builder will catch it when there is an error, never look at the builder error logs
* (puppet) modules have NO TESTS
* (puppet) modules get included in several git repo's as submodules, in turn they are part of a git repo, in turn they are replicated to several puppet masters, and they differentiate the environment by bash scripts... R10K or code manager? never heard of it.
* Me cleaning up code, commit, gets accepted, some douchebag checks out code, reverts it back to the point where linting tools generate 50+ lines of warnings, complains to ME his code doesnt work! (Seriously, bitch? Serously?) , explain to that person what linting does, that persons hears the bells ring on the other end of the galaxy, refuses to use it.
* Deployment day arrives (today) -> tasks are set up on an excel sheet (on google docs) , totally out of sync with what really must be done -> something breaks, spend 30 minutes finding out who is to blame, the whole deploy train stops, find out it's a syntax error, ... waiting for person to change that since that person can only access it...
...

the list goes on and on and on. And did you expect to ahve any docs or guidelines? NO , as if docs are something for the luxurious and leisurely people having "time" to write it...

I can use another coffee... hopefully i wake up from this nightmare at my 15th cup...
},
require => [Class['::coffee'], Class['::auxiliary_brain'], Class['::brain_unfuck_tools'],],
}

First pull request to an open source project :D

Well, a small project, without contribution guidelines.

I am the only front end developer in my team, used to be 2, and there is 4 java backend dev. We are all Seniors, so you'd expect to be experienced. I like my code to be "nice" and I am using linting tools, rules, formatting etc... (I do JS mainly).

During a scrum review some of the java guys showed some code on the screen and that thing was a monstrosity for me! I could not look at some code like that, if I had to work with that I'd probably hang myself. Nothing was aligned, no consistency. So my question: you guys aren't using any guidelines to have cleaner code ? How do you make sure you all code the same ?

...

What are you taking about ? We use Eclipse, with default options, no tools no guidelines...

App Store Submission Guidelines: „(and turn on your back-end service!)“

A question to game devs : which design/architecture patterns do you use ?

Everytime I try to take a look at game development, I feel like there is a lack of guidelines, mostly about architecture.

It's something strange to me as a web dev, as we use much of these patterns on a daily basis. Of course I think about the near omnipresence of MVC and its variants, but not just that. Most of frameworks we do use are essentially focused on architecture, and we litterally have access to unlimited tutorials and resources about how to structure code depending on projects types ans needs.

Let's say I want to code a 2D RPG. This has been done millions of time across the world now. So I assume there should be guidelines and patterns about how to structure your code basis and how to achieve practical use-cases (like the best way to manage hero experience for example, or how to code a turn-based battle system). However I feel these are much harder to find and identify than the equivalent guidelines in the web dev world.

And the old-school RPG case is just an example. I feel the same about puzzle games or 3D games... Sure there are some frameworks and tools but they seems to focus more on physics engine and graphic features than code architecture. There are many tutorials too, but they are actually reinforcing my feeling : like if every game developer (at least every game company) has his on guidelines and methods and doesn't share much.

So... Am I wrong ? Hope to.

What are the tools and patterns you can reuse on many projects ? Where can I find proper game architectures guidelines that reached consensus ?

!!rant

Why the fuck would you bother creating a style guide if you don't adhere to it even a bit in creating mockups?!

Sure as hell I can code what you want, but you gotta stick to the agreed guidelines, dude! We can't keep adding *slightly different* elements, it'll lose its purpose!

I get that this was a small team when they developed this and there was no coding guidelines...
But, using spaces and tabs in the same file is just unacceptable!!

Wtf!? Clowns wants to, again, move me up the ladder. They don’t care. I am starting to think they have an evil plan for me in play here. Step 1) promote so high that noone really knows what the fuck I am doing. I am just name on a paper. And in the meetings. And then, 2) fire my ass

Have not accepted this job position. Yet. But I’ll guess I’ll take it. I can always go back to coding. Haven’t coded for a year now!

I think there must be some sort of evil play here. Am I that incompetent?

Do I want to be Chief Supreme Structural Architect Commander? Wtf!? Clowns…

All bow for the Chief Supreme Structural Architect Commander! I got principles and guidelines! Pff…

So I desperatly want to engage into C lang. yet I can find clear guidelines for OSX IDE or common C scaffolding. Any help ?

Suppose you wrote a library for some purpose in a language. How do you get other devs to use it? How does it become known among the devs, assuming it follows proper language guidelines and fulfills it's purpose?

Have any of you tried cloning NFC cards? I really want to try it out. Any advice or guidelines would be much appreciated.

At starting of my professional career I was part of an android project for a big credit card company. I used love the UI and colors in it. With all the tablets and phones around, people used to see me like a geek 😀

But UI guidelines and UX of that project, never got such extensive guidelines again. It used to make the development so easy.

iOS/native app devs!

How usual it is for your apps to differ from iOS UI guidelines? Our lead dev always throws a fit when he has to implement custom stuff, but I see popular games “shit all over” these guidelines all the time and do very well in popularity.

As I’m no expert, please tell me if it is generally accepted to not follow these iOS rules / use premade controls 100% of the time, so I know what’s up. Thank you.

Hi! It's my first time working as a professional developer and I am the team lead. Where can I find a a set of programming guidelines which we can edit a bit according to our needs and follow so there is consistency?
We are using python.

God damn...if you want to be a developer learn using git and fucking STOP messing up the repo every time you push something.

Understand the importance of branches and use 'em so the problems you're causing are isolated and stop commiting / pushing on master....ITS NOT THAT HARD TO READ THE FUCKING CONTRIBUTION GUIDELINES!!!

Had the most awkward day where I had to usability test with random people around the office and I took so much time and it was so awkward asking people to test your designs cause I suck at approaching people.
Why am I a UX engineer and when is confidence gonna grace its presence cause I was a stuttering mess :(

I started to write an API for our application and asked everybody to use it.
Everybody liked the idea, but nobody liked the API.

So now we have api/v1, api/dev1, api/dev2, api/dev3 to do the same fucking operations.

When I complained about them not respecting the guidelines, dev1,2,3 told me it's my fault because I'm the director.

I thought for a while about how to get rid of these apis and I finally agreed with their view.

I removed developer 1,2 and 3 and finally now there is only api/v1

Which syntax is "correct" TypeScript syntax ?. I prefer the first one. But what's about guidelines ?

Note for UpperCase variables: yes I know. We use that syntax to differentiate public and private variables. (Yes I know that doesn’t exist in JavaScript)

I am planning to create a broadcasting channel app.
there is a group of people who are managing 20-25 whatsapp groups and are sending religious messages.
They tried broadcasting feature of whatsapp but they prefer managing group which makes sure that people are receiving messages.
broadcaster's number needs to be saved in receivers contacts for whatsapp broadcasting and all subscribers were not doing so, and complaining about not receiving messages.

so this group decided to manages whatsapp groups and put guidelines that no users other than admins are allowed to post anything.

so ultimately they want a broadcasting medium.

another problem here is that it is hard to find old messages to refer to. they are posting everything on blog too, but not all the subscribers are comfortable using that.

so I am planning to create an app which will store the received messages offline(last 30 days) and anyone can read older messages within the app and also can share it on other social media.

would you guys please suggest me architecture for this app?
I have learned PHP and thinking about using phalcon PHP framework, but it required VPS and it is costly.

any suggestions welcomed.

I’m a full stack developer, working with React. Also before this I used to be an OK hobby artist (for sketching and painting, that is), but man I SUCK at designing websites!! I don’t have that designer’s mind at all. At work that’s not an issue because we have guidelines and such, but when I’m doing free time projects it always looks so ugly and amateurish.

How can I improve, should I take some graphic design course, or is there some specific buzz word for graphic design on the web that I should look out for? How can I learn standards of margins, buttons, text and such in a good way. Some people just seem to have it in them already!

Any advice or thoughts would be appreciated!

Do not know how to execute Roku com link activation steps? Here we explain the guidelines in detail. Select your device and connect the necessary cables. Create a Roku account, log in. Search to find the Roku activation code. Type the code navigating to the page, Roku com link

Is self advertisement against the rules here on devrant? I wouldn't spam devrant with it, of course. I just happen to have developed a script a while back which some people might find useful. I took a look at devrant's rules and it says nothing about this, but I just wanted your guys opinion. Is this frowned upon here?

Wanted to discuss about this AMP framework by Google. I have developed with it for my company and have been having mixed feelings about it.

On one end, it gives you the power of Google cache, declarative layout and all.
But still, it seems to be too restrictive and filled with bizarre rules that often could have been avoided if they just made guidelines for normal "web pages" to be better and not yet another framework to build "AMP pages".

One more (and probably the biggest) thing. AMP is Open Source... But can it be really considered Open if the biggest player in its development is a single corporation?

Can an app built with Cordova, designed without following Apple's Human Interface Guidelines (so basically a responsive website), be published on the App Store?

"People always ask, 'What do you think of my site?' I want to say back to them, 'Who cares what I think. Does it meet your site requirements? Has it been tested? Has each requirement been validated? Are your site guidelines being adhered to?'" - Kim Krause