HN user

jpoesen

351 karma

PHP Developer, Instructional Designer, Drupal trainer.

Posts1
Comments55
View on HN

Mali's a Daesh hotbed.

Mali has been close to Russia politically, culturally, economically, and militarily since the 1960's.

Mali's welcomed Russian troops, including Wagner's, in the wake of the French pulling out.

"[The Russian involvement in Mali] signals a major expansion of Russia's military interests in Africa and a strategic setback for the West. The deployment of Russian military contractors signals a profound break with France and the West."

https://www.bbc.com/news/world-africa-58751423

https://www.reuters.com/world/africa/un-security-council-end...

https://www.chathamhouse.org/2021/12/russias-presence-mali-r...

https://en.wikipedia.org/wiki/Mali%E2%80%93Russia_relations

If you use duckduckgo there's the ddg-filter firefox plugin that lets you block domains. I use it to block exactly the low quality domains you mention.

Maybe there are similar plugins for other search engines as well...

Exactly this.

Similar example: Tintin in Congo is by today's standards absolutely racist, but reflects the era when it was published. The last decade the (Belgian) publisher was sued multiple times to try and force it off the shelves.

Also: calls to remove statues of King Leopold II (who committed horrible atrocities in "his" Congolese colony).

In both cases, why not leave access to the original books/statue/... intact but add an introductory section on why this is no longer appropriate today. Or place a contrasting statue, opposite King Leopold II, that embodies the struggle for independence / the colonial horrors / the blight that is racism / etc.

Overall it feels like there's a drive to remove "inappropriate" materials from society, instead of leaving them accessible as living proof of the mistakes that were made, and to provide backstory, context, and the "appropriate" contemporary view.

tl:dr: contribute to opensource -> learn tech and tools in the real world, forge relationships and expand your network, all while learning.

--

One approach is to pick one (or a handful) of opensource projects that use tech you seem interested in, and start contributing in small ways: correcting typos, testing if patch or merge request X does indeed seem to solve problem Y and report back, etc.

Many projects tag issues that are well-suited for beginners, and many welcome first-time contributions.

Doing this exposes you too a specific set of tools and processes, teaches you collaboration and making things happen, and can create friendship for life.

Also, don't dismiss writing about what you learn. Either as a dev journal blog or helping with documentation, writing tutorial-style forces you to be technically correct and unambiguous, and in turn forces you to learn about things at a level of detail you wouldn't otherwise have bothered to research.

Great news! But please run it on your main domain, as something like social.washingtonpost.com rather than washingtonpost.social.

Running the instance under your own well-known domain equals instant verification and trust, whereas anyone can set up a .social.

My friend, if you have time to ask for a tl;dr and ask follow-up questions, you have time to read the original post. Off you go.

Thanks. Too bad you didn't find Drupal worth hanging around for. Great you found a stack that makes you happier.

Dunking on a tech while using a throwaway account and not providing details on why you find it absolute misery... not very useful or trustworthy.

Check out The Impostor's Handbook: 2-parts on various CS concepts in human-readable language.

Also, I'd look into modern practices around the tech stack / programming language of your choice: code linters, debug tools, static analysis tools, refactoring tools, various command line tools, build/packagement tools, etc.

Also familiarize yourself with the CI/CD tools/approaches in your field.

Lastly, find one or more opensource projects with decent QA practices and start contributing to get into the habit of following prescribed tools, code standards, automated testing, etc.

Good luck.