Just released the side project that made me join programming! :) It's been about five months and I learned a lot: PHP, JavaScript, CSS, Handlebars, Jquery, Git (terminal), I even started building a RestAPI. Its been an amazing journey, and I didn't alone! I met other Devs (now good friends) over the Internet and we did it together :) Thanks to everyone on DevRant for being such a great community!
If you want to take a look at the site is: projectgroupie.com
It's a website to find new projects you like and join them! So if you're a developer and you wanna make a blog, you post your project on PG asking for some designer to help you and if someone like it, he can join! :)

I hope you enjoy it and any feedback is welcome!

what kind of dumb fuck you have to be to get the react js dev job in company that has agile processes if you hate the JS all the way along with refusing to invest your time to learn about shit you are supposed to do and let's add total lack of understanding how things work, specifically giving zero fucks about agile and mocking it on every occasion and asking stupid questions that are answered in first 5 minutes of reading any blog post about intro to agile processes? Is it to annoy the shit out of others?

On top of that trying to reinvent the wheels for every friggin task with some totally unrelated tech or stack that is not used in the company you work for?

and solution is always half-assed and I always find flaw in it by just looking at it as there are tons of battle-tested solutions or patterns that are better by 100 miles regarding ease of use, security and optimization.

classic php/mysql backend issues - "ooh, the java has garbage collector" - i don't give a fuck about java at this company, give me friggin php solution - 'ooh, that issue in python/haskel/C#/LUA/basically any other prog language is resolved totally different and it looks better!' - well it seems that he knows everything besides php!

Yeah we will change all the fucking tech we use in this huge ass app because your inability to learn to focus on the friggin problem in the friggin language you got the job for.

Guy works with react, asked about thoughts on react - 'i hope it cease to exists along with whole JS ecosystem as soon as possible, because JS is weird'. Great, why did you fucking applied for the job in the first place if it pushes all of your wrong buttons!

Fucking rockstar/ninja developers! (and I don't mean on actual 'rockstar' language devs).

Also constantly talks about game development and we are developing web-related suite of apps, so why the fuck did you even applied? why?

I just hate that attitude of mocking everything and everyone along with the 'god complex' without really contributing with any constructive feedback combined with half-assed doing something that someone before him already mastered and on top of that pretending that is on the same level, but mainly acting as at least 2 levels above, alas in reality just produces bolognese that everybody has to clean up later.

When someone gives constructive feedback with lenghty argument why and how that solution is wrong on so many levels, pulls the 'well, i'm still learning that' card.

If I as code monkey can learn something in 2 friggin days including good practices and most of crazy intricacies about that new thing, you as a programmer god should be able to learn it in 2 fucking hours!

Fucking arrogant pricks!

I've been inspired by cpg grey (I think that's the name), mainly his 10 tips on how to be miserable, to write a blog or some kind of post explaining the 8 things you need to do if you hate your coworkers and want your codebase to go to shit.

So it'll be like a anti-SOLID, anti-pattern type of blog promoting every code smell imaginable

I feel like 8 tips to fuck up your codebase (php perhaps) might he more memorable than actual helpful advise. I'm sure that this has been done before, but I was wondering:

Do you think this would be effective? Would it help people understand why not to do the 8 tips? Does this reverse psychology work?

For the love of GOD, if you're an architect or someone in the position where you can make drastic changes to the overarching design of a software system, if you're so keen on enforcing something "cool" just because you've read about it in a blog post/seen it on a youtube video, READ ABOUT IT THOROUGHLY, as in, pick up a fucking book or do actual research. An architect overseas just informed us that a whole legacy PHP application (a fucking monolith with a dysfunctional database, yes, I think someone demented designed it) should be rewritten to a microservice architecture (without a messaging broker, just plain API interaction through HTTP) AND WE'RE KEEPING THE DATABASE WHICH BEGS TO BE PUT DOWN FOR GOOD. So now we're gonna have a clusterfuck of tons of PHP microservices (Q_Q) which interact through plain HTTP APIs (swagger's gonna be put to a test) and all have a single broken database in the center. Talk about a microlithic design. Jesus Christ.

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.