2,386 karma · joined December 17, 2010
So don't worry if you've never played fantasty football or don't follow the NFL. If you can paste a prompt into your agent or harness, you can play.
This is DFS, so it's a fresh game every week. Happy to answer any questions, the code is all up on Github here:
Why did we build this? We wanted to streamline the process for getting folks up-and-running. No need to install Python, download dependencies or configure your environment. Just install Langflow Desktop and start building.
We're launching a preview of Langflow Desktop today for MacOS. Please download it and take it for a spin! We can't wait to hear what you think of it, please feel free to comment and the team and I will respond.
As part of this announcement, Langflow has released an alpha of their 1.0 product. Langflow is free, open source and vendor agnostic and we'd love for you to take it for a spin.
It's a simple `pip install` and we're hear to capture any and all feedback:
It's a simple `pip install` and the team would love any and all feedback!
I joined Twilio in 2012 and I saw first hand how pivotal Jeff was in supporting the idea that in order for a platform to be successful it needed to treat developers like first class citizens, and not simply the recipient of a "directive to integrate" from the CTO.
This idea wasn't simply a fist bump to devs for cool points, it was a recognition that developers themselves held the key to innovation and creating radically new things. This culture led to entirely new ways of building API docs, designing developer dashboards, creating developer events, and so on.
So many of these things have become mainstream and the new baseline for platform companies that people forget how unlikely it was in the beginning and how hard Jeff had to fight to keep the company from treating developers as a means, and not as an end. And I think all developers who are happily hacking away on a free tier of a cool API with excellent docs and a vibrant developer community should tip their hat to a person who helped make this normal and influenced a generation of leaders to do the same.
Server - https://github.com/trycourier/courier-nextjs-puppygram
Courier Inbox comes with web and mobile SDKs that are highly customizable, and we wanted to push the limits and see what we could build using them. We landed on the idea of Puppygram, an Instagram clone that displays nothing but pictures of cute puppies. We built the server using Next.js, Random.dog and Inngest.
We wrote-up a technical tear-down blog post [1] and have posted all source code [2] [3] on Github.
Happy hacking!
[1] https://www.courier.com/blog/introducing-puppygram-powered-b...
I organize an annual developer conference [1], and one of the highlights of my life was renting this place out and inviting ~400 fellow devs to spend the night playing with mainframes & vintage PCs [2] and signing karaoke.
[1] https://2020.cascadiajs.com
[2] https://twitter.com/ermap/status/1063697148514983936?s=21
Shameless plug:
If anyone would like to create a developer profile that you have full control over and that doesn't expose you to recruiter spam, please check out what I'm building at https://fizbuz.com.
The folks behind Architect built a fully hosted service that includes CI/CD called Begin [2].
I’m happily using both for a few different projects.
[1] http://arc.codes
[2] http://begin.com
I follow over 2k accounts, so the odds of the most recent tweet being 45+ minutes old is low.
I also double-checked some of the people I am following, and indeed their most recent tweets are not showing up in my home timeline.
This is happening across all my devices (mobile & PC), so I assume it must be an issue with their infra that is limited to a subset of their users. Possible an issue with a cluster?
It's very alpha, but I'd love to hear what folks think. Here's an example profile:
https://fizbuz.com/u/elginskye
I plan to ship a public GraphQL API that makes your data available for any use you can imagine, including generating a "standard" resume or building a personal website.
Was that an error on the webpage or in the JS console?
https://github.com/crtr0/twilio-video-app-react
You can try it out at:
https://video-app-7758-dev.twil.io?passcode=7020447758
Just enter your name and the room "HN".
https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/API....
Hats off to anyone who can rapidly go from those docs to a deployed and working app. I was able to modify the repo linked in the parent to suit my needs in roughly 2-3 hours, much of which was install/setup.
I spent some time looking at the Jitsi Meet source to confirm this assertion:
https://github.com/jitsi/jitsi-meet/
It was quite clear that trying to use that code to execute my use case above would have been a very large waste of time, and quite possibly (given the lack of docs) a futile exercise.
I'm seeing discussion below about fully open-source solutions (Jitsi Meet) vs. fully proprietary solutions (Zoom). What's interesting about using Twilio is that it is a programmable solution.
Case in point: I am building a webpage where people can log-in to a virtual office, so that people working from home don't feel so lonely. I have certain requirements, such as:
- All audio is muted
- Participants are arranged in a grid
- Room is persistent (no need for an "owner")
Now, Twilio isn't the only Video platform on the market (see TokBox, etc), but I think comparing this to Jitsi/Zoom/Hangouts is like comparing apples to oranges.
[1] https://www.netlify.com/products/functions/
In about 15 minutes I ported the code I had written to Autocode. A few things that felt pretty magical:
- auto recognized and imported required NPM modules to my project
- ability to run code in-line (via Runkit)
- auto-generated documentation
https://stdlib.com/@carter/lib/open-graph-api/
...and can see an example API GET request which returns the Open Graph information for one of the top stories on HN today:
https://carter.api.stdlib.com/open-graph-api@dev/api/?url=ht...
I'm pretty curious to see where this product goes! It would be super cool to be able to easily tack on auth and a pricing model for heavier (enterprise) users of this API.
I like to think that how we message the CFP and how we manage the process and communication with submitters decreases the chance of people being overly upset with the outcome.
I'd encourage the author to consider if there is anything they can do to attract different kinds of people to their CFP or perhaps manage expectations better?
One thing we did with our most recent CFP [1] was to reply individually [2] to each person who submitted with constructive feedback on their submission. I think transparency and respect goes a long way.
Doesn't it friend in what you're hiring for? I'm not sure a backend developer should be expected to craft together a great website.
And even if you're hiring for the front end, I've found that being proficient at a11y or building React apps or designing elegant CSS doesn't really predict your ability to execute on a professional profile site, which is essentially a marketing tool.
Disclaimer: I'm working on a tool for developers [1] in this vein.
This sounds like an email that should have only gone out to a handful of people went out to everyone. And those people, rightfully concerned that SUS didn't think they had submitted their weekly update, are now taking the server down.