Hi-yo
Hope you all had a lovely weekend. I spent most of mine writing about PostGIS performance and implementing an API server in Clojure for one of my side projects. It's super frustrating when code in documentation doesn't work and you have to go spelunking for an alternative solution. I was having issues with some form data middleware for reitit, which ultimately got resolved by scrapping that specific middleware function and using the one it was a wrapper for. I still don't know what the actual problem was. *shrug*
It did make me think about how I approach learning new libraries/tools though. I'm definitely much more in the camp of "just try to get something to work", rather than "open up the lib code and try to understand it from the bottom up". To be fair, if opening the lib code is the only possible option, I can do it, but it's rarely my first choice. What about you? How do you approach a new lib you want to use?
I can see the benefits of going the bottom up route, but I feel like I'd just waste too much time trying to understand a lib, to then choose not to use it because of some discovered limitation during implementation. At the moment my "build first, understand later" approach seems to filter out shitty libs that I wouldn't want to use any, because they have unintuitive design, terrible docs, or some fundamental flaw specific to the use case. I'd be curious to hear what you think.
Anyway, here's the issue.
|
|
|
====================================================================
Developers need and deserve good documentation. But let’s face it, most documentation systems are broken, leading to incomplete, outdated, and hard to find docs. Swimm’s platform can be set up in minutes and gives engineering teams usable, discoverable, and auto-synced documentation - all without interrupting their regular workflow.
|
|
====================================================================
Published: 19 August 2022
Tags: compiler
Jeremy Ong compiles shaders in Compile Explorer and peruses the output.
|
|
====================================================================
Published: 18 August 2022
Tags: css
Jen Simmons presents the (relatively) newly added :has() selector in CSS and how you can use it to conditionally apply layouts.
|
|
====================================================================
Published: 18 August 2022
Tags: web assembly
Andy Wingo demonstrates how WebAssembly could support JIT compilation.
|
|
====================================================================
Published: 7 May 2021
Tags: philosophy, research paper
Edson Dias, Paulo Meirelles, Fernando Castor, Igor Steinmacher, and Gustavo Pinto present a thorough study conducted on what attributes make a great open source maintainer. Spoiler, communication is numero uno.
|
|
How did I do?
|
1
|
2
|
3
|
4
|
5
|
Bad
|
|
|
|
Good
|
Want to help and get cool stuff?
Thank you for reading! If you enjoy the newsletter, I would really appreciate you helping me spread the word by forwarding this to your friends and colleagues or sharing it on social media! Get cool stuff for your referrals using your link https://abyteofcoding.com or the buttons below.
If you want to discuss or comment on this issue, head on over to this page at A Byte of Coding. You can also subscribe there if you're new!
Have comments or feedback? Just reply to this email or hit me up on Twitter @AByteOfCoding.
Email landed in your promotions tab? Please move it over to primary so you don't miss the latest issues in the future.
|
|
Thanks for your Support!
Thanks to sponsors and supporters like Євген Грицай, Scott Munro, zturak, pek, Emil Hannesbo, Joe Hill, Astrid Sapphire, Gregory Mazzola, moki scott, Michael, Matt Braun, Tim Nash, Christoffer, and Mike Rhodes this newsletter is provided to you for free. If you'd like to also show your support and buy me a monthly meal, you can donate on the Patreon page. It's not necessary, but it lets me know that I'm doing a good job and that you're finding value in the content.
|
|
|
|
|
|
|