Spacing the Cans
6 by hams-andwich | 2 comments on Hacker News.
Sunday, March 31, 2024
Saturday, March 30, 2024
Friday, March 29, 2024
New top story on Hacker News: Beware Scaling on AWS in Early Days
Beware Scaling on AWS in Early Days
9 by Kalanos | 3 comments on Hacker News.
During my first month on AWS, I used AWS Batch a lot. AWS decided to bill me mid-month (for more than I utilized I should add) even though the cycle ends on the 31st. The transaction failed. Instead of contacting me to resolve the issue, AWS completely locked me out of the account. Card is also now locked due to "fraud." I've been trying to resolve this for a week now (closer to 3 weeks if you include quota-related tickets). It's Friday, and I have a demo with a Fortune 100 company next week. In order to get results for this demo, I need to run a lot of Batch jobs - not great. I shudder to think about what would happened if this had been a launch with paid customers. From their perspective, I get that crypto miners probably sign up and cancel their credit cards, but I was just using the cloud as intended. I had multiple tickets related to resource quotas that explained why I was using the cloud.
9 by Kalanos | 3 comments on Hacker News.
During my first month on AWS, I used AWS Batch a lot. AWS decided to bill me mid-month (for more than I utilized I should add) even though the cycle ends on the 31st. The transaction failed. Instead of contacting me to resolve the issue, AWS completely locked me out of the account. Card is also now locked due to "fraud." I've been trying to resolve this for a week now (closer to 3 weeks if you include quota-related tickets). It's Friday, and I have a demo with a Fortune 100 company next week. In order to get results for this demo, I need to run a lot of Batch jobs - not great. I shudder to think about what would happened if this had been a launch with paid customers. From their perspective, I get that crypto miners probably sign up and cancel their credit cards, but I was just using the cloud as intended. I had multiple tickets related to resource quotas that explained why I was using the cloud.
Thursday, March 28, 2024
Wednesday, March 27, 2024
Tuesday, March 26, 2024
Monday, March 25, 2024
New top story on Hacker News: Show HN: Auto-generate an OpenAPI spec by listening to localhost
Show HN: Auto-generate an OpenAPI spec by listening to localhost
12 by adawg4 | 1 comments on Hacker News.
Hey HN! We've developed OpenAPI AutoSpec, a tool for automatically generating OpenAPI specifications from localhost network traffic. It’s designed to simplify the creation of API documentation by just using your website or service, especially useful when you're pressed for time. Documenting endpoints one by one sucks. This project originated from us needing it at our past jobs when building 3rd-party integrations. It acts as a local server proxy that listens to your application’s HTTP traffic and automatically translates this into OpenAPI 3.0 specs, documenting endpoints, requests, and responses without much effort. Installation is straightforward with NPM, and starting the server only requires a few command-line arguments to specify how and where you want your documentation generated ex. npx autospec --portTo PORT --portFrom PORT --filePath openapi.json It's designed to work with any local website or application setup without extensive setup or interference with your existing code, making it flexible for different frameworks. We tried capturing network traffic on Chrome extension and it didn't help us catch the full picture of backend and frontend interactions. We aim in future updates to introduce features like HTTPS and OpenAPI 3.1 specification support. For more details and to get started, visit our GitHub page ( https://ift.tt/NxBwnjb ). We also have a Discord community ( https://ift.tt/qFv9Gfm ) for support and discussions around using OpenAPI AutoSpec effectively. We're excited to hear what you all think!
12 by adawg4 | 1 comments on Hacker News.
Hey HN! We've developed OpenAPI AutoSpec, a tool for automatically generating OpenAPI specifications from localhost network traffic. It’s designed to simplify the creation of API documentation by just using your website or service, especially useful when you're pressed for time. Documenting endpoints one by one sucks. This project originated from us needing it at our past jobs when building 3rd-party integrations. It acts as a local server proxy that listens to your application’s HTTP traffic and automatically translates this into OpenAPI 3.0 specs, documenting endpoints, requests, and responses without much effort. Installation is straightforward with NPM, and starting the server only requires a few command-line arguments to specify how and where you want your documentation generated ex. npx autospec --portTo PORT --portFrom PORT --filePath openapi.json It's designed to work with any local website or application setup without extensive setup or interference with your existing code, making it flexible for different frameworks. We tried capturing network traffic on Chrome extension and it didn't help us catch the full picture of backend and frontend interactions. We aim in future updates to introduce features like HTTPS and OpenAPI 3.1 specification support. For more details and to get started, visit our GitHub page ( https://ift.tt/NxBwnjb ). We also have a Discord community ( https://ift.tt/qFv9Gfm ) for support and discussions around using OpenAPI AutoSpec effectively. We're excited to hear what you all think!
Sunday, March 24, 2024
Saturday, March 23, 2024
Friday, March 22, 2024
Thursday, March 21, 2024
Wednesday, March 20, 2024
Tuesday, March 19, 2024
Monday, March 18, 2024
Sunday, March 17, 2024
Saturday, March 16, 2024
Friday, March 15, 2024
Thursday, March 14, 2024
Wednesday, March 13, 2024
Tuesday, March 12, 2024
Monday, March 11, 2024
New top story on Hacker News: Show HN: Async tasks in 350 lines of C
Show HN: Async tasks in 350 lines of C
21 by rkaehn | 1 comments on Hacker News.
Tasks are a primitive for asynchronous programming and an alternative to working with threads directly. Instead of creating a thread, performing work, then waiting on it using synchronization primitives, you only define a unit of work and let a scheduler decide when and where to execute it. The threads that the scheduler uses are created once and reused for many tasks throughout the program's lifetime. In most cases, creating and executing a task requires not even a single syscall and is a significantly faster operation than creating a thread, resulting in lower latency. Furthermore, tasks from different subsystems can be automatically interleaved by the scheduler, which is difficult to achieve manually with threads without communication between the subsystems. The library is written in standard C11 and only depends on the C POSIX library. It is designed to be easy to integrate into a project by just copying the header and simple enough to be understood in an afternoon.
21 by rkaehn | 1 comments on Hacker News.
Tasks are a primitive for asynchronous programming and an alternative to working with threads directly. Instead of creating a thread, performing work, then waiting on it using synchronization primitives, you only define a unit of work and let a scheduler decide when and where to execute it. The threads that the scheduler uses are created once and reused for many tasks throughout the program's lifetime. In most cases, creating and executing a task requires not even a single syscall and is a significantly faster operation than creating a thread, resulting in lower latency. Furthermore, tasks from different subsystems can be automatically interleaved by the scheduler, which is difficult to achieve manually with threads without communication between the subsystems. The library is written in standard C11 and only depends on the C POSIX library. It is designed to be easy to integrate into a project by just copying the header and simple enough to be understood in an afternoon.
Sunday, March 10, 2024
Saturday, March 9, 2024
Friday, March 8, 2024
Thursday, March 7, 2024
Wednesday, March 6, 2024
Tuesday, March 5, 2024
New top story on Hacker News: Show HN: NeedleDrop – Guess the movie from a song
Show HN: NeedleDrop – Guess the movie from a song
24 by wernah | 24 comments on Hacker News.
Backstory: I'm a product designer who's mostly worked for startups and now big tech, and I haven't really touched html/css for nearly a decade. I've worked closely with engineers my entire career but never really rolled the sleeves up and dived into a scripting language. I'd seen some engineers playing around with CodeGPT over a year ago when it launched–we huddled around a screen and tried to decide how quickly our jobs would be replaced by this new technology. At the time, we weren’t in any real danger, but I caught a glimpse of how well it understood prompts and stubbed out large amounts of code. For the past four or five years, I've played a hacky trivia game with family and friends where I play a song, and they have to guess the movie that features the song; Guess the Needle Drop. After many passionate debates and over-the-top celebrations fueled by my generation’s nostalgia for popular classic songs and films, people often told me that I needed to “build an app for this.” I started doodling in Figma before quickly starting to build the website in Node, and then read somewhere that it's a better approach to learn vanilla javascript before trying to benefit from frameworks like React, etc. So I started again with a static vanilla website and, piece by piece, built out each chunk of functionality I’d envisioned. My mind was consistently blown at how helpful ChatGPT was–far beyond my lofty expectations, even with all the AI hype. It was like having a 24/7 personal tutor for free. I rarely had to google console errors hoping that a Stack Overflow discussion catered to my exact scenario. With enough information, ChatGPT always knew what was wrong and explained in terms I could understand. The workflow went like this: I would describe the desired user experience, parse the code GPT suggested, copy it to my editor, and paste back any errors I came across along the way. The errors were abundant at the beginning, but I got better over time at anticipating issues. Perhaps my biggest takeaway was that I had to learn how to converse with ChatGPT: sometimes I would spend 10 minutes crafting a prompt, forcing me to fully understand and articulate my own line of thinking about what I was trying to achieve . Using ChatGPT to make a static local website is fairly trivial, but the deployment and automation stage is where I fully realised the scope of what I could achieve. As a product designer, I’ve had the luxury of listening to engineers discuss solutions without personally having to sweat the execution. Working solo I couldn’t stay in the periphery anymore. I kinda knew AWS was a whole thing. That git was non-negotiable. That having a staging server is sensible and that APIs could do a lot of the heavy lifting for me. I would sanity-check with ChatGPT whether I understood these tools correctly and whether it was appropriate to use them for what I was building. A few of the things that initially intimidated me but I ended up working out: - GitHub Actions workflows - AWS hosting and CloudFront - Route 53 DNS hosting - SSL certificates - Implementing fuzzy search - LocalStorage and JSON manipulation - Even some basic python to scrub data It’s a fairly basic game, and for anyone sneaking a look with the inspector, it’s a dog’s div soup breakfast served with a side of spaghetti logic. But it still goes to show how much AI seems like a learning steroid.
24 by wernah | 24 comments on Hacker News.
Backstory: I'm a product designer who's mostly worked for startups and now big tech, and I haven't really touched html/css for nearly a decade. I've worked closely with engineers my entire career but never really rolled the sleeves up and dived into a scripting language. I'd seen some engineers playing around with CodeGPT over a year ago when it launched–we huddled around a screen and tried to decide how quickly our jobs would be replaced by this new technology. At the time, we weren’t in any real danger, but I caught a glimpse of how well it understood prompts and stubbed out large amounts of code. For the past four or five years, I've played a hacky trivia game with family and friends where I play a song, and they have to guess the movie that features the song; Guess the Needle Drop. After many passionate debates and over-the-top celebrations fueled by my generation’s nostalgia for popular classic songs and films, people often told me that I needed to “build an app for this.” I started doodling in Figma before quickly starting to build the website in Node, and then read somewhere that it's a better approach to learn vanilla javascript before trying to benefit from frameworks like React, etc. So I started again with a static vanilla website and, piece by piece, built out each chunk of functionality I’d envisioned. My mind was consistently blown at how helpful ChatGPT was–far beyond my lofty expectations, even with all the AI hype. It was like having a 24/7 personal tutor for free. I rarely had to google console errors hoping that a Stack Overflow discussion catered to my exact scenario. With enough information, ChatGPT always knew what was wrong and explained in terms I could understand. The workflow went like this: I would describe the desired user experience, parse the code GPT suggested, copy it to my editor, and paste back any errors I came across along the way. The errors were abundant at the beginning, but I got better over time at anticipating issues. Perhaps my biggest takeaway was that I had to learn how to converse with ChatGPT: sometimes I would spend 10 minutes crafting a prompt, forcing me to fully understand and articulate my own line of thinking about what I was trying to achieve . Using ChatGPT to make a static local website is fairly trivial, but the deployment and automation stage is where I fully realised the scope of what I could achieve. As a product designer, I’ve had the luxury of listening to engineers discuss solutions without personally having to sweat the execution. Working solo I couldn’t stay in the periphery anymore. I kinda knew AWS was a whole thing. That git was non-negotiable. That having a staging server is sensible and that APIs could do a lot of the heavy lifting for me. I would sanity-check with ChatGPT whether I understood these tools correctly and whether it was appropriate to use them for what I was building. A few of the things that initially intimidated me but I ended up working out: - GitHub Actions workflows - AWS hosting and CloudFront - Route 53 DNS hosting - SSL certificates - Implementing fuzzy search - LocalStorage and JSON manipulation - Even some basic python to scrub data It’s a fairly basic game, and for anyone sneaking a look with the inspector, it’s a dog’s div soup breakfast served with a side of spaghetti logic. But it still goes to show how much AI seems like a learning steroid.
Monday, March 4, 2024
Sunday, March 3, 2024
Saturday, March 2, 2024
Friday, March 1, 2024
New top story on Hacker News: Ask HN: Who wants to be hired? (March 2024)
Ask HN: Who wants to be hired? (March 2024)
22 by whoishiring | 86 comments on Hacker News.
Share your information if you are looking for work. Please use this format: Location: Remote: Willing to relocate: Technologies: Résumé/CV: Email: Readers: please only email these addresses to discuss work opportunities.
22 by whoishiring | 86 comments on Hacker News.
Share your information if you are looking for work. Please use this format: Location: Remote: Willing to relocate: Technologies: Résumé/CV: Email: Readers: please only email these addresses to discuss work opportunities.