Hello.
It's better for me to leave this place because it's no different than an abusive workplace. Most of the people do not know what they are talking about and they can confuse things like implementing arrayaccess interface with implementing toArray method. Note: my pronouns ar she/her.
I am a computer scientist graduated 10 years ago, right now studying Masters of Visual Graphic design, because I was let go from my job with some bonus after half year of mobbing and harrassment. The girl who was moved in my position resigned after 3 months. So I am not paid other than freelance work. But when I am paid, it's not underpaid.
I am writing my second book. It's going to be about OOP. Yes it was 2001 when I started coding PHP, but there are new things to learn everyday. And I believe that, the best way of learning is doing and explaining others. The packages are not perfect, some of the feedback were great and I was working to fix them for long long hours. Because, when you write a book, you cannot say "Go to packagist and do composer require." All packages are almost fully tested, travis and scrutinizer checked, analyzed against patterns and anti patterns and fully types. Also all of them are PSR-12 and phpcs checked before pushing. (Why so strict? Because it's for a book.) Why it's for education? What is wrong with that? I know that nobody cares about my little packages, there is nothing wrong for me to use php 7.4 and its features. (Yes one of it comes from me.) Why packages? Because they are isolated, reusable and better than a monolith app in a book. Every package is going to be a new chapter. Is it forbidden to have bugs in a software piece written somewhere? I don't think so. The main aim of packages, they are explainable simple codes. They have to be short, not to include every edge cases. (So, I know that the JOIN is missing.) I also know that password_need_rehash or why we should not save plain text passwords into a database. So better not to assume. When you say, "the author, does not understand X"instead of "Hey, it seems that there is a bug here.", it's extremely offensive.
I answer politely to any issues, but I think polite feedback givers
- Do not assume anything.
- Do not make statements about me
- Do not argue about design
- Do not tell the code does not spark confidence.
There have been bunch of good code feedbacks like this one and some others: midorikocak/view#1 But every time I post a package there is always a comment like:
- It's not secure! It's dangerous. (Without explaining what could happen)
- What about this edge case?
- The author is X.
- Delete this post
- Remove this from packagist.
Sorry but this community suffers from bad attitude and I think for me it's better not to be part of it. In my opinion people should not be harassed for making mistakes but they have to be "celebrated". And worse than that, nobody should nitpick any kind of code to find mistakes to post things like "Ah postData! you are pwned!" when the post is not the http request method but instead a post as in a "Blog Post". I am disappointed about this community seeing it being no different than my ex toxic masculine workplace. Nobody dealing with any kind of harassment or mental health issues, should be part of this place. Thanks.
Midori