Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "xdebug"
Dear designer, if you're generating assets please make sure you're naming them right. And oh, get rid of that .DS_Store thing please.10
Do you ever have those weeks where you have to fix a bug, then uncover another bug then another then another. Then you realise some functionality is completely missing. You write tests to cover your bug fixes and new functionality. Then you realise tests are broken with your fixes and you have no idea why. Then you get so frustrated you start making silly mistakes. Then your debugger starts playing up.... Yeah that's been my week.5
*explains the importance of official docs*
*moments later, the intern pointing at his screen to a crappy YouTube tutorial video*
Intern: How did he figure all this stuff out? He must be a genius.1
Everywhere you go, you find these memes where developers are skeptical of their work. Things like "It works. I don't know how. It doesn't work. I don't know how.". Don't you guys think this is a huge problem? And people say that their programming language is the best, because preference. But isn't this happening because our tools suck?
Yes the problems maybe inherently complex but at least we should be able to figure out the logic behind the snipper and reason about it.
Haven't really experienced it, but they say Haskell and the likes are great at this and it must be true because it's backed by mathematical properties and laws, not " experience".
So the rant here is, wish we had better tools in the mainstream that allowed us to enjoy absolute faith in at least what we have written, regardless of the fact that we understood the problem in the domain.11
Modify the front-end code and noting change.
Empty the cache... ✔️ not work
Check xampp open... ✔️ not work
Check my sass compile... ✔️ not work
Compile vuejs webpack... ✔️ not work
Check my laravel route... ✔️ not work
Check with Xdebug... ✔️ not work
Go get coffee... ✔️Not work
See the url on stagging.<website>.ca in my browser ❌
😲🙄😅 Holy fucking retard i am...4
Meta devRant rant:
Everyday there's a rant that reads, "I don't care what others think but I love me some PHP because all the $ gets me $$$, it just works™!"2
Nearly strangled a fellow dev after finding out he refuses to use xdebug and litters his code with `die()`statements instead2
These god damn idiots!11!!
Why, for duck sake, php-fpm and xdebug are using the same standard port 9000?
There are thousands of different ducking ports you could choose from!
So each developer who wants to debug his php app served by php-fpm, has to adjust the port for xdebug on something like 9001 or 10000.
Especially when it comes to debugging third party (usually outsourced) plugins and implantations..
It's daz vile wild west over there, you never know where something is defined, but more often that not, some obscure TypoScript file.
Never have i been so grateful for xdebug & grep / awk combined with regular expressions..
CamanJS is a nice library and such but why does it's vignette function take a String as it's parameter for percentage!? It parses it by removing the '%' character and doing a parseInt()!2
So far in my new job, a colleague that refuses to use Xdebug and contractors that don't document anything they do.1
Do you ever have days where you get absolutely nothing done, because of a local environment problem. My xdebug would break on break points but once you stepped to the next breakpoint it would halt execution of the code... It worked fine yesterday!!!!! Arghhh1
Visual Studio Code and xdebug: my saviors to finally not have to put up with NuSphere PhpEd constantly shitting itself over memory limit issues in my 3,704 file PHP project.
About ready to murder Xdebug...debugging an issue on a Drupal site and the debugger catches fine if I set a breakpoint in index.php, but breakpoints in any other file do not catch, even though die statements show that code is being executed where the breakpoint is set.3
"XDebug is like the SELinux of PHP."
-"I know right? It's the thing you always have to disable when something weirds out."
- random dudes on the train home
One of those debugging days where minutes feel like hours, and hours like days.
I had the bad luck of being asked to dive into a legacy project which was unmaintained for months, but of course it's still on prod. And very suddenly the urgent need arrises to change stuff.
Yet: the docker stack won't work. It builds fine but the stack crashes.
Long story short: some internal api URI were renamed and at some point one internal api started to always require an access token. Which we set for the stage, prod env yet somebody forgot to mention that to the devs of legacy-project.
That ain't too bad.
WHAT IS FUCKING BAD IS THAT YOUR SHITTY APP SWALLOWS THE ERROR MESSAGE!
I mean it's bad enough I have to `var_dump && die` your app since you never bothered to setup a xdebug that I could use out of the box, yet egregious fact that your app would catch a valid exception but transforms it into an "internal warning" is borderline insane!
It's ok to throw exceptions. It's ok to let your service die. That's how other will know what and where to fix it. (You may want to restrict the data visible to the outside, but that's a whole different conversation.)
Not being able to lol at "Monad is a monoid in the category of endofunctors." joke even after several readings of articles/guides online.
Assured the boss that the app will be ready in minutes and only a simple callback implementation is yet to be made. Immediately discovered that the library is inconsistent with the docs and only thing possible is to file an issue. Way to go Facebook Fresco!