It's funny to work on certain projects, because sometimes your lines diff is super enormous because you move a 1700-lines-long file into several smaller classes, and the copyright header takes 30 lines.
If I was judged by Elno, he would definitely think I'm an awesome developer.
I absolutely hate this capitalistic view of Open Source, the saying "We do whatever we want, it's Open Source anyway".
This leads to philosophies like "Let's rewrite this entire thing our way, and put some marketing on it, this will destroy the previous project and deny the work of all its contributors, but hey, it's Open Source".
Or even "Let's take this entire project, add our brand, put some glitter and marketing on it, and sell it, without giving any fucks to its maintainers".
Experience has told me that companies that are really successful in tech often don't care about code quality, they succeed by doing two things:
Spend a lot in marketing to fund the product
Use the money to fund two things: support, and quick coding.
Legacy projects are successful projects, and the biggest companies that have been here for super long time are most of the times companies that contain hundreds of thousands of lines of bad code and they're ok with it as long as "it works".
@lucastucious This realisation makes me wonder whether I should quit quality code, especially since I specialise in refactoring and modernizing legacy code 😬
Bon bah le CFP du Forum PHP est ouvert, j'ai déjà vu plusieurs talks sur des sujets similaires que je voulais moi-même abordé après avoir fait mes propositions (j'ai soumis mes talks avant de regarder, sinon je suis 100% sûr que j'aurais été découragé).
Bah je suis découragé à l'avance : j'ai aucun autre talk à soumettre à part les quelques idées que j'ai déjà proposées et qui sont quasiment toujours rejetées, donc c'est dead pour moi cette année, encore.
However, I'm dropping a unit-testing setup of single components, and added more tests, and I like that, even though it's a long process to make it work!
Once again, a unit test and a hell lot of debugging time helped me realise that I long ago had a function that should have been broken but wasn't for strange reasons.
Still, in a Promise, I used "return resolveFunc" instead of calling "resolveFunc()".
return new Promise((resolve) => {
this._callback(data, operation, requestParameters);
return resolve;
resolve();
});
That's stupid, I know.
I even don't have any idea why I couldn't see that before. Everything worked super well, but it's only when unit-testing this particular piece of code that I realized the promise actually takes super long time, therefore is never resolved ("never resolved" should have given me a hint, by the way)
@pierstoval
Yeah, I usually watch YT on my iPhone via safari, which is the only browser allowing you to use an ad-blocker at the time, and because i'm not using the app or chrome I have a "BUFFERING" time of 5 ~15 sec before each video, anyways, that's the time I'm not watching ads so, I don't mind.
The thing is that if it was a real technical limitation due to the browser, then why can I see the vidéos launching instantly on the homepage ? 😅