# personal-experience Published articles for personal-experience. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building an Audience Through Technical Writing: Strategies and Mistakes DevFeed: [Building an Audience Through Technical Writing: Strategies and Mistakes]() Original publisher: [Read original article]() Author: Hamel Husain Published: 2024-11-30T08:00:00Z Content type: tutorial Language: en Sources: [Hamel Husain]() Topics: [Learning](), [Artificial Intelligence]() Tags: [building](), [consistency](), [developers](), [how-to](), [marketing](), [personal-experience](), [technical](), [writing]() ### AI overview An advice article on building an audience through technical writing. It recommends thoughtfully engaging with other people's work, adding meaningful insights, publishing consistently, and participating in discussions rather than relying only on promotional content. ### Source excerpt People often find me through my writing on AI and tech. This creates an interesting pattern. Nearly every week, vendors reach out asking me to write about their products. While I appreciate their interest and love learning about new tools, I reserve my writing for topics that I have personal experience with. One conversation last week really stuck with me. A founder confided, "We can write the best content in the world, but we don't have any distribution." This hit home because I used to think the same way. Let me share what works for reaching developers. Companies and individuals alike often skip the basics when trying to grow their audience. These are proven approaches I've seen succeed, both in my work and in others' efforts to grow their audience in the AI space. 1. Build on Great Work Here's something surprising: few people take the time to thoughtfully engage with others' work in our field. But when you do, amazing things happen naturally. For example, here are some recent posts I've enjoyed that present opportunities to engage with others: Shreya Shankar's DocETL Eugene Yan's work on AlignEval Ben Claive's work on rerankers Jeremy Howard's work on llms.txt In the above examples, you could share how their ideas connect with what you've built. You could add additional case studies and real-world insights. If you deeply engage with someone's work and add your insights, they often share your content with their audience. Not because you asked, but because you've added something meaningful to their work. Swyx has written a great post on how to do this effectively. The key is authenticity. Don't do this just for marketing--do it because you're genuinely interested in learning from others and building on their ideas. It's not hard to find things to be excited about. I'm amazed by how few people take this approach. It's both effective and fun. 2. Show Up Consistently I see too many folks blogging or posting once every few months and wondering why they're not getting tr ## On being a Freelance Full-Stack Developer DevFeed: [On being a Freelance Full-Stack Developer]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2024-11-20T11:50:46Z Content type: opinion Language: en Sources: [Robin Wieruch]() Topics: [web applications](), [Web Development](), [React](), [Node.js](), [React Native](), [JavaScript](), [Next.js]() Tags: [2017](), [apis](), [career](), [freelance](), [freelance-full-stack-developer](), [javascript](), [junior-developer](), [next-js](), [node-js](), [personal-experience](), [react](), [remote](), [side-projects](), [skills](), [team](), [web-applications]() ### AI overview A freelance full-stack developer reflects on working with companies to build and maintain web applications and APIs. The article describes the prior experience, collaboration, side projects, and technical skills the author considers important before starting freelance work. ### Source excerpt ... ## Preparing for Android Job Interviews: A Guide to the Typical Interview Process DevFeed: [Preparing for Android Job Interviews: A Guide to the Typical Interview Process]() Original publisher: [Read original article]() Author: blundell Published: 2023-05-16T21:19:15Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [Android](), [App](), [Code]() Tags: [android](), [androiddev](), [blog](), [hiring](), [intermediate](), [interviewing](), [interviews](), [personal-experience](), [process](), [reference](), [reference-android-androiddev-interviewing-interviews]() ### AI overview This personal-experience guide describes common stages of an Android job interview, including an introductory conversation and take-home exercise. It offers preparation advice such as reviewing the job candidate's CV, researching the company, following the exercise rubric, and documenting code decisions. ### Source excerpt This post aims to demystify some of the steps in a typical Android interview process. We'll discuss steps, strategies, targets and solutions. Getting you better prepared to get your next Android role. This blog is from personal experience, caveat up front that your experience could be completely different, but I've been through A LOT of [...] The post Proven Prepping for Easy Android Interviews in 2023 first appeared on Blundell. ## Five Costs Engineers Don't Know About Breaking A Critical Path In The App DevFeed: [Five Costs Engineers Don't Know About Breaking A Critical Path In The App]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2022-10-22T05:12:08Z Content type: opinion Language: en Sources: [Ishan Khanna]() Topics: [App](), [Software](), [Monitoring]() Tags: [app](), [article](), [monitoring](), [personal-experience](), [production](), [software](), [software-engineering]() ### AI overview The article identifies five types of costs that can result from breaking a critical path in an app: explicit revenue loss, collateral damage to the business, investigation, fixing, and remediation. It also discusses effects on brand perception, app ratings, user retention, and engagement. ### Source excerpt In this article, I share five costs of breaking a critical path of your app that most engineers don't consider while writing software. ## What's on My Desk? DevFeed: [What's on My Desk?]() Original publisher: [Read original article]() Published: 2021-10-24T08:30:00Z Content type: opinion Language: en Sources: [Gunnar Morling]() Topics: [Large Screen](), [samsung](), [macOS]() Tags: [cameras](), [computer](), [conferences](), [covid](), [curved](), [evaluation](), [monitors](), [personal-experience](), [samsung](), [screen](), [ultra-wide](), [wide](), [work]() ### AI overview A personal account of improving a home computer setup for remote work, online calls, and recording conference talks. The article discusses a curved Samsung ultra-wide monitor and briefly introduces other setup components, including cameras, lighting, and audio equipment. ### Source excerpt Table of Contents The Screen Compute Cameras Work in Progress: Teleprompter Lighting Audio What's Next? I've been working from home exclusively for the last nine years, but it was only last year that I started to look into ways for expanding my computer set-up and go beyond the usual combination of having a laptop with your regular external screen. The global COVID-19 pandemic, the prospect of having more calls with colleagues than ever (no physical meetings), and the constantly increasing need for recording talks for online conferences and meet-ups made me reevaluate things and steadily improve and fine tune my set-up, in particular in regards to better video and audio quality. ## How I made beautiful screenshots for Google Play (Developer experience) DevFeed: [How I made beautiful screenshots for Google Play (Developer experience)]() Original publisher: [Read original article]() Author: Yahor Urbanovich Published: 2021-07-10T11:24:12Z Content type: tutorial Language: en Sources: [Stories by Yahor Urbanovich on Medium]() Topics: [Google Play](), [Android](), [App](), [Mobile](), [pixel]() Tags: [android](), [android-studio](), [developer](), [google-play](), [google-play-developer](), [personal-experience](), [photoshop](), [play-store](), [screenshots]() ### AI overview A developer shares a workflow for creating polished Google Play screenshots, comparing device-mockup tools and online services with a do-it-yourself approach using Google Play guidelines, Photoshop, mobile tools, and Android Studio. ### Source excerpt Comparison of the initial and final result Every developer who has an application in Play Store worries about user engagement before the application install. This metric can be simply improved by adding beautiful and informative screenshots. I want to share my own experience of how I made it for my pet project. Let's begin. Originally I prepared screenshots for Google Play using a simple approach: Make a screenshot of the application Add it into Device Mockup to make it more natural Publish to Google Play For this purpose, I used Screener: https://play.google.com/store/apps/details?id=de.toastcode.screener&hl=en_US The tool is useful, contains a different amount of phone frames and manufacturers, and fully customizable. Screenshot after rendering The main lack for me that the application didn't update since 2018 and doesn't contain new Android devices, especially Google Pixel's latest model. Screener app info from Google PlayFind the other solutions. If you are lazy and don't want to spend your free time, the best way to organize screenshots is through online services. Few of them, which I have tried: https://mockups.pixeltrue.com/ 2. https://previewed.app/ 3. https://theapplaunchpad.com/ 4. https://screen.traction.one/ 5. https://www.launchmatic.app/ The main drawbacks of online services for me: To unlock more themes and functionalities you need to have paid subscription Limited customization Can't adjust the screenshot for mockup, the content cropped unexpectedly from different sides Some services focus only on iPhone or several Android devices How to deal with a problem? Do It Yourself! What we need: Official guidelines Adobe Photoshop and basic editing skills Creativity and inspiration Official Google Play guidelines: https://support.google.com/googleplay/android-developer/answer/9866151?hl=en The most important for us from the Screenshots section: Edit excess elements in the notification bar before submitting. Do not show service providers or notifications. The ## A CTO's Personal Journey Through Startup Leadership and Development DevFeed: [A CTO's Personal Journey Through Startup Leadership and Development]() Original publisher: [Read original article]() Author: Yonatan (Yoni) Levin Published: 2018-08-28T19:06:14Z Content type: opinion Language: en Sources: [Stories by Yonatan V. Levin on Medium]() Topics: [Development](), [Back end](), [Mobile]() Tags: [blog-post](), [cto](), [development](), [entrepreneurship](), [journey](), [personal-experience](), [product-management](), [startup](), [startups]() ### AI overview The author reflects on becoming a CTO, describing how the role differs between startups and large companies. The account covers responsibilities spanning product, technology, management, development, investors, and meetings, along with the author's experience moving from Android development into backend work and startup leadership. ### Source excerpt Around three years ago, a day I will never forget, a day that changed the course of my life. Marked the beginning of both my personal life (the day that my dear daughter was born) as well the day that the legendary entrepreneur and investor -- Eyal Gura called me and asked me to join the visionary team at KolGene together with Dan Faszczyk and build a revolutionary idea -- a marketplace for genetic tests which turnout to be a platform to managing all genetic tests of the hospital. And the rest is the history :) KolGene's magic This post will not focus on how we raised our first seed round (but we did!) Or about how we made a successful pivot and acquired our first customers (hard work!) and all of the other fuck-ups we encountered along the way. But rather, about my personal journey to becoming and being a CTO. I was recently invited to talk with Zell students about what it means being a CTO in a startup world. While preparing for the presentation I became inspired to share and write this blog post. Not the same CTO The first thing you need to understand is that a CTO position ranges from company to company (Like every position!). For example, a CTO of a small startup is very different to a CTO of large corporate company. The first requires you to do everything -- from the product, tech, managing and of course developing all by yourself. While simultaneously acquire investors and attend meetings. While a CTO in a large corporate company is far more tech only oriented, where your main responsibilities are to find out the right tech stack for a company product and explain it to the rest of the companies stakeholders. Prelude: Personal experience I was lucky enough to be able to observe various CTO's in different companies embarking on different stages: from corporate to fast-growing startups like Gett. But, since this is mostly about my journey let's talk about my personal journey to becoming a CTO. For years I was "the" go-to guy, the guy that everyone looked to for sol ## Review of 97 Things Every Software Architect Should Know DevFeed: [Review of 97 Things Every Software Architect Should Know]() Original publisher: [Read original article]() Author: Federico Published: 2018-06-06T23:06:00Z Content type: opinion Language: en Sources: [Federico Cargnelutti]() Topics: [Architecture & Design](), [Software Engineering](), [Software](), [Development]() Tags: [advice](), [architecture-design](), [book](), [personal-experience](), [software-architecture](), [software-engineering]() ### AI overview A personal review of 97 Things Every Software Architect Should Know, a compilation of advice from more than 40 software architects. The article highlights lessons about communication, complexity, developer empowerment, and balancing technical and organizational concerns, while noting that the book is not an in-depth theoretical work. ### Source excerpt I've finally had a chance to read a book I bought a while ago called "97 Things Every Software Architect Should Know - Collective Wisdom from the Experts". Not the shortest title for a book, but very descriptive. I bought this book at the OSCON Conference in Portland last year. It's an interesting book and [...] ## The Other Side of Stack Overflow DevFeed: [The Other Side of Stack Overflow]() Original publisher: [Read original article]() Author: Márton Braun Published: 2018-06-02T19:00:00Z Content type: opinion Language: en Sources: [zsmb.co]() Topics: [Stack Overflow](), [Kotlin]() Tags: [android](), [competition](), [kotlin](), [marton-braun](), [personal-experience](), [real-time](), [stack-overflow](), [thoughts](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview A personal account of answering questions on Stack Overflow, primarily under the Kotlin tag, after more than a year of participation. The author discusses reputation, badges, competition, and the motivation to answer questions quickly. ### Source excerpt My experiences and thoughts after using Stack Overflow from the other side for over a year now, answering questions mostly under the Kotlin tag. ## How to Become a Great Front-End Engineer DevFeed: [How to Become a Great Front-End Engineer]() Original publisher: [Read original article]() Published: 2015-08-02T22:39:17Z Content type: opinion Language: en Sources: [Philip Walton]() Topics: [Front end](), [Web Development](), [CSS](), [JavaScript](), [Code]() Tags: [advice](), [code-reviews](), [css](), [front-end](), [javascript](), [personal-experience]() ### AI overview The article argues that becoming a great front-end engineer depends less on memorized knowledge than on how you think, acquire knowledge, and use it to solve everyday problems. It emphasizes understanding the causes of issues in CSS and JavaScript instead of relying on trial and error. ### Source excerpt I recently received an email from a reader of my blog that, for whatever reason, really got me thinking. Here's what it said: Hi Philip, is it okay to ask how you become a great front-end engineer? Any advice?