Skywing

I was looking into using lambda functions called in response to an S3 event. Specifically, I wanted to create a record in my SQL database after a file is uploaded to S3. Users are uploading directly to S3 using pre-signed requests, so I needed some way to step in and create a database record after they actually perform the upload to S3. S3 supports this via several methods, one of which is the lambda functions, but when looking into lambda functions there was no way to have the code access my SQL database internally, I would have had to make my SQL database open to the world. I didn't find any IAM rules etc to enable lambda functions to access my SQL database resources. I'd be curious to see how this is handled by this JAWS work flow.

Part of the beauty of markdown, imo, is its simplicity. If I ever have a question about markdown syntax, I can glance at the original docs and have the answer in less than 30 seconds.

Why would this be free forever? Seems like something you could charge at least a small, one-time fee for.

Is this just a long way of saying that you shouldn't execute code, downloaded using curl, like this?

I currently write software for an e-discovery company. Most tasks that our software is expected to be able to perform are simple-sounding tasks, at first glance, such as ...

1. extracting documents from within other documents (attachments out of an email, files out of a zip, embedded excels out of a word doc, images out of a powerpoint, etc)

2. convert all said documents to some kind of standard media format so that the native viewing applications are not needed (all said document types to png, or pdf, or tif)

3. allow full-text searching across all electronic files

With these kinds of tasks available as an automated feature, the real product would just allow a bunch of attorneys to review the documents and apply tags or labels to them. Once they've gone through all the documents, there is generally an output from the system that summarizes their work and provides the relevant documents, notes, etc.

Over the years of writing this kind of software, we've encountered a never-ending amount of complicates with file types, feature requests, etc. The real complexities with this kind of software is making your software work for a large number of customers. Every customer probably has a different idea about what they want this kind of tool to do for them.

A lot of explanations here about how other people learned to use programming as a tool for themselves, but everybody is different. One person's analogy for using code might not work for you. You have to discover what works for you on your own. Sure, keep the other analogies and things in mind, and ask yourself if you can relate, as you progress through your own journey. Everything is relative though, and your experiences are what make you unique and valuable to the community as a whole. Maybe you're the next Bob Ross of JavaScript - we want you to be. So, don't aim to mimic somebody else's experiences because that'd just be an injustice and it'd also take away from what makes this journey so rewarding. I suggest just visualizing some end goal of yours. You want to make a website that offers some kind of service of something? Visualize that site and break it down into chunks. Finally, dive in head first. Just start coding on it. Don't give a single thought to whether or not it's as good as somebody else's code. Don't worry about if it's the best it could be, yet. All you need to do is connect the dots, mentally, and play with the legos. Focus on hacking together something that, in the end, resembles that mental picture you had. Once you're there, a large portion of your original question will have pretty much been answered - you'll have use code to solve some problem. All that remains is to figure out how to improve. That's all any of us are doing - trying to improve.

sigh time to start looking into Go

With what purpose? What's the significance of this? node is also node with many of the key contributors.

I'm not very familiar with React or Angular's history, but wasn't the idea of diffing a virtual DOM something that React kind of came up with, after Angular had been around? Isn't your comment kind of unfair, because you have the advantage of hindsight?

I've owned and used both a 4k monitor and a 144 Hz refresh rate monitor. I personally value the higher refresh rate over the higher resolution. My 4k monitor is actually difficult for me to use, because it feels like the software has not caught up to the resolution yet. Very little is optimized for 4k desktops, yet.

I've never worked on a larger javascript project, so I'm not sure why you'd care if your front-end js renders on the server (i'm assuming this means no visual browser). Is this for purposes of automated testing?

I remember a day where I was proud that my C projects took a few seconds to compile. Made me feel like I had written something with some umph to it.

While watching the video, I kept hoping he'd look down at the cubes and "jump down" to them. Like, enable gravity and jump down onto the cubes as a player. That'd have been awesome.

Good point. I was taking the parent's post literally, where jquery.com was used.

If somebody has the ability to change the script file, what's to stop them from changing that hash, too?

So, yea I think this is a great thing and I don't mind JSX. It has been a pleasure to use ... I think. I can't help but be reminded about original PHP, though. When PHP was new, you could write PHP but then you could also write your markup in the same file. The end result was a bunch of bad PHP and markup. JSX is not quite is liberal, but it's along the same vein. You kind of have markup in your Javascript, now (I say now, but I guess you did before in some cases where you built DOM elements with JS). Especially with components that also have HTML-literal content in them, like labels and text and stuff. Like, to literally change the text in a form or something, you might have to go edit your Javascript file ... no wait, your JSX file to change that. Javascript is also already enough of a pandoras box, in regards to common patterns and "how to do X or Y." I don't really know how to articulate my thoughts on it yet, but I feel like I lean towards rather not having to look at code with JSX in it than having to do so.

What about the weekends? It only take an hour to two to get some darker skin. It's not rocket science.

Chrome's bookmarks auto sync to your gmail account, if you sign in to Chrome. I've been using it to replace Delicious for quite a long time, now.

I wrote the exact same thing about 3 years ago, according to HN timestamps: https://news.ycombinator.com/item?id=2102790

I also had an arbitrary chat radius, initially. After feedback and testing, I made it so that the radius shrank as more people were online. So, if 1 person was on the site the radius was non-existent - it'd show the next few people regardless of location. As enough people opened the website, the radius would begin to shrink based on your own location to include at least 1 other person as close to you as possible, down to a minimum of like 20 miles. This way, if 10 people were online in San Francisco, but I was building the thing in Dallas, then I could at least join in the discussion in San Francisco until more people in Dallas joined in.

Looking back, to call my old thing a start-up in that post was hilarious. I also learned that my concept, being real-time location-based ephemeral anonymous chat (buzzwords jeez), has a severe chicken and egg problem. It's damn near impossible to reach critical mass for long enough for the chat radiuses to create any opportunity for local discussion. I also learned that it really needed to be a native mobile app, instead of a website. Only tech savvy people really knew what was going on, in regards to enabling location services in browsers.

In the end, I had wished I just made some sort of non-realtime location-based tagging service, instead. Instead of real-time chat, just have location-based notes that you can leave somewhere in a very small precise proximity. That way there's no need for a critical mass of users all at the same time.

Edit: it looks like by the time I posted it to HN even, I had began changing to the non-real-time version. it originally was purely real-time chat. the code is on github: https://github.com/ryancole/geohello.com

Arrington is still around? When will he go away? Thankfully techcrunch is mostly irrelevant lately, but ugh seeing Arrington posts is enough to last awhile.

Github with Jekyll?

As a truck owner, is there a way to make sure that I never end up on this website? :) Just kidding. Any truck owner knows the joys of having every non-truck-owner ask to borrow the truck.

Based on my current connections, and experience, I can't fully see myself ever getting the chance to do so, but I'd love to have the opportunity to work on similar problems - at Facebook or anywhere. I've always loved working on lower level problems such as this. I learned to program by writing computer game hacks, reverse engineering games and coding in C / ASM. Currently, I find myself writing C# every day for a small company at which nobody understands a single word I say about programming.

Hey, I just wanted to sign-in and comment to say that at some point in the past, I found myself reading your book website. I do recall back then it had way less chapters, and I remember hoping that it'd find its way to completion eventually. I see a lot of new chapters. Great work! Very good resource, too.

Who wouldn't?

You won't read that book again because the ending's just too hard to take.

Oh give it a break. Be rude if you want to be. Not like anybody actually cares anyway.

Am I the only one who rolls my eyes at blog posts like these? Oh boo hoo.

Couldn't this be gamed somehow? Just create some catch-all email, and send $1 to as many as you want? I'm guessing they probably restrict a single dollar to 1 debit card number, though. Wonder if there's a way around that? Oh well.

But then isn't this just the other way around? Now will YC invest in the company if they see that they're not raising much from outside investors?