messel

Funny response :). What's common sense to you, may be less than obvious to others.

Put another way, agreeing with the advice someone else gives doesn't make it bad advice.

Great question.

When I was a kid (11-12) I injured my neck and was pretty worried, stuck lying down, and my pop called 911 to ask for help. A neighbor two houses down was a volunteer fireman so he heard the call over the radio. He headed over and helped make my family and I much more calm while we waited for emergency professionals to show up.

Caring about the safety of people in your neighborhood is a great start. Technology playing a role feels like less of a gamble and more of an inevitability.

I consider this app as an extension of my senses. I get a push message when an emergency is happening nearby. Maybe I can help, maybe its none of my business, maybe I'll completely avoid that block. But I get a choice, where my earlier ignorance is no choice at all.

It's the technological equivalent of someone shouting for help. You can assist or not.

Disclaimer: I helped build the backend so I'm biased.

You nailed it, taking investor money and being guided by it to grow until your business breaks. Really appreciate your last paragraph.

Read this comment nodding, but it sounds like a zero sum system. There's got to be a better way to attract and enhance talented developers.

Totally agree, thought I was a solid engineer in my early-mid 20s. Had no idea how much I'd learn. I'm frightened by how much more I could learn now (42).

I waste much less time, still make silly mistakes, but much less often.

In my younger years (mid 90s), we respected and learned from the grey beards. Embrace it.

Hah! This is great.

"Wait all descriptors containing the letters 'ad' are ignored?"

"Madness."

"This is HTML!"

Pre IE, no simulation levels

This was a bunch of fun.

Notes:

Be useful, that's fine, no need to alter the world drastically.

Big Next shifts: AI & Genetic Modification (oh and a faster connection to our minds)

High probability of failure, not a problem. Tesla, Space X. Push the ball forward.

Democratization of AI is a best possible outcome (direct connection, we are the AI)

Looking forward to the exciting conclusion, did the author just get their first prof prog job? Does that make them good, or hireable, or are they the same? I don't believe so.

Maybe keep it going, and it'll get really interesting around years 5, 10, or even 20 past their first prof job.

Humans have a knack for adaption. We'll figure out the employment problems that result from automation and robotics. We'd make great pets.

I hope that some of this type of hands on expertise develops and is shared in places like this https://synshop.org/ (my friend Aakin who helps out there told me about it)

That's wild. The computer is cheaper than the adapters.

The heroku-> lambda path is what I was considering - so would love to hear more about any pain points etc. edited nvm read claudia.js. Reviewing that vs apex.run now. Thanks for open sourcing that deployment tool.

(repost from the blog comment thread. Would dig any feedback with HN readers who use lambda in production)

Here's the setup I'm hoping to leverage lambda for: light workers. I have kue.js/redis for submitting jobs to, and creating workers. My subscribed worker listeners will simple trigger lambda.invoke with json packages (no need to call or support http endpoints etc). No need for api gateway either.

I'm starting with apex.run as a deployment tool and writing/running all tests locally. I assumed local testing is doable by hitting the same func exports with mocked inputs - this could be off.

See any big hurdles with that usage plan?

As an aside, I've got a backlogged task to explore serverless, and their moving away from cloudformation shouldn't be an issue (assume terraform?)

Hahahaha. Should we be coding, reading about code, or doing fun non work stuff? Voting for the latter. Thanks for the wake up!

If you drill down far enough it's all binary or byte code. But on the way back up, there are variations of implementation in more than a single language.

Pseudo inception like self describing languages are close but never 100% self describing (this always blows my mind). Then there are languages implemented on top of C, and the many XVM languages (elixir built on the erlang virtual machine, JVM langs, etc)

Any particular language is almost always composed of multiple languages, so trying to craft one to solve all problems is an interesting problem.

The issue with general reviews is that they're not tailored to our tastes, and possibly more important, our momentary whims.

Better to have an option for a likeness score applied to reviewers as a filter.

Soma carried the brunt of that load, not unlike modern pain killers

Huge feature set, thanks.

Any news on deeper/more complex queries (chaining, or something like joins without rewriting our data in multiple places)

Or faster queries (server side I've seen some very slow .once calls taking hundreds of ms)?

Also I'd love some tips on how to better scale listener/trigger functions. I have many listeners (server side) and am migrating them to explicit client endpoint point functions to handle it horizontally (more api workers).

Ok. Try a different language :)?

A single language needed to solve all problems is a fallacy.

I don't see FPGA programming ousting c++, but expect higher level languages with strong parallel semantics to gain "market share". You can always call a dedicated process written in optimized c for the hottest components. Compose the rest in go, elixir, or any high level language (lisp).

Architectures will naturally gravitate to higher level languages that support cleaner composition. The tools and interfaces will push towards higher abstraction without impacting build or run time. Maybe this process is related to Kevin Kelly's inevitable. I'm an optimist here.

My super power.

During the week I walk a loop in the morning (9.5miles) and when I have to commute to NY, it's a few miles downtown,a brief lunchtime wander around, and a swift walk back up in the evening to Penn.

Part of my walking is for health reasons, part is due to a need to move about, part is meditation. My mind wanders while out for a good walk, it's the most liberating feeling I experience.

My wife and I go for longer walks on the weekend, sometimes we chat, but often time we walk together in silence. It's a guilty pleasure.

Read this again with the voice as Nick Offerman

Fantastic read, very curious about post fertility life and population stabilization.

Looks good. Wonder why these benchmarks never include an actual database. I'm using firebase with nodejs and no matter how many requests per second my server can respond with, it's ultimately constrained by data requests and memory (ie how many connections can I wait on).

When I see numbers like 50k requests per second it's meaningless, unless I have no database or some kind of in memory cache only db.

Cool, thanks for sharing it here

First impressions: felt great, supported a ton of languages, has some very powerful looking debug tools (for nodejs)

Anyone have any luck creating an extension with mac classic? Tried manually adding the theme (following their doc) and no luck. Then created a msft account to try and create a package to install it as an extension and couldn't get past 401 on create-publisher.

Back to sublime for now, but I'll keep an eye on this one.

Looks like the beginnings of a sync adapter (android) except limited to a single app.

I need to better understand the use of NSOperationQueue and why the speaker hates on singletons vs dependency injection.

Singleton: allocs first time its needed, exists for the life of the app. Need to be mindful of how much data it stores, and thread safety

Dependency Injection: allocs and passes to other view controllers as needed. Still need to be mindful of data it stores, and thread safety.

The story at 27min or so is a keeper. Many Async->Async->Async calls all launching independently and updating the viewcontrollers without any control flow.

One comment on higer taxes + UBI. This curve is interesting to think about, slowly ramping or fixed percentage? I prefer simpler when it comes to large scale concepts, but maybe it needs to ramp up and affect all income equally (long term capital gains as well).