You can now easily import your 3 favorite notes into DeepCura and it will learn your writing style, no need to learn fancy prompt engineering skills. Watch the video below to see how it works.
DeepCura AI’s Post
More Relevant Posts
-
One of the hardest lessons I've learned from writing over the years is this: Adding more words rarely leads to increased clarity. When someone comments on your doc that something isn't clear, your first reaction shouldn't be to add but to take away. What words are confusing? Is something out of order? Which sentences provide little value? This principle scales, too. Many engineers will cry that their docs are out-of-date or don't capture the correct details. They then run to create an entirely new set of documents to provide clarity. But the original documents exist and aren't cleaned up, creating the "yet another competing standard" problem. The knowledge base is now more confusing than before. A better approach might be to think: What docs are truly obsolete? Can we archive the docs that are? What details are getting in the way of these docs being helpful to others? More words are just more opportunities for more confusion.
-
Too often engineers get caught up in abstraction and lose sight of the problem they are trying to solve. It would be like a writer getting stuck on the perfect hook and never writing anything. Or a golfer regripping their club and never hitting the ball. A key takeaway from my entry-level writing course in college was to write "Shitty First Drafts". You don't have to merge in that draft, but at least you will have something to improve upon. It will give you something you can reflect and refine. It could be that the problem was hiding something else. Maybe your first draft will end up being something that becomes a full-fledged product. Who knows? However, no one will know what it will be unless you sit down and code it.
-
Staff Software Engineer | Delivery Hero Talabat | Passionate TDDist | Android | Backend
Prompt Engineering = High Quality Writing High quality writing has always been about knowing who are you writing for. The more you know about subject matter than object matter the more you are able to drive value.
-
Writing technical papers is a significant achievement for engineers. Looking to improve your technical paper writing? Check out this tutorial for crafting excellent papers! https://lnkd.in/dkGc_hkD #spe #engineering #technicalwriting #careerdevelopment
Writing an Excellent Problem Centered Technical Paper
https://www.youtube.com/
-
👋 Hi everyone, I am excited to share with you a valuable template that I frequently use for writing technical documentation. It is an essential first step whenever I implement a new feature or optimization. I hope it will be helpful to you. 💪 Another link to the blog: https://lnkd.in/gW4aCHaY You can visit my blog here: https://blog.luciango.com
-
Lead Software Engineer | Node.js, React.js, Typescript, PHP, Ruby, TDD, Clean Architecture, AWS
Love and take care of your documents! I don't know a better strategy to share complex topics than the (g)old writing. Documents will require structuring your thoughts in advance. Your audience will get the best version of your content. My invite for everyone, especially Software Engineers, is to write more! Write articles on Medium. Write more internal documentation. Write! Writing is like DSA exercises for thoughts.
-
The process of writing tests could be deemed as an investment of time, but one that yields valuable results. It is crucial to recognize that skipping tests often results in spending more time debugging the codebase, rather than utilizing the tests to locate the specific test that has failed and subsequently fix the related code. Hence, investing time in writing tests is of paramount importance for optimal efficiency and productivity in a business or academic setting.
Many developers skip writing tests due to lack of time. But they have a lack of time because they skip writing tests.
-
This is a great post, but as I scan the comments, I see a theme emerging: people don't write tests because they perceive them as hard to write. I almost always find that if the code is hard to test, it's hard to understand too and therefore hard to change. I use "writing tests for this is hard" as a signal that the design of the code is not quite what it should be and then adjust the design of the code accordingly.
Many developers skip writing tests due to lack of time. But they have a lack of time because they skip writing tests.
