Dear Dev community, I have more ideas for new articles that I have time to actually write them.
Can you help me filter them out?
Please tell me which 1 or 2 subjects sounds most interesting to you.
A: Simple Continous Integration with GitHub Actions and Gradle
CI is useful but it is one more thing to setup, and when you do it for the first time, it feels overwhelming. It certainly felt that way for me. I have found a nice simple solution for people building with Gradle.
B: Asciidoc is Markdown done right
Markdown has become really popular and for a good reason: it tackles a real, important problem. Unfortunately while I love the idea of Markdown, it isn't really the right solution to that problem, which is why everbody is extending it in mutuable incompatible ways. Can we do better than this?
C: 20 pro tips for writing on dev.to
I have written a significant amount of articles and comments on dev.to now and I can share what I've found useful to do it better. I don't actually have 20 tips in mind right now, but I'm pretty sure I can brainstorm it :)
D: Rethinking job hunting powered by dev.to's collective widsom
My current job contract ends at the end of the month and I want to be smarter at job hunting that I was in the past. The basic premise of that article is that the hiring market is mostly broken. Not only because of how companies typically hire, but also because of how software developers typically hunt for a job. The reason it's broken is mostly inertia. It's hard to do things differently than others. But there is a lot of interesting articles on dev.to about careers... By leveraging that collective wisdom, we might be able to do better than that.
E: You had a problem, you used a regex, now you have two problems
There are some useful articles here on how to become a regex master.
True mastery however also involves knowing when not using them and how to do it instead. Regex are very powerful so you can use them fora lot of things. But that doesn't mean you should.
F: How to choose a mobile strategy that makes sense for you
You have a product and you think you need an app for this.
There are lots of options on how to do it, from going 100% native
to having only a website, to everything in between.
How to choose a strategy that makes sense for you?
Basic premise: mobile is hard, there is not one solution that is good
in all or even most cases, and you have to pick your poison.
Your turn: what's the most 1 or 2 interesting topics in this list?
Top comments (8)
I would love an article on subject A.
While I have managed to learn tweaking gradle on android studio. I never had a chance to build a professional gradle setup from scratch. And now since I have started taking java projects, I feel that would be right thimg to learn from you.
Also you are great at explaining things.
A if it's gonna involve caching because it's the only part I haven't figured out :P
Otherwise C and D would by far be the most widely impacting articles that I too am very interested in :-)
Caching which parts?
The download of dependencies? Or the build artifacts?
The downloaded dependencies. Build artifacts were a piece of cake with the official upload-artifact action.
'A' probability is the most interesting.
A and c
A
A & C 🙂