@ekaitz_zarraga pretty much sums up C++ for me as well. I'm often surprised to find some code fixed or written by myself which I can't reason about without a ridiculous amount of mental effort :blobpeek:
Conversation
Notices
-
Adrián Pérez (aperezdc@mastodon.social)'s status on Wednesday, 22-Dec-2021 09:33:37 CET Adrián Pérez -
ghostdancer (ghostdancer@mastodon.sdf.org)'s status on Wednesday, 22-Dec-2021 09:57:39 CET ghostdancer @ekaitz_zarraga Your book? 🤣 🤣 🤣
-
ghostdancer (ghostdancer@mastodon.sdf.org)'s status on Wednesday, 22-Dec-2021 10:03:12 CET ghostdancer @ekaitz_zarraga I thought that was one already published,
-
Adrián Pérez (aperezdc@mastodon.social)'s status on Wednesday, 22-Dec-2021 10:09:39 CET Adrián Pérez @ekaitz_zarraga I spend most of my days doing bringups of WPE WebKit in new hardware, integrating it with other pieces of software, and also contributing to WebKit itself... So basically 80% of the time I'm in C/C++ land, the other 20% in anything needed to get things working (mostly build tools: Python, Make, Bitbake, Buildroot, shell scripts...)
-
Adrián Pérez (aperezdc@mastodon.social)'s status on Wednesday, 22-Dec-2021 10:51:15 CET Adrián Pérez @ekaitz_zarraga I don't consider myself that good at C++, but I can manage my way around decently most of the time. I enjoy plain C much more, despite its warts, to be honest.