Ruslan Zavacky’s Post

🌟 Bytes of Brilliance: New Writers Welcome & July’s Technical Articles 🌟 Greetings, tech enthusiasts! 🙌 We're thrilled to welcome new writers to Code Like a Girl, adding their unique insights and knowledge to our amazing community. Your contributions play a major role in making Code Like a Girl the success it is today! 😍 If you're reading this and have an itch to write for Code Like a Girl or know someone who does, leave a comment on this article or spread the word by forwarding this newsletter to them! Let's expand our community together! 💪 👉 Find out more about writing guidelines at Code Like a Girl by clicking on this link: []() 🥁 Now, let's dive into July's most captivating articles, which are all about the thrilling world of different technologies! How exhilarating is that?! 🎉 💡 Shalise S. Ayromloo, PhD, takes us on an engaging journey through the story of Machine Learning. From its beginnings with Alan Turing to its practical applications in our everyday lives, Shalise introduces us to the fascinating world of ML and how it impacts everything, right down to advertising. It's a captivating story that'll entertain you while you learn! Dive into "Where It All Began: A Fun Guide to the Foundations of ML an…

This one is more for my Engineers, DevRels, and Technical Writers... Have you ever created broken backlinks on Gitbook? Then check out this video:

Here are 3 lessons I learned as a Technical Writer when I changed complex words for simpler ones while working for a software company: 1- Keep the language simple. Users want an easy read where they don't have to overthink. Just make small changes, like changing "commence" to "start." 2- Everything needs context. Don't assume users will read your Knowledge Base articles in the order you suggest. So, before diving into something complex, set the stage—explain what it is and why it matters. 3- Always let them know what's next, whether it's a step or how close they are to the end. Users are impatient and want to see the end of the process ASAP. The last thing they want is the feeling of being near the finish line and discovering there are still 10 more steps to go.

I started writing in dev to technical blog welcome everyone check out my blog post and leave a sincere review on what recommendations would make the blog better https://lnkd.in/e4FDPMJp

Every great journey starts with a single step. Write your first line today and unblock your inner writer with loopscribe

Do you cringe when you think about your past self, your writing from months/years ago, an earlier version of your product? If you said yes, congrats on leveling up!! This is what an early version of the welcome page for Pull looked like. We have a lot more to to do but proud of how far we have come and all the progress the team has made 🙌 And if you're curious about what the new version of this page looks like, go check out www.pullnow.com and click "Get Started"

The Puppy Stress-Test! Woof! Hey technical writers! We've all encountered complex jargon that makes even the most interested reader want to run for the hills. But remember, the primary role of a technical writer is to simplify the complex. Imagine your audience as a puppy. Puppies are enthusiastic and curious, but they have short attention spans. Would you explain API integration or software debugging in the same way to a puppy as you would to a seasoned engineer? Probably not. Use the 'puppy test' as your metric: If you can explain it simply enough that a puppy would get it (or at least wag its tail in interest), you're on the right track!

🚀 Fast feedback is one of the most important aspects of writing code IMO because it makes it easier to know what effect your changes are having. This is what makes REPL driven development with #clojure so #joyful . When you start working on your program you just boot up the REPL and only quit out when you're done. While you're in there your whole program is laid bare, you can invoke, inspect and run anything anytime and get instant feedback on your changes. In contrast, most other language workflows look more like a "Change some code, run the program, check the result" loop. Hopefully your program is fast enough that there's not too much delay but it's already adding a barrier between changing something and inspecting the result. And if you want to know what your program is actually doing you have to start debugging it because you have to get it back into the right state. This isn't a "my language is better than yours" post, rather it's a drawn out sigh that this kind of power is not available to more developers because I find that it brings me #joyatwork . Oh and interactive shells are not REPLs 🙉 https://lnkd.in/dYRhPMKf

Calling all technical writers! Don't miss our latest article on HelpNDoc's Characters Analyzer. Learn how this powerful tool can transform your documentation projects and boost your productivity 💼

Today I wrote my first editorial about a Leetcode problem. Writing the solution enabled me to more deeply understand the problem and how the solution is working. If you find any mistakes or areas for modification, it will be highly appreciated. I had thought of writing editorials about many problems before but always stopped, thinking that I would write them tomorrow. I will try to write solutions to Leetcode problems on a regular basis. Link : https://lnkd.in/dtRQsGpP #leetcode #leetcode2023 #leetcodechallenge #leetcodestreak