The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Hellō, a cooperative approach for online identity
We are looking for feedback on a novel way to build and run a service for you to manage and share your identity.<p>Demo: <a href="https://greenfielddemo.com" rel="nofollow">https://greenfielddemo.com</a>
Show HN: Hellō, a cooperative approach for online identity
We are looking for feedback on a novel way to build and run a service for you to manage and share your identity.<p>Demo: <a href="https://greenfielddemo.com" rel="nofollow">https://greenfielddemo.com</a>
Show HN: A beginner’s guide to finding user needs
<a href="https://urbook.fordes.de/" rel="nofollow">https://urbook.fordes.de/</a><p>…a free/libré book about UX research with qualitative methods on motivations, activities written for UX researchers, UX designers and product managers.<p>I have been writing on this book since about 2010 and did a large rewrite during the first half of 2022. (I initally planned this with a bigger tech publisher).<p>This is the link to the full book for online reading: <a href="https://jdittrich.github.io/userNeedResearchBook/" rel="nofollow">https://jdittrich.github.io/userNeedResearchBook/</a> (it’s one long page, so it might take a bit to load)
Show HN: A beginner’s guide to finding user needs
<a href="https://urbook.fordes.de/" rel="nofollow">https://urbook.fordes.de/</a><p>…a free/libré book about UX research with qualitative methods on motivations, activities written for UX researchers, UX designers and product managers.<p>I have been writing on this book since about 2010 and did a large rewrite during the first half of 2022. (I initally planned this with a bigger tech publisher).<p>This is the link to the full book for online reading: <a href="https://jdittrich.github.io/userNeedResearchBook/" rel="nofollow">https://jdittrich.github.io/userNeedResearchBook/</a> (it’s one long page, so it might take a bit to load)
Show HN: A beginner’s guide to finding user needs
<a href="https://urbook.fordes.de/" rel="nofollow">https://urbook.fordes.de/</a><p>…a free/libré book about UX research with qualitative methods on motivations, activities written for UX researchers, UX designers and product managers.<p>I have been writing on this book since about 2010 and did a large rewrite during the first half of 2022. (I initally planned this with a bigger tech publisher).<p>This is the link to the full book for online reading: <a href="https://jdittrich.github.io/userNeedResearchBook/" rel="nofollow">https://jdittrich.github.io/userNeedResearchBook/</a> (it’s one long page, so it might take a bit to load)
Show HN: My book for programmers called “Junior to Senior” was published today
After a four year journey, the book I wrote to help junior and mid-level programmers earn their first promotion was published today . The book is titled Junior to Senior: Career Advice for the Ambitious Programmer and is now available on Holloway’s website[0].<p>I truly believe that soft-skills are what makes the difference between a good programmer and a great one. I also believe that anyone can learn the soft-skills needed to accelerate their programming career.<p>I wish I’d had better resources to learn these things in the early years of my career and I’m hoping this book will become a useful resource for the next generation of programmers to build successful careers.<p>What this book covers:<p>Choosing a career path: generalist vs. specialist<p>What makes you a senior engineer?<p>How to deal with feeling like an impostor<p>How to build trust and work with your manager<p>How to recover when you make a mistake, and what to do during incidents<p>How to ask better questions<p>How to read and understand unfamiliar code<p>How to add value to your team and company<p>How to identify and manage risk<p>How to deliver better results<p>How to communicate more effectively with both technical and non-technical audiences<p>The importance of a healthy work-life balance<p>How to ask for a promotion, and how to prepare for it<p>I wrote this book because these soft-skills are rarely taught in coding bootcamps or computer science degrees, yet they are critical to every programmer’s career trajectory. Almost every programmer I know, including me, had to learn and develop these soft-skills on the job. It took hard work and a lot of trial and error to learn how to communicate my ideas effectively, navigate office politics, manage risk, and so many other things that programmers encounter in their jobs today.<p>Get instant lifetime access at holloway.com. Use this link for a launch discount:<p>[0]: <a href="https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUNCH" rel="nofollow">https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUN...</a>
Show HN: My book for programmers called “Junior to Senior” was published today
After a four year journey, the book I wrote to help junior and mid-level programmers earn their first promotion was published today . The book is titled Junior to Senior: Career Advice for the Ambitious Programmer and is now available on Holloway’s website[0].<p>I truly believe that soft-skills are what makes the difference between a good programmer and a great one. I also believe that anyone can learn the soft-skills needed to accelerate their programming career.<p>I wish I’d had better resources to learn these things in the early years of my career and I’m hoping this book will become a useful resource for the next generation of programmers to build successful careers.<p>What this book covers:<p>Choosing a career path: generalist vs. specialist<p>What makes you a senior engineer?<p>How to deal with feeling like an impostor<p>How to build trust and work with your manager<p>How to recover when you make a mistake, and what to do during incidents<p>How to ask better questions<p>How to read and understand unfamiliar code<p>How to add value to your team and company<p>How to identify and manage risk<p>How to deliver better results<p>How to communicate more effectively with both technical and non-technical audiences<p>The importance of a healthy work-life balance<p>How to ask for a promotion, and how to prepare for it<p>I wrote this book because these soft-skills are rarely taught in coding bootcamps or computer science degrees, yet they are critical to every programmer’s career trajectory. Almost every programmer I know, including me, had to learn and develop these soft-skills on the job. It took hard work and a lot of trial and error to learn how to communicate my ideas effectively, navigate office politics, manage risk, and so many other things that programmers encounter in their jobs today.<p>Get instant lifetime access at holloway.com. Use this link for a launch discount:<p>[0]: <a href="https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUNCH" rel="nofollow">https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUN...</a>
Show HN: My book for programmers called “Junior to Senior” was published today
After a four year journey, the book I wrote to help junior and mid-level programmers earn their first promotion was published today . The book is titled Junior to Senior: Career Advice for the Ambitious Programmer and is now available on Holloway’s website[0].<p>I truly believe that soft-skills are what makes the difference between a good programmer and a great one. I also believe that anyone can learn the soft-skills needed to accelerate their programming career.<p>I wish I’d had better resources to learn these things in the early years of my career and I’m hoping this book will become a useful resource for the next generation of programmers to build successful careers.<p>What this book covers:<p>Choosing a career path: generalist vs. specialist<p>What makes you a senior engineer?<p>How to deal with feeling like an impostor<p>How to build trust and work with your manager<p>How to recover when you make a mistake, and what to do during incidents<p>How to ask better questions<p>How to read and understand unfamiliar code<p>How to add value to your team and company<p>How to identify and manage risk<p>How to deliver better results<p>How to communicate more effectively with both technical and non-technical audiences<p>The importance of a healthy work-life balance<p>How to ask for a promotion, and how to prepare for it<p>I wrote this book because these soft-skills are rarely taught in coding bootcamps or computer science degrees, yet they are critical to every programmer’s career trajectory. Almost every programmer I know, including me, had to learn and develop these soft-skills on the job. It took hard work and a lot of trial and error to learn how to communicate my ideas effectively, navigate office politics, manage risk, and so many other things that programmers encounter in their jobs today.<p>Get instant lifetime access at holloway.com. Use this link for a launch discount:<p>[0]: <a href="https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUNCH" rel="nofollow">https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUN...</a>
Show HN: Komorebi – A tiling window manager for Windows 10/11 written in Rust
Show HN: Komorebi – A tiling window manager for Windows 10/11 written in Rust
Show HN: Komorebi – A tiling window manager for Windows 10/11 written in Rust
Show HN: Komorebi – A tiling window manager for Windows 10/11 written in Rust
Show HN: Komorebi – A tiling window manager for Windows 10/11 written in Rust
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
Hi HN! We’re Aleem, Chris, Borys, Meichen and Zach from Streak (YC S11) and today we’re open sourcing our InboxSDK <a href="https://www.inboxsdk.com" rel="nofollow">https://www.inboxsdk.com</a>, which makes it easy to build apps for Gmail.<p>Over 1.8B users spend their days in Gmail! Having your app built into the Gmail workflow is a better user experience and gives you great user retention. InboxSDK gives you a high-level, declarative API to insert your UI into Gmail without having to directly manipulate the DOM yourself. End users install a browser extension to use your app.<p>The SDK can add UI to multiple areas of Gmail. For example, adding a button is as simple as:<p><pre><code> composeView.addButton({
title: "My Nifty Button!",
iconUrl: 'https://example.com/foo.png',
onClick: function(event) {
event.composeView.insertTextIntoBodyAtCursor('Hello World!');
},
});
</code></pre>
InboxSDK enables you to add info to the sidebar on threads, add items in the left navigation tree, insert results into the search box, navigate to full page routes, add toolbar buttons to the compose window, add label indicators to thread list views and many more. You can see some examples in my comment posted below.<p>Hubspot, Dropbox, Giphy, Clickup, Loom, Todoist, Clearbit and our own Streak have all built apps using the InboxSDK. The InboxSDK is open source dual-licensed under the MIT and Apache 2.0 licenses for maximum flexibility.<p>Why use the InboxSDK over rolling it yourself? Several reasons: (1) it’s hard to do DOM manipulation in a performant way; (2) you need to handle all the different configurations of Gmail—there are a lot, and they change often: e.g. conversation view on/off, multiple inboxes, chat left/right, personal vs Workspace accounts; (3) You have to maintain compatibility with tons of other Gmail extensions so you don’t stomp over each other.<p>On a technical level, the InboxSDK handles all the DOM watching and manipulation, XHR interception, multiple extension coordination, and exposes a high level API to developers. We make use of page-parser-tree, another package we open sourced that helps detect elements on the page performantly. The trickiest bit we handle is intercepting and modifying network requests that Gmail makes in order to support several of the APIs we expose.<p>We’ve been building this SDK for years - it’s what powers Streak (www.streak.com), an 8 figure ARR SaaS business. We built the InboxSDK for ourselves because we wanted to separate our logic for wrangling Gmail from that of our app. Several years ago we let developers use a hosted version of our SDK. We didn’t want anyone else to go through the same pain to integrate deeply with Gmail. There were two unexpected benefits:<p>It vastly increased the number of end users (20M+) using apps built on our SDK. This gave us significant leverage with Google. They are super supportive of the SDK and give us early access to several builds to ensure the SDK doesn’t break when they make updates to Gmail.<p>We spent an ungodly amount of time maintaining compatibility with other Gmail extensions. Once the InboxSDK became a defacto standard, all the apps (currently >1000) that used it were instantly compatible (the InboxSDK operates under the model that there will be several extensions running at the same time and it elects a leader to route all modification through).<p>Why open source it now? First, several companies were nervous about us hosting the SDK. We mainly did this so that every extension was running the same version of the SDK, but with the recent Chrome manifest V3 changes, remote code execution is no longer supported. Not hosting the SDK removed the primary reason why the project needed to be closed source. We do need to figure out a new way of keeping all developers relatively up to date on the latest version of the SDK, <i>any ideas?</i><p>We’d love feedback! The repo is <a href="https://github.com/inboxSDK/inboxsdk" rel="nofollow">https://github.com/inboxSDK/inboxsdk</a>, and the docs are: <a href="https://inboxsdk.github.io/inboxsdk-docs" rel="nofollow">https://inboxsdk.github.io/inboxsdk-docs</a>
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
Hi HN! We’re Aleem, Chris, Borys, Meichen and Zach from Streak (YC S11) and today we’re open sourcing our InboxSDK <a href="https://www.inboxsdk.com" rel="nofollow">https://www.inboxsdk.com</a>, which makes it easy to build apps for Gmail.<p>Over 1.8B users spend their days in Gmail! Having your app built into the Gmail workflow is a better user experience and gives you great user retention. InboxSDK gives you a high-level, declarative API to insert your UI into Gmail without having to directly manipulate the DOM yourself. End users install a browser extension to use your app.<p>The SDK can add UI to multiple areas of Gmail. For example, adding a button is as simple as:<p><pre><code> composeView.addButton({
title: "My Nifty Button!",
iconUrl: 'https://example.com/foo.png',
onClick: function(event) {
event.composeView.insertTextIntoBodyAtCursor('Hello World!');
},
});
</code></pre>
InboxSDK enables you to add info to the sidebar on threads, add items in the left navigation tree, insert results into the search box, navigate to full page routes, add toolbar buttons to the compose window, add label indicators to thread list views and many more. You can see some examples in my comment posted below.<p>Hubspot, Dropbox, Giphy, Clickup, Loom, Todoist, Clearbit and our own Streak have all built apps using the InboxSDK. The InboxSDK is open source dual-licensed under the MIT and Apache 2.0 licenses for maximum flexibility.<p>Why use the InboxSDK over rolling it yourself? Several reasons: (1) it’s hard to do DOM manipulation in a performant way; (2) you need to handle all the different configurations of Gmail—there are a lot, and they change often: e.g. conversation view on/off, multiple inboxes, chat left/right, personal vs Workspace accounts; (3) You have to maintain compatibility with tons of other Gmail extensions so you don’t stomp over each other.<p>On a technical level, the InboxSDK handles all the DOM watching and manipulation, XHR interception, multiple extension coordination, and exposes a high level API to developers. We make use of page-parser-tree, another package we open sourced that helps detect elements on the page performantly. The trickiest bit we handle is intercepting and modifying network requests that Gmail makes in order to support several of the APIs we expose.<p>We’ve been building this SDK for years - it’s what powers Streak (www.streak.com), an 8 figure ARR SaaS business. We built the InboxSDK for ourselves because we wanted to separate our logic for wrangling Gmail from that of our app. Several years ago we let developers use a hosted version of our SDK. We didn’t want anyone else to go through the same pain to integrate deeply with Gmail. There were two unexpected benefits:<p>It vastly increased the number of end users (20M+) using apps built on our SDK. This gave us significant leverage with Google. They are super supportive of the SDK and give us early access to several builds to ensure the SDK doesn’t break when they make updates to Gmail.<p>We spent an ungodly amount of time maintaining compatibility with other Gmail extensions. Once the InboxSDK became a defacto standard, all the apps (currently >1000) that used it were instantly compatible (the InboxSDK operates under the model that there will be several extensions running at the same time and it elects a leader to route all modification through).<p>Why open source it now? First, several companies were nervous about us hosting the SDK. We mainly did this so that every extension was running the same version of the SDK, but with the recent Chrome manifest V3 changes, remote code execution is no longer supported. Not hosting the SDK removed the primary reason why the project needed to be closed source. We do need to figure out a new way of keeping all developers relatively up to date on the latest version of the SDK, <i>any ideas?</i><p>We’d love feedback! The repo is <a href="https://github.com/inboxSDK/inboxsdk" rel="nofollow">https://github.com/inboxSDK/inboxsdk</a>, and the docs are: <a href="https://inboxsdk.github.io/inboxsdk-docs" rel="nofollow">https://inboxsdk.github.io/inboxsdk-docs</a>
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
Hi HN! We’re Aleem, Chris, Borys, Meichen and Zach from Streak (YC S11) and today we’re open sourcing our InboxSDK <a href="https://www.inboxsdk.com" rel="nofollow">https://www.inboxsdk.com</a>, which makes it easy to build apps for Gmail.<p>Over 1.8B users spend their days in Gmail! Having your app built into the Gmail workflow is a better user experience and gives you great user retention. InboxSDK gives you a high-level, declarative API to insert your UI into Gmail without having to directly manipulate the DOM yourself. End users install a browser extension to use your app.<p>The SDK can add UI to multiple areas of Gmail. For example, adding a button is as simple as:<p><pre><code> composeView.addButton({
title: "My Nifty Button!",
iconUrl: 'https://example.com/foo.png',
onClick: function(event) {
event.composeView.insertTextIntoBodyAtCursor('Hello World!');
},
});
</code></pre>
InboxSDK enables you to add info to the sidebar on threads, add items in the left navigation tree, insert results into the search box, navigate to full page routes, add toolbar buttons to the compose window, add label indicators to thread list views and many more. You can see some examples in my comment posted below.<p>Hubspot, Dropbox, Giphy, Clickup, Loom, Todoist, Clearbit and our own Streak have all built apps using the InboxSDK. The InboxSDK is open source dual-licensed under the MIT and Apache 2.0 licenses for maximum flexibility.<p>Why use the InboxSDK over rolling it yourself? Several reasons: (1) it’s hard to do DOM manipulation in a performant way; (2) you need to handle all the different configurations of Gmail—there are a lot, and they change often: e.g. conversation view on/off, multiple inboxes, chat left/right, personal vs Workspace accounts; (3) You have to maintain compatibility with tons of other Gmail extensions so you don’t stomp over each other.<p>On a technical level, the InboxSDK handles all the DOM watching and manipulation, XHR interception, multiple extension coordination, and exposes a high level API to developers. We make use of page-parser-tree, another package we open sourced that helps detect elements on the page performantly. The trickiest bit we handle is intercepting and modifying network requests that Gmail makes in order to support several of the APIs we expose.<p>We’ve been building this SDK for years - it’s what powers Streak (www.streak.com), an 8 figure ARR SaaS business. We built the InboxSDK for ourselves because we wanted to separate our logic for wrangling Gmail from that of our app. Several years ago we let developers use a hosted version of our SDK. We didn’t want anyone else to go through the same pain to integrate deeply with Gmail. There were two unexpected benefits:<p>It vastly increased the number of end users (20M+) using apps built on our SDK. This gave us significant leverage with Google. They are super supportive of the SDK and give us early access to several builds to ensure the SDK doesn’t break when they make updates to Gmail.<p>We spent an ungodly amount of time maintaining compatibility with other Gmail extensions. Once the InboxSDK became a defacto standard, all the apps (currently >1000) that used it were instantly compatible (the InboxSDK operates under the model that there will be several extensions running at the same time and it elects a leader to route all modification through).<p>Why open source it now? First, several companies were nervous about us hosting the SDK. We mainly did this so that every extension was running the same version of the SDK, but with the recent Chrome manifest V3 changes, remote code execution is no longer supported. Not hosting the SDK removed the primary reason why the project needed to be closed source. We do need to figure out a new way of keeping all developers relatively up to date on the latest version of the SDK, <i>any ideas?</i><p>We’d love feedback! The repo is <a href="https://github.com/inboxSDK/inboxsdk" rel="nofollow">https://github.com/inboxSDK/inboxsdk</a>, and the docs are: <a href="https://inboxsdk.github.io/inboxsdk-docs" rel="nofollow">https://inboxsdk.github.io/inboxsdk-docs</a>
Show HN: Open-Sourcing InboxSDK (YC S11) – Build Apps in Gmail
Hi HN! We’re Aleem, Chris, Borys, Meichen and Zach from Streak (YC S11) and today we’re open sourcing our InboxSDK <a href="https://www.inboxsdk.com" rel="nofollow">https://www.inboxsdk.com</a>, which makes it easy to build apps for Gmail.<p>Over 1.8B users spend their days in Gmail! Having your app built into the Gmail workflow is a better user experience and gives you great user retention. InboxSDK gives you a high-level, declarative API to insert your UI into Gmail without having to directly manipulate the DOM yourself. End users install a browser extension to use your app.<p>The SDK can add UI to multiple areas of Gmail. For example, adding a button is as simple as:<p><pre><code> composeView.addButton({
title: "My Nifty Button!",
iconUrl: 'https://example.com/foo.png',
onClick: function(event) {
event.composeView.insertTextIntoBodyAtCursor('Hello World!');
},
});
</code></pre>
InboxSDK enables you to add info to the sidebar on threads, add items in the left navigation tree, insert results into the search box, navigate to full page routes, add toolbar buttons to the compose window, add label indicators to thread list views and many more. You can see some examples in my comment posted below.<p>Hubspot, Dropbox, Giphy, Clickup, Loom, Todoist, Clearbit and our own Streak have all built apps using the InboxSDK. The InboxSDK is open source dual-licensed under the MIT and Apache 2.0 licenses for maximum flexibility.<p>Why use the InboxSDK over rolling it yourself? Several reasons: (1) it’s hard to do DOM manipulation in a performant way; (2) you need to handle all the different configurations of Gmail—there are a lot, and they change often: e.g. conversation view on/off, multiple inboxes, chat left/right, personal vs Workspace accounts; (3) You have to maintain compatibility with tons of other Gmail extensions so you don’t stomp over each other.<p>On a technical level, the InboxSDK handles all the DOM watching and manipulation, XHR interception, multiple extension coordination, and exposes a high level API to developers. We make use of page-parser-tree, another package we open sourced that helps detect elements on the page performantly. The trickiest bit we handle is intercepting and modifying network requests that Gmail makes in order to support several of the APIs we expose.<p>We’ve been building this SDK for years - it’s what powers Streak (www.streak.com), an 8 figure ARR SaaS business. We built the InboxSDK for ourselves because we wanted to separate our logic for wrangling Gmail from that of our app. Several years ago we let developers use a hosted version of our SDK. We didn’t want anyone else to go through the same pain to integrate deeply with Gmail. There were two unexpected benefits:<p>It vastly increased the number of end users (20M+) using apps built on our SDK. This gave us significant leverage with Google. They are super supportive of the SDK and give us early access to several builds to ensure the SDK doesn’t break when they make updates to Gmail.<p>We spent an ungodly amount of time maintaining compatibility with other Gmail extensions. Once the InboxSDK became a defacto standard, all the apps (currently >1000) that used it were instantly compatible (the InboxSDK operates under the model that there will be several extensions running at the same time and it elects a leader to route all modification through).<p>Why open source it now? First, several companies were nervous about us hosting the SDK. We mainly did this so that every extension was running the same version of the SDK, but with the recent Chrome manifest V3 changes, remote code execution is no longer supported. Not hosting the SDK removed the primary reason why the project needed to be closed source. We do need to figure out a new way of keeping all developers relatively up to date on the latest version of the SDK, <i>any ideas?</i><p>We’d love feedback! The repo is <a href="https://github.com/inboxSDK/inboxsdk" rel="nofollow">https://github.com/inboxSDK/inboxsdk</a>, and the docs are: <a href="https://inboxsdk.github.io/inboxsdk-docs" rel="nofollow">https://inboxsdk.github.io/inboxsdk-docs</a>
Show HN: We built a tool that automatically generates API tests
Hi, this is Mish and Sebastian.
We are working on Step CI - a fully automated API testing platform for developers.<p>Step CI works programming-language independent and for different API paradigms (REST, GraphQL, XML).<p>Our CLI and test runner are available on GitHub (<a href="https://github.com/stepci" rel="nofollow">https://github.com/stepci</a>) under the MPLv2 license.<p>Since our last launch, Step CI is now able to generate automated tests for your API based on your OpenAPI (Swagger) spec. This saves you a lot of time as you never have to write and maintain your tests again!<p>We would like to invite you to try our tool and give us feedback! Please star us on GitHub, if you like what we are working on!<p>We are very thankful for your attention and any feedback or suggestions we receive from you :)<p>Mish and Sebastian from Germany
Show HN: We built a tool that automatically generates API tests
Hi, this is Mish and Sebastian.
We are working on Step CI - a fully automated API testing platform for developers.<p>Step CI works programming-language independent and for different API paradigms (REST, GraphQL, XML).<p>Our CLI and test runner are available on GitHub (<a href="https://github.com/stepci" rel="nofollow">https://github.com/stepci</a>) under the MPLv2 license.<p>Since our last launch, Step CI is now able to generate automated tests for your API based on your OpenAPI (Swagger) spec. This saves you a lot of time as you never have to write and maintain your tests again!<p>We would like to invite you to try our tool and give us feedback! Please star us on GitHub, if you like what we are working on!<p>We are very thankful for your attention and any feedback or suggestions we receive from you :)<p>Mish and Sebastian from Germany
Kitchen Renovation ideas animation using Stable Diffusion [video]
Using stable diffusion to generate and walk through different kitchen renovation ideas.