Which means effectively zero over-the-air reception in parts of the Mission. Lesson learned during a Super Bowl party the 2010s.
258 karma · joined June 29, 2012
Which means effectively zero over-the-air reception in parts of the Mission. Lesson learned during a Super Bowl party the 2010s.
1. You write the book as part of your job during the workday. 2. Your company buys the published book to distribute at events and conferences for free. 3. The book seems successful and you get paid. 4. The book gives you credibility in industry events and may even help you get a special visa if you need one.
Full disclosure: I have never written a technical book, but you should if you work in Developer Relations.
LangChain gets a lot of pushback in production scenarios, but think going through some of their tutorials is a very reasonable way to get learning more about how you could apply gen AI for various use-cases.
* When your chains get long/complex enough in LangChain, it's really hard to understand from debug output what's final prompt that actually being sent, how much it costs, or catching runaway agents. This pretty much solves that for me.
As a "prompt developer", one thing that'd be incredibly useful is a way to see/export all of my prompts and responses over time to help me tune them (basically a "Prompt" button in the left nav).
Congrats on the launch. So nice to see a tool in the space that lets you get up and running in 4 minutes.
Great post on this: “Why Agatha Christie could afford a maid and a nanny but not a car”
https://www.fullstackeconomics.com/p/why-agatha-christie-cou...
The thing that had the biggest impact on various quality of life issues (and why I stayed) was moving from the Mission to a quieter and safer SF neighborhood. I bike everywhere, don’t have a car, and can walk to work and several beautiful parks, including one that opened this year.
If I had kids, don’t think it would have been possible at all to stay.
Last year I implemented TCP/IP over AWS Cloudwatch. Tons of "can you believe that actually works?" stuff possible with it:
https://medium.com/clog/tcp-ip-over-amazon-cloudwatch-logs-c...
“Because of dust”
[spoiler below]
https://twitter.com/ncis_cbs/status/1044751471927947264?lang...
https://techcrunch.com/2020/11/24/splunk-acquires-network-ob...
[blatantly promoting my substack] Been following this area about a year, first wrote about some of startups using eBPF here in late 2019: https://monitoring2.substack.com/p/ebpf-a-new-bff-for-observ...
Now the random sighting ("why is that guy polishing a Waymo Jaguar on a Saturday morning in SF?") makes much more sense.
Uber -> Chronosphere Google -> Lightstep Facebook -> Honeycomb Twitter -> Buoyant (and Zipkin, OSS)
An online spreadsheet + UI + optional external API calls seems perfect for fast development of a large number of straightforward internal-facing apps, including lots of things that are currently done on paper.
For those limited and simple use cases Google Sheets is a far more usable "serverless" platform than a lot of stuff in the hype cycle right now.
Don't think iOS developers are abandoning the platform, but I do think many indie developers (or those who were considering becoming an iOS indie developer) did leave. It became a lot harder to make a living as a full-time iOS indie dev.
The indie devs brought a lot of the excitement and energy to these events and made for extremely interesting and fun conferences full of people from different design, engineering, and professional backgrounds.
(Context: developer evangelist-type here, once focused on iOS-related developer conferences and attended many of them in North America and Europe.)
To echo another comment on this thread, headless chrome seems well-positioned to shake up the automated browser testing market. The price—especially with the AWS Lambda free tier—is very, very compelling for a number of projects.
[1] https://github.com/smithclay/lambdium [2] https://github.com/adieuadieu/serverless-chrome
1: https://www.clay.fail/posts/ubuntu-http2-in-mere-hours 2: https://www.clay.fail/posts/hip-http2-using-docker/
Wrote about the process here: https://clay.fail/posts/hip-http2-using-docker/
Kinto - Mozilla, CloudKit - Apple, Parse - Facebook, Firebase - Google, Azure Mobile Services - Microsoft, Mobile Hub - Amazon, Usergrid - Apache Foundation
... and many, many startups.
Here's the link for their recent (10/16-10/17) conference, some great talks: http://jsconf.co
Couldn't help but wonder if the (valid) cost and performance problems the author has with heroku will end up pushing devs faster to Backend-as-a-Service platforms like Parse, Firebase, or something like Amazon Mobile Hub (Lambda on Rails?).
(Note: not affiliated with any of these platforms, etc. Just a lazy mobile developer with lots of things that never make it to the app store.)