I was reviewing one dev's work. It was in PHP. He used MD5 for password hashing. I told him to use to password_hash function as MD5 is not secure...

He said no we can't get a password from MD5 hashed string. It's one way hashing...

So I asked him to take couple of passwords from the users table and try to decode those in any online MD5 decoder and call me after that if he still thinks MD5 is secure.

I have not got any call from him since.

Let's get rid of the developer training: Pair Programming

Let's get rid of the software testers: Test First Programming

Let's get rid of the project managers: Agile

Let's get rid of the project planners: Scrum

Let's get rid of the system admins: DevOps

Let's get rid of the security guys: DevOpsSec

Let's get rid of the hardware budget: Bring Your Own Device

Let's get rid of the servers: Cloud Computing

Let's get rid of the other scruffy guys: Outsourcing

Let's get rid of the office space: Home Office

Let's get rid of the whole fucking company: Takeover

Guy: I don't trust password managers
Me: so how do you remember passwords?
Guy: oh, I just keep them in a note in the iPhone notes app/iCloud.

Why not have a custom (500 line) JSON mapper... you know... fuck those auto mapping libraries out there...

*my first day on the job to work on a website used by dozens of companies worldwide and 1000s of users*

me: So where can I find the git repository?
dev: Git?
me: Uh... what kind of source control do you use?
dev: We don't use anything fancy like that.
me: *freaking out a little, I already committed to this job*
me: So then where do you edit your code and how do you back it up?
dev: Oh, I just edit it on FTP and zip all the code every week.

If I had a dollar every time a non software engineer used the word "just" in a sentence...

"Just" convert this Matlab code to C++

"Just" make it faster

"Just" have it done in a week

security practices...

My employer is now under investigation by the government for illegal business practices. #blessed

This cuts deep

$ git push --force origin master

Starting a new project

Me: This time we'll follow all the best practices, do atomic commits and write meaningful commit messages.

Coworker: Yeah! Let's start.

40 commits later.

Me: Why is .idea folder in the repository?

Coworker: Sorry My Bad.

Me: 👿👿👿👿

This codebase reminds me of a large, rotting, barely-alive dromedary. Parts of it function quite well, but large swaths of it are necrotic, foul-smelling, and even rotted away. Were it healthy, it would still exude a terrible stench, and its temperament would easily match: If you managed to get near enough, it would spit and try to bite you.

Swaths of code are commented out -- entire classes simply don't exist anymore, and the ghosts of several-year-old methods still linger. Despite this, large and deprecated (yet uncommented) sections of the application depend on those undefined classes/methods. Navigating the codebase is akin to walking through a minefield: if you reference the wrong method on the wrong object... fatal exception. And being very new to this project, I have no idea what's live and what isn't.

The naming scheme doesn't help, either: it's impossible to know what's still functional without asking because nothing's marked. Instead, I've been working backwards from multiple points to try to find code paths between objects/events. I'm rarely successful.

Not only can I not tell what's live code and what's interactive death, the code itself is messy and awful. Don't get me wrong: it's solid. There's virtually no way to break it. But trying to understand it ... I feel like I'm looking at a huge, sprawling MC Escher landscape through a microscope. (No exaggeration: a magnifying glass would show a larger view that included paradoxes / dubious structures, and these are not readily apparent to me.)

It's also rife with bad practices. Terrible naming choices consisting of arbitrarily-placed acronyms, bad word choices, and simply inconsistent naming (hash vs hsh vs hs vs h). The indentation is a mix of spaces and tabs. There's magic numbers galore, and variable re-use -- not just local scope, but public methods on objects as well. I've also seen countless assignments within conditionals, and these are apparently intentional! The reasoning: to ensure the code only runs with non-falsey values. While that would indeed work, an early return/next is much clearer, and reduces indentation. It's just. reading through this makes me cringe or literally throw my hands up in frustration and exasperation.

Honestly though, I know why the code is so terrible, and I understand:

The architect/sole dev was new to coding -- I have 5-7 times his current experience -- and the project scope expanded significantly and extremely quickly, and also broke all of its foundation rules. Non-developers also dictated architecture, creating further mess. It's the stuff of nightmares. Looking at what he was able to accomplish, though, I'm impressed. Horrified at the details, but impressed with the whole.

This project is the epitome of "I wrote it quickly and just made it work."

Fortunately, he and I both agree that a rewrite is in order. but at 76k lines (without styling or configuration), it's quite the undertaking.

------

Amusing: after running the codebase through `wc`, it apparently sums to half the word count of "War and Peace"

When you gotta work on a project you made a year ago and see the bad practices you use to have...

I fucking hate subscription services that start with a free month but still require you to input your credit card information.

"It's just so we can bill you for the following month! You can still cancel the subscription before the following date to not be billed anything."

No, there's no reason why you can't offer a free month WITHOUT having my credit card information. The REAL reason is because you're hoping I'll forget to cancel. Fucking predatory bullshit.

I just can't understand what will lead an so called Software Company, that provides for my local government by the way, to use an cloud sever (AWS ec2 instance) like it were an bare metal machine.

They have it working, non-stop, for over 4 years or so. Just one instance. Running MySQL, PostgreSQL, Apache, PHP and an f* Tomcat server with no less than 10 HUGE apps deployed. I just can't believe this instance is still up.

By the way, they don't do backups, most of the data is on the ephemeral storage, they use just one private key for every dev, no CI, no testing. Deployment are nightmares using scp to upload the .war...

But still, they are running several several apps for things like registering citizen complaints that comes in by hot lines. The system is incredibly slow as they use just hibernate without query optimizations to lookup and search things (n+1 query problems).

They didn't even bother to get a proper domain. They use an IP address and expose the port for tomcat directly. No reverse proxy here! (No ssl too)

I've been out of this company for two years now, it was my first work as a developer, but they needed help for an app that I worked on during my time there. I was really surprised to see that everything still the same. Even the old private key that they emailed me (?!?!?!?!) back then still worked. All the passwords still the same too.

I have some good rants from the time I was there, and about the general level of the developers in my region. But I'll leave them for later!

Is it just me or this whole shit is crazy af?

What bad practices (regarding software development) you are aware but can't get rid of?

Does anyone know if there's a Bob Ross of development?

I feel like I just need to hear someone coding or talking best practices in a chilled out relaxing way to help me through the day.

Too week 😋

Dear LinkedIn,

Try training your AI model without using captured data of real recruiters and their dodgy practices.

Anyone ever entered a password and it keeps saying wrong password, so you decide to reset the fucking password and now the problem is ....the systems/website tells you that you can't reset the password to your current password or a password you are already using... like okay what the fuck!!!!!.....

Remember to use good coding practices

Most jobs are shit. Find a place where you like your coworkers and development practices. Most other things are secondary to your mental well-being.

You know what's more irritating than working with a partner who doesn't understand how to properly build an API?

Working with one who fully understands the best practices but doesn't give a shit to implement them until something breaks.

Finally graduated only to realize that my degree did not provide hard skills, only outdated practices and student loans.

Philosophy 🤣🤣
Credits: commitstrip.

Which one do you use?

So my boss booked me a spot at a conference about "the future of online payments" and I received an email with auto created account (there was no sign up) with a clear text password.

I'm feeling pretty confident that I can trust them to guide and advise me on best practices when it comes to handling sensitive information.

"I know, I'll set my password as '12345'. No one will guess it because it's too simple right? RIGHT?"

Just received a mail from my college that my college's student account password does not contain any special characters and I should change it immediately. Wtf? How did they know that?

The good Java practices...

My code is always a battle between best practices and what I assume would be the most efficient way to do things

PHP Best Practices

yeah, i use the best security practices

Half convinced universities are paid off by virus developers to teach their students the most shit and insecure practices available.

former boss wrote three cyber-defense books. had his "collections" team sending plaintext passwords to high-side clients over unsecured email

Sometimes dirty code is more efficient than clean code.

If features get dropped frequently and requirements change every few days, writing best-practices, tested code is wasted time. Learned that in my first job where I thought the other devs were all bad. Until I realized their bad code pays my salary, and my clean code takes more time to develop.

Had a job interview for a front end dev (Involving a technical test). After couple of days, recruiter says - Unfortunately they say that you are too focused on best practices so they want to pass.

Fuck Oracle for their scummy practices.

New password cannot be one of your four previous passwords.
Password must conatin upper and lower case characters, at least two numbers and two special characters
Password cannot contain five or more consecutive letters of username.
Password cannot include any _illegal patterns_.

Locked out of your system? Drive over to HQ and ask the admins to reset your password in person.

Testing live cause you're to lazy to set up your test environment.. 😂

during code review...
peer: "you should pass this variable, and extract the logger from it"
me: "why? it is a 3 line logging function. why not pass the logger instance?"
peer: "because that is our best practice. It is the way we do things"
me: "why is it a best practice?"
peer: "because it is. We use it everywhere!"
me: "No we don't. And I still don't understand why is this a best practice. can you explain?"
peer: gives ups, did not look at the mr, and was not going to.

mr stays open. probably forever.

Password policy for a big water company site in Spain.

Translation: Between 6 and 10 characters (only letters and numbers, no spaces)

In guess they have a VARCHAR(10) password field in their db?!?

So I was reviewing my old code. Refactoring and improving the documentation.

This is a production app that is being used 24/7/365.

I see myself using "bar = foo" and there's even an explanation of what it does.
Apparently I resolved a relatively difficult Date object issue and had to use temporary variables.
Didn't know how to call them and ended up with these jewels.

Went to the ATM to get some cash.. entered an amount of 800 INR and to my surprise got an error saying "Your account does not have sufficient funds for this transaction" .. Instantly thought that my account has somehow been compromised.. checked the bank app and found out that I everything was normal..

As it turns out the ATM machine did not have 500 or 100 INR notes, thus it could not dispense my requested amount..

Now that's what we call a "Good" error handling..

I wonder how many decades it will take until employees stop to fucking stick their passwords to the computer screen at their station. It is a complete fucking nightmare if you are responsible for the network!
Can we bring back the guillotine? But it must be stub!
Those nitwits shall suffer!

Why the fuck would you allow special characters in your passwords, when some of them are considered "potentially dangerous!" can't even login ffs!

Won a new job; 50% payrise which, for a junior, is a pretty big deal.

A bigger team, with more established practices, a commitment to testing and code coverage, code reviews, and a smaller learning surface area as I go forward (focusing entirely on the js ecosystem, 80% frontend).

So this is all good.

But I *have* to go back to Windows. Windows *7*. Their infosec practices move at a glacial pace. After two glorious years on mac/linux I feel like being sick.

I love when people post a piece of their code here and got ranted for bad practices then posts "haha i was kidding, i would never do this" on the comment section.

I mean, we can learn here to, you're not suposed to be right 100% of the time, stop been so arrogant :/

Vendor: We are very professional and follow best practices, we know what we are doing. You should trust us.

Also Vendor 5 mins later: DB passwords, API keys and SSH keys in repo. AWS Access Keys shared in screenshots in email.

Me: 😭

“Password length mustn't exceed seventeen characters.”
Why? Why do some Web sites still have this rule? It's 2018. We should be using passwords of at least twenty-four characters. This is crap.

*logs in to pc*
- Your password will expire in 3 days. Consider changing it.
+ yeah sure...
*tries to change password*
- Your password must be different from your old 25 passwords
+ ....
+ What the fuck?!? I mean, really, what the fuck is this bullshit? You force me to use EXACTLY 8 char long passwords and this? Fuck you!

We act like a start-up and use agile practices.... Now we need you to give us a date for all these features.

Be skeptical of best practices. "Best" comes with assumptions, which may not apply to you.

Friend asked if I have ever built authentication using PHP and SQL...

Feel like sending links for them to research how instead of having me build it for them.

Teach a man to fish...?

Our current programming teacher actually being able to teach us good practices and give us constructive criticism on our code.

When UserID is an int(3) in one table, and then text(10) in another. And then the monent you see that the Username field is stored in both tables ......🖕🖕🖕🖕

Who dafuq wrote this crap?!?!?!?

Let's teach the class about security. OK *spends 1.5 hr teaching about encryption and practices* OK now students make a login page and just store the passwords in a JavaScript array....... *Facepalm*

The guy who became my manager just pushes to the prod branch.

On a repo where another team clearly set up development and production branches.

This guy has been pushing code like crazy and I always wanted to take my time setting things up properly in our team: TDD, CI/CD, etc.

Because he pushed so much he became my manager and I was seen as unproductive.

Data Science and software development best practices just dont coexist it seems.

Yeah yeah, it's up to me to start introducing good practices, but atm "getting it done" takes priority over the real based shit.

Agile: ✅

Agile practices: ✅

Certified Agile practitioners: ❌😡 powerpoint jockeys 👺💥⚡️failed programmers 💩 timewasting idiots 😥

In my team, unit tests are called so, because every Dev is a 'unit' who manually tests their own code...

Overworked team spends 2 months hacking together a Codecademy clone in record time: avoiding best practices, conflating paradigms, throwing shit at the wall until it stuck.

But today I submit a small UI fix that used a table instead of `display: table`...

C: “Look, I agree that these are likely leading practices, but we really don’t need all that.”

M: “These aren’t even leading practices, these are the bare minimum practices to help ensure secure login sessions and that account passwords aren’t trivially compromised.”

C: “How do I put this...? You’re trying to secure us against the hacker. That’s a noble goal. But my only concern is the auditor.”

M: “...”

*Senior Dev:* Ah yes, we need to put try-catch in every function to handle errors and Logger.Log() at the beginning.
*Me:* Is not better to define a global error handler and use the stacktrace instead of doing all that?
*Senior Dev*: ...
*Senior Dev*: Is a rule here, do what I'm telling you.

That's it, it's over, I'm done! I'm officially a graduate! I have my paper and I'm out!

Goodbye preditory USA college related companies and practices I won't miss you!

I swear If I ever have to hear the name Pearson again.....

Expert: "The core problem with passwords is that they reside on a server."

I suppose that's true, but only if you're a complete moron. Store a hash of a password, and users can authenticate against it with a password that doesn't get logged. This is technology that's been around for over fifty years. If you're storing passwords on a server, you deserve whatever trouble you get.

> asks for better pay
> starts trying to evaluate the quality of our efforts
> complains about doing things that are not good in the long run
> spends time mastering best practices
> unemployed

Vendor we('re forced to) work with, as we share a client. This is in their stylesheet. Fuck SEO best practices, amirite?! 😒

Why fix browser compatibility issues when you can just block what versions users can log in with?

"PHP does not need good practices, because the use of PHP it is already a good practice". This is one of the loading messages in the Slack where I work.

PS: We do not use PHP there.

fucking hate how some sites deliberately break their own scroll functionality if you haven't logged in/accepted gdpr nonsense/signed up for a newsletter.

It's such an easy fix (most of them just slap style="overflow:hidden;" to their <html> tag) but I still think it's very loathsome

"The password must have 7 or 8 characters (numbers and/or letters)”
says Movistar, the biggest ISP and telecom company in Spain ... I can't even.

Software development best practices: decouple your code

Apple, on applying a bold text style: Nah.

The worst thing I've seen a developer do would be becoming a university teacher while not being able to understand simple OOP or good programming practices.

I can't think of a most harmful one, just mediocrity cultivating unknowingly mediocre devs.

<rant>
Don't fucking tell me to move business logic from the service to the controller. Don't fucking tell me it will enable an "event driven architecture." Don't fucking use Angular for this project if you're just gonna shit on best practices and write convoluted, messy, inconsistent code and force your coworkers to do the same!
</rant>

Password

browsed LinkedIn articles, saw one about "good qualities of WordPress Developer", first bullet point is "following coding best practices" is it just me or that is one of the main things wrong with WP

Trying to be agile and employ modern best practices in a decades old traditional super-corp.

I feel like head butting a large nail

I kinda feel like people trying to call Facebook "Meta" is just as awkward as people trying to use correct pronouns when a person announces that now their pronouns changed.

A person, however, deserves to be understood.

Meanwhile, Meta is just Facebook. A new name won't solve that shit pile of ethical problems and sketchy business practices that just keeps growing.

Does anyone get the feeling that as they become more senior, they care less about meeting "best practices" and more of just "good enough"?

Best practices being everything in those books about TDD, unit testing, design patterns, design artifacts.

Good enough: enough so it won't blow up in prod, some tests but not 80-90%, some docs. Basically not like those public docs, open source projects/frameworks where function is covered

When I first started professionally, I was all about efficiency, good design, reducing technical debt, clean code.

But now, I look at problems and instinctively I may make these decisions but I don't really think about it much. First goal is to just get something working, clean it up later... Maybe.

I am driven by my love for this industry and wanting to do everything to the best of my ability.

Being a strong advocate for quality i am always on the look put for new practices and finding new ways to improve my code.

If you consider a project 'done' then you gave up on it.

I got moved to a new team. My old team was truly agile, and my manager was very "off hands" and actually let us work.

My new team is an older team that practices a bloated abomination called SAFe Agile, and the manager gets into all the details to the point of removing autonomy.

Shoot me please.

Paradise lost.

Me: Boycotting Facebook lately due to shady business practices, is very outspoken about how people shouldn't use Facebook services

Also me: Literally uses React for every web app

... conflicted 🤔

Love how DoD work requires sec+ certification but as you are learning the material you realize they don’t follow any procedures or practices.

A 'using namespace std;' in a FRIGGGINGG FRIGG LIBRARY HEADER.
"Yuh, I'm totally the king of multiverse. F*** me, right"

It bothers me when potential employers *require* a salary expectation in your application. It's like they're focusing on the wrong parts. I don't even consider places that do that, no matter how cool the job sounds. Remember kids, in negotiations, the first one to mention a number loses.

OpenAI is probably one of the most hypocritical companies in history. From the name, to how they copy other startups that build on top their platform, to how they use copyrighted material but prohibit others from using their model for training. I don;t understand how they are so celebrated when they engage in shady practices

Anyone know of any hosts NOT running on amazon/silicon valley/microsoft cloud?

I'm specifically looking for a host thats setup for or works well with python.

I'm about done with censorship and noplatforming. As a moderate that for a very long time was left of center, these practices are never justified.

i think formal education is the best, because it teaches good practices and all the whys of programming. it requires a lot of discipline and effort, but actually sitting down and studying theory is good for us

Me:To my new boss I think its fare we adopt version control for the project we working on.
Boss: No need just do what we hired you for.
Me:Its my second day of work and don't know how this will play out

Am beginning to dislike this boss he still sticks to old practices

And another shitty hoster...
Translation:
“The password is to long. Please choose a password that is not longer than 16 characters”

This book isn't at all what I thought it was going to be. I hoped it would be patterns and practices to writing better code...it's more like a philosophical Chicken Soup for the Developer's Soul. Self-care for syntax geeks.

And by that merit, it's actually quite good.

Well done zippo/willianpenn!

Today I got a reply to a PR comment from a coworker literally stating that "it's not a good practice to add unit tests to hotfixes".

I can't, just can't. Left me speechless. Wonder where this guy gets his "good practices" from.

I've read so many "best practices" on every topic just to come to one conclusion: it depends.

Sysadmin's nemesis: a DBA. Especially an oracle DBA. There's no other kind of tech worker I've seen who's more opposed to best practices.

How about for devs?

What are your thoughts about competitive coding and hackathons in general?

I sometimes feel that practices which are important for maintaining and structuring the code gets lost in the spirit of competition. Also, more hacks are kind of used to finish the assigned tasks rather than a proper approach.

Pointers like this:
char* string;

Or like this:
char *string;

?

As a rookie programming, I wrote really bad code and didn't understand why. Now, I've improved to where I know bad code, but I continue writing studios horrible solutions. And in the end up refactoring much until I don't have energy to look at my code anymore. This although knowing what I should/shouldn't do. Shame!

When writing code that has to be evaluated by a college prof, redirect all the best practices to /dev/null

Comment on a code review:
How does this relate to the task?
Me:
Most of the changes have nothing to do with the task, but half of the code & build system was either wrong, broken or not following best practices. This particular change is because something was broken.

When you have to build a startup product using enterprise project management methodologies, and corporate practices.

R.I.P Agile

Three things for me:

- when the mentor whom I admire said that I've kept growing non-stop and would have some discussions about how to execute things as an equal.

- when I more than doubled my salary in less than a year

- when I started to recognize code smell and bad code practices on the PRs

Ugh, been debating with a client for an hour about basic backups and security practices and want to tear my hair out. How do you guys deal with stubborn clients?

Somebody asked me for help on their thesis, gave them advise, how they should do it, what are the best practices on implementing things...

I asked the today how are they doing? They answered, we paid someone to do it, we can't do it...

Damn are they even studying and doing their daily programming practice???

Just because it's popular, doesn't mean it's good.

An overengineered solution can usually be simplified without breaking anything important. An oversimplified solution can rarely be upgraded without major breaking changes.

Not everything needs to follow the "best practices" - if it's not a part of the core functionality, diminishing returns often kick in quite fast.

Our IT team keeping our PET Production server alive by resizing partitions on the fly.
#living-on-the-edge
#caveman-practices

If you have no defined business processes whatsoever nor code quality practices, why bother putting on the job offer "software engineer" or "full stack web developer"?

WHAT YOU'RE LOOKING FOR IS A FUCKING PHP HACKER

My senior colleague recently said "Don't go around asking for best practices, it's a waste of time! Just try stuff until it works and commit it".

We were talking about writing code in a new language.

I do not think that GoTo is bad. It can lead to hellish code but if you don't misuse it - it can be extremely useful.

My colleague told me today that companies with shit code quality, complete chaos, no tests of QA of any kind, and poor security practices still make loads of money and are extremely successful so it's all a waste of time.

I detest this idea and I refuse to work like that anymore. But I also think he's right :(

Went through a lot of GitHub repositories and other people's codes to try to understand how the "magic" happens. Slowly started getting a hang of it. Good thing being, I picked up good coding practices along the way

When the „Senior“ of your colleague only stands for this
- knowledge of ancient technologies and practices
- Speed of a pensioner
- ability to learn like a dementia
- John snow knows more about coding the he does

This is not the senior you are looking for

What's the point of opening a PR if you're just going to immediately merge it without even asking anyone to look at it? Just so you can say "Oh look I'm following process"? Well, you're not..

Joining a new team to find that ,
Non .. and I mean non of all of their code is Asynchronous!! non .. zeroo !!

And they have told me to follow their practices !

I forze for a couple of seconds then I said : no !

* Start maintaining/upgrading new project at work
* Read book on best practices for the framework
* quickly realise all the "don't do this" parts of the examples in the book is EXACTLY how everything in the project is done
* cry self to sleep

Who else is tired of fancy new buzz words in and around software engineering (for practices and ideas that have been around long time in the industry).....
So we have to go back to school for english not the engineering ?

I feel like being a doctor is like being a contract dev. You're thrown into a bad situation, you know the stack but you don't know the project history, best practices aren't followed, and the only dev is also the primary stakeholder who learned everything he knows from w3schools.

Does someone know a site where i can get professional level help/guides/tutorials with system architecture questions? Like best practices for implementing common features? (Something like stackoverflow but where u actually get an answer instead of insults)

Googling for tutorials gives very basic/demo level results that might not be great for scale/security in prod env

Please, share your website backup strategies and practices - I have a simple php/mysql webapp and files don't actually have any backup other than the fact that they're also saved in a dropbox, and for DB I have a cron job that will export it daily and send it to my email.

How do you do it? How large are sites/app that you're backing up?

Looking at an old Java project, running java 1.6, test folder doesn't even exist and the "old but gold" java.utils.Date class is used throughout the whole thing. How do I initialise a new date again...? I actually just googled that :D At least the constructor parameters are named nicely... wait.. what...

Recruiter: we're looking for someone who knows .Net and "JAVA practices".

Me: <WTF is "java practices">
Me: <googling "java practices">
Me: dear recruiter, I know dotNet and good programming practices but there isn't thing like "java practices" in dotNet.

Recruiter: <no shit given>

Me: <why such incompetency is in charge of my potential future job?>

Best coding practices and tips

Until today, I had assumed deploying stuff to prod would NOT be one of my responsabilities in this company. Apparently that's not the case.

Had to deploy my code and pray it didn't break anything. Why is this a big deal at all?

Well you see, there is no repository. At all. No git, no svn, not even duplicate folders. No tests, no pipeline. Just a bunch of CPanels.

Had to manually copy files and folders from the development site to the production site and partially copy a database. "Just drag and drop" were the instructions I was given.

As if using CakePHP2, PHP5 and having to parse fucking Excel files wasn't bad enough, now I have to deal with one of the worst ways to deploy code.

Fuck it, I'm switching on the looking-for-job flag on linkedin.

how do you tell your "higher ups" that their practices/code are/is terrible?

Shoutouts to the former programmer that put 5 controllers and 1 service in a single .js file

!important in CSS and not commenting complex algorithms in c#

funny how creating something merely useless like a text2asciiart converter can spark this amount of joy

I loathe Google because of its censorship practices and general bias.

I'm a lot more organised now & I keep searching for good practices of everything, I try to save time at every step

(Questions below.) At this point I probably just whine about job search in IT w/o much commitment. It's because I don't learn stuff from interviews and have no willingness to prepare for primitive questions from HR's book. You know, stuff like: "What was your experience on previous jobs and why you quited them?" and "What are your advantages and cons?"
Even though I see them a bit discriminatory. I barely find words and make them audible alrite, and so rush to the stack questions. I answer 50% of them in average, 20% ideally. As a result, I get no conclusive offer. Fair... probably not. Doesn't matter.

All of a sudden, idea chimed in to make a personal website with all of the frequent questions answered in advance. At last, I've got some time to make the decent replacement of the CV into a landing page that communicates my professional and emotional ability to headhunters.

TL;DR: I wanna make my personal website portfolio and I need your word about the following.
1) Can I make up for the absence of my own live projects with OSS commitments or other smooth talk?
2) Is there a merit in answering the common interview questions right off the bat in written form?
3) So, I already prepared 4 conclusive theses with thoughtput choice of words, that I wanna place as a grid in first scrolling section. I call it "Principles", but perhaps there is a synonym to this one or it's good as it is?
4) I don't want to represent myself as a blunt set of "features". How do I transite into explaining the usage of my stack in these circumstances? Less text better, right?

So we have a confluence page all about best practices (there’s not even a lot in it) but when you check the repository, most rules are not followed 😭

companies really be having hiring practices like google but the works literally just servicenow ticket writing for an offshore team.

Today a senior developer and a colleague started looking into my code reviews and started commenting best practices that were never used in the team.
Got my chance back at the senior developer's code when he raised a code review, which had none of the best practices.
Gave back a good set of review comments to him :D
Karma is a boomerang :)

What Dev tools/practices would you love to see getting adapted into the normal world?

I would like to fork Spotify playlists!

Logs in to client office 365.

Big recommendation at the top

"Disable password auto expiry, it's currently set to 90 days"

Why is this a recommendation? I suppose there's an argument that making a user change every now and again will weaken their passwords over time, but really?

I'd be interested to hear what are some bad development practices you've ran into in your company?

Questions/best practises for git?

For example:
- use present tense in commit messages. (why though?)

A friend of mine also starts his commit messages with either [Task] or [Cleanup]. Useful for finding Commits in Gitlab etc, because only the first line is shown from the message.

Also, one teacher recommended the usage of branches and the other didn't because of alot of potential merge conflicts when working in a Team or a larger Collaboration. What are your thoughts?

Sorry for the messy post, have a hangover

Isn't it fun when you are given a library or framework and that in order to debug it you have to use some hacky way of hooking the code to a special instance of the project?

Even more fun: the developers by default don't debug the project with tools, but rather with logic. Ok, that's a good way to debug but it shouldn't be the only way to debug. I don't want to go back to the age of coding on paper. At least give me a stacktrace that's halfway clear on what's happening there. Even worse is when the framework doesn't document its own problems! stacktrace.someMagicalMethodNoOneKnowsWhatItDoes(). Having to read the even more mystic and overly verbose documentation! You're just left there trying and guessing shit, even for the senior devs!

And do you know what's more fucked up?! Fucking using println() to debug!! And they take this shit seriously! I don't understand how these people call themselves programmers. No breakpoints? What the fuck, man!

Just give me Visual Studio for fuck's sake. I don't want to code in a broken IDE with a broken framework. Development on its own is already hard enough, so don't make it harder by giving me crappy frameworks and crappy IDE's that only work half the time.

Debugging without a debugger, with broken IDE's, with broken frameworks, I'm sorry but that's just not for me. And then the framework dares advertise that it 'lets the developer focus on business code!' (how many times have you heard this crap before?). Right, the only thing I focus on constantly is trying to figure out why their broken framework doesn't work.

Arghhh.

SO sucks.

I'm looking for a community there I can learn good code practices through code review, but getting into a huge established open source project is really intimidating. Anyone have any good suggestions? My skill set is mostly Java and go

What do you think of online tests (for hiring) with a mandatory webcam?
The webcam part is making me anxious enough to back out.

J.P. Stinking Morgan Chase does not allow special characters in passwords.

This is stupid.

Load tests:

I'm used to do load tests in Visual Studio where it gives which line is exactly your bottleneck. But now I'm using VS Code (visual studio requires enterprise license for load tests :\ no longer have one)

Anyways long story short, what are the best practices for load tests? For me what I'm testing is how much can a given hardware specs handle and when test fails I go back and check if code can be optimized, is this the correct way to do this?

What a sad day for emulation tbh.
But yuzu had it coming, considering the practices they employed 🤷

They also have to pay a 2.4Mio fine.

Every once in a while I start to question my development principles and start to read articles, especially software philosophical, and try to improve my practices, aswell as find several trade-offs between my own best practices.

"I would say my biggest pet peeve related to the industry would be people focusing on technology instead of design, standards instead of users, and validation rather than innovation. Web standards and best practices are noble goals, but all too often in our community people forget they are a means to an end, not the end itself." - Jeff Croft

I'm starting to think that I could listen to some podcasts while I work, to learn things in the background.

Would you recommend good podcasts?

I'd like to listen to software dev good practices, or real life dev stories to learn from. Also videogame dev related would be good too.

Good friend, Jay. Helped level up my understanding over the years, JS patterns, using APIs, best practices, etc.

Also helped kill off anxiety about the community by proving we work together and share knowledge.

Many thanks and I hope everyone has a Jay in their life.

Is it me or most developers just write code so it compiles and passes tests?

No documentation, no standards, no "good practices", no"good design", no software principles, no performance analysis, nothing.

Yeah sure random tech recruiter, I like to be emailed directly on my email account that is only visible in that one regretful commit I made several years ago.

Definitely won't make me paranoid about your privacy practices.

On the other hand, it's refreshing to know that I'm somehow eligible for a senior position after 3 years experience

I never worked on PHP. Sharing to get more knowledge!

Project is dammed, is broken, we complain about it for almost 3 months, daily, code is old and client is full of bad practices and is always searching for a way to blame us for his failure.
Administration decides that best solution is motivate meditation techniques on dev team

Due to sad circumstances at my current company, I had to work with bash scripting exclusively.

At least I found joy even in this situation and now I'm satisfied with my bash TDD practices...

¯\_(ツ)_/¯

Oh you have a pull request that fixes a bug impacting customers atm? This is a perfect opportunity to write a novel that debates optimal coding practices in the review

Smiling eye twitch

MICROSERVICES ARE NOT A SUBSTITUTION FOR GOOD DEV PRACTICES, IF YOU WERE A WERECODER BEFORE MICROSERVICES, A MIGRATION WILL NOT TEACH YOU/YOUR TEAM HOW TO CODE.

My worst common practice:
I do almost everything as root. Even programs which tell me not to run as root, I do run them as root.

What are yours?

Wish everyone could understand that it's not learning the programming language or the 'best practices' that makes you good it's understanding how things work together and how to mix them to create new things that do what you want is the real engineering

I recently got carpal tunnel syndrome. Any suggestions for remedies, practices, etc. so I can keep doing my job?

There is a fine line between idiomatic code and idiotic fucktard.

Don't use "best practices" as an excuse to write shitfuck code.

When I started developing and was skeptical on my efficiency, one of the first things someone said to me was, "honestly, as long as it works, they'll be happy."

Aside from encouraging bad coding practices, would any of you give that same advice?

What are the best practices, which helps you follow "Pomodoro technique" and avoid wasting your time in general?

When you have to follow bad practices and practically fuck yourself because of short deathlines that your boss decided without you.

I'm learning python for work and trying to see the best practices for python projects. Are there any open source projects of python that anyone can post?

!rant

Lately I've started caring more about code standards and best practices, but as I am self taught I have never really learned them.. could anybody here be as helpful as to offer some insight as to how I could get a nice intro to the subject?

My languages of focus at the moment: PHP, Java (android)

+++ THEY ARE WRITING TYPE DEFINITIONS +++

THEY ARE UNDOGGING THEMSELVES. THIS IS NOT A DRILL: THEY ARE LEARNING SOME GOOD FUCKING PRACTICES

I wanted some ideas on how to word an error message better, so I googled "error message best practices".
80% of the results were about form validation and not actual code breaking errors >:(

On the up-side, I now know that I must not say "No, Bad User!"

How ofte are you guys absolutely sure that you've picked the right solution for a specific problem? As a novice programmer it bugs me to death that I sometimes don't know if I'm using a "best practice" solution

It's really sick how beginners start to code in Javascript and CSS, and their complex frameworks, without even understanding atleast the paradigm first. Googling your way up can be fine for smart ones, but as least time optimal this learning method sounds, it's as dangerous and non-productive too.
Also once project gets to a certain level, it's practically impossible to revisit and refactor old codes in front-end languages which kills the maintainability. Views?

I once had to implement a program to process CSV files. One line would be one order, so I wrote a class with a static factory method (Java) instead of an ordinary constructor, because I needed to throw exceptions if something with the line was wrong (which now and then was the case: invalid product IDs, missing fields and the like). After I committed my changes (CVS was still common in those days), a coworker (let's call him Max) asked me what the hell I was doing there. He expected me to replace the code (perfectly working, by the way) with either an ordinary constructor or by implementing "the factory pattern properly". His rationale: "We don't have those kinds of things in our code base!" So I let him argue a bit, not finding any well substantiated reason for me to "fix" the code. So Max wanted to team up with another developer in our office (let's call him Rick), explained the "issue" to him. I just sat there and enjoyed, knowing that Rick would not really care. But as soon as Rick understood what I did, he walked over to the book shelf, picked "Effective Java" from it, opened the book at chapter 1 and said to Max: "Look, Josh Bloch suggests doing it exactly that way for the problem at hand!" Max kept on arguing for a while, because his "rationale" (see above) was not affected by the fact that the code was actually good. It just didn't appear in our code base before.

!rant
TL;DR: Can anyone recommend or point at any resources which deal with best practices and software design for non-beginners?

I started out as a self-taught programmer 7 years ago when I was 15, now I'm computer science student at a university.
I'd consider myself pretty experienced when it comes to designing software as I already made lots of projects, from small things which can be done in a week, to a project which i worked on for more than a year. I don't have any problems with coming up with concepts for complex things. To give you an example I recently wrote a cache system for an android app I'm working on in my free time which can cache everything from REST responses to images on persistent storage combined with a memcache for even faster access to often accessed stuff all in a heavily multithreaded environment. I'd consider the system as solid. It uses a request pattern where everthing which needs to be done is represented by a CacheTask object which can be commited and all responses are packed into CacheResponse objects.

Now that you know what i mean by "non-beginner" lets get on to the problem:

In the last weeks I developed the feeling that I need to learn more. I need to learn more about designing and creating solid systems. The design phase is the most important part during development and I want to get it right for a lot bigger systems.
I already read a lot how other big systems are designed (android activity system and other things with the same scope) but I feel like I need to read something which deals with these things in a more general way.

Do you guys have any recommended readings on software design and best practices?

Co worker who makes the sliders/ banners for the site asks how to get his form input beside on the right side... asks all three people in his department... worker with "20 years experience" says they should use "!important"
😳Ahhh best practice says DO IT RIGHT!

was developing a custom website for a friend, coz i primised him id do so.

but when i actually developed it i felt lazy midway so i made one table store json strings and used it for every type of data he has on his website.

everything works fine and fast, its nothing he would notice but...

am I going to hell?

I probably do 15% of modern web dev best practices

Can someone help me to get some good practices with expressjs/sequelize combinations?
I managed to find how to not have all the models in the same js page and how to organize the routing but when I look the time it took me to find, I would like to don't have to search now 😂

!rant

So I got my first rails jobs today!! After learning ruby for a little more than a year on my own I spent the entire summer slaving away helping my Sr dev friend gaining really awesome really world experience and great practices. Now I'm officially a software developer in title haha so excited!

PHP best practices

I swear these underclassmen are in a contest to see how many unique one letter variable names they can come up.

When a software improvement organization (cough Scrum.org) does this stupid crap with their passwords, causing us all to be pwned.

I learned at IT school, because I didn't want to learn bad practices. And I don't regret that choice, teachers and courses were great !

My face learning Android in class, when being answered with "I don't give a shit" after asking how to do the program with best practices.

I get frustrated about the shitty work I'm forced to do to meet useless deadlines or follow meaningless ever changing consultant ideas.

I write a rant.

People in devrant suggest me best practices, solutions, tools, even technical steps.

I write this meta-devrant.

Devrant refuse to add more than 1 rant every 2 hours.
Fuck.

I start a project that follows the best architecture, best practices, etc..

i suddenly stop working on it until 3 days pre-deadline. at which point I end up building the shittiest, hackiest, thing that works enough to give to the client on time

What is the best way for an intermediate programmer to gain experience? The jobs I had before gave little to no feedback on my work other than was it done on time and does it work, I'm not confident enough in my knowledge to contribute to open source and I feel like I need guidance on best practices and such. Any suggestions are welcome.

When you saw the code of the whole product, and the best way to describe is the best example of a bad coding practices.

Looking at learning C++, anyone got any useful tips, best practices & trusted sources?

How to API / REST service calls. What are your suggestions/experiences/best practices?

Not dev per sé but annoys see he'll out of me on a monthly basis... 30 day password expiration, how does that make things more secure?! The thing that makes it worse is that I can't use any previous 28 passwords or anything too similar... Now I'm stuck with a 36 character password which I have to put in everytime my work machine decides to lock out... Which is less than a minute of not touching it.

What's that? No I can't turn around and answer a question because if I do I'll be taking 20mins off of my future career prospects as I'm working on leveling up my inevitable arthritis

Not following all the practices at the PSR