Conversation
|
@bambam955 this is ready for a first review. To be clear, this is the very rough first draft. I am very open to totally rewriting/restructuring it or even making major additions and/or deletions. Currently, I feel that last year's post was much better. It was more concise and to the point. Looking forward to hearing your feedback to help improve my meager output 😅 |
|
I think the biggest difference between last year's post and this year's is an increased focus on writing about the details. It's a well-written post in its own right, but it feels a little more like a report than a blog post. Last year's post was more focused on the lessons learned from something that happened. For example, in this year's post, you talk about how Go was a "breath of fresh air" compared to older languages...and you say why...but what was the lesson there? To me, the lesson I learned was that it's important to not be biased towards a particular language or framework just because it's what you're familiar with. I think a more apt title for this post at the moment is "2025 in Review", and I know that's not what you were going for...I would say focus less on the details of what happened (no need to specify that subdomains of mrs-electronics.dev are for various projects) and more on the why or lesson (being able to easily access documentation via public websites works better for both devs and customers). Hopefully that's not too harsh. I genuinely think it's a great piece of writing on its own. But I think the points I made above are maybe the reason you think it needs revision. |
|
I think that is very accurate feedback. Which way would you lean? Just rename it and embrace it being "2025 in Review"? Or rework it? One idea I had for rework was to reduce a lot of the lists I have in written-out form to bullet-point form. This would be must more blog-like. I agree that if it is going to be "Lessons From 2025", it should focus much more on the why of each big change. Really, I'm not just how well I could write about lessons learned from 2025. To me, it felt more like the year was about having some ambitious goals for improvements (which line up pretty well with the 3 top-level sections), implementing steps towards those goals, and then benefiting from the improvements. I'm not sure how many noteworthy lessons I learned, it was more about taking lessons learned and applied on individual projects and scaling them across projects. Maybe you have a different perspective, would love to hear it! |
|
I personally would lean towards a "Lessons" focus...but really that's up to you 😅 Yeah that would definitely help. Bullet points to say "here's what we did" and then longer-form sentences to explain the whys and results. That's fair...the things we learned in 2024 kinda gave us the direction for 2025... What if you kept this post as-is and then I wrote a short "Lessons" post? I have some ideas... |
I think it is a great idea for you to write the "Lessons from 2025" post! 😁 Leave this one totally as-is? No change requests? |
|
Title and date updated! |
I thought you'd like that idea 😆 yeah I think so. I enjoyed reading it as a "year in review" post, nothing really stuck out to me as needing changed. |
|
approval requested |
2 participants
No description provided.