ediardo

Bard:

Prompt: What's funny about this image?

Bard: Sorry, I can't help with images of people yet.

In my experience, a lake looks glassy when the wind speed is less than 5 km/h.

You just reported a new bug. It's been fixed. Thank you!

Enjoy

Yes, we will land on Firefox very soon, hopefully next month.

Copilot's been very useful. The extension is built on TS and lots of custom CSS. Codex is knowledgeable with browser extension APIs and it's helped me to write most CSS utility classes that change sizes, margins and paddings, so that I don't have to bundle the extension with another third-party library.

I've been using Copilot for 5 months while building another AI productivity tool. It's changed my habits my I'm becoming a bit dependent on it for autocompletion. It feels so good just hitting TAB and moving on.

I know some developers that aren't embracing it the same way I do, making judgements without even trying it. "This is the future", I tell them, "it makes your life much easier", but there's resistance.

Prompt engineering is quite interesting too, and it may turn into a job skill later. While using Codex, I understood the importance of knowing how to ask for the right things to a non-human. Is bit like talking to Alexa in the early days, in the sense that I couldn't talk to Alexa like a human yet, I had to be specific, clear and intentional. I still see that people who are less experienced with a smart personal assistant struggle to get their commands done.

If you love this technology and would love to try it for Explaining Code in your browser, check out the extension ExplainDev (https://explain.dev). It works on GitHub, StackOverflow and documentation websites.

Disclaimer: I built ExplainDev, with the help of Copilot.

This is very clever hack. I did not know you could do something like this by reading metadata of a repo.

I'm thinking of connecting it to Zapier so that I can send the screenshot to some places.

Hi all,

Maker here. This is a browser extension for Chrome. Very fresh release focused on stability and support for GitHub repositories.

The extension is free to try and use. I'm looking for feedback that can help steer ExplainDev in the right direction.

ExplainDev is powered by OpenAI Codex.

I like Carbon, the option of creating new themes and saving snippets. Is the project still alive? I got a message from Open Collective [0] saying they stopped accepting donations.

[0] https://opencollective.com/carbon-app

hey abeyer, thanks for the feedback.

kmdr-cli[0] won't go away. It's definitely our base and when we launched with it initially, we learned that people are willing to install and wanting to have something that's running in their terminal. What prompted us to focus on the browser, was that a huge number of our queries (55%) were coming from our demo page on our website. We're a team of 3, so investing in the browser extension meant a hault to progress in kmdr-cli but we fully intend to re-invest there and bridge browser and kmdr-cli. This morning we updated the kmdr-cli to leverage the same definitions available on the browser extension. Next will be to leverage the same parser.

[0] https://github.com/ediardo/kmdr-cli

Maker here. kmdr works on any website where code is selectable, including on GitHub or GitLab, in official documentation, StackOverflow, or web-based chat. In a pop-up window, kmdr will describe each attribute of the commands: programs, options, subcommands, operators, etc.. All feedback welcome! Thanks!

Start a free trial at https://chrome.google.com/webstore/detail/kmdr/lbigelojleemi...

Noted. We have to add more details as to why kmdr cli today doesn't pull from your system.

The biggest obstacle for doing that is parsing manpages. Kmdr uses explainshell.com's parser for extracting options from manpages, but the parser fails to detect many options and subcommands' options. Kmdr's repository of definitions extends past man page parsing thanks to human verification and additions that help us to explain commands with subcommands, e.g. docker, kubectl, docker, git, npm, yarn, pip, etc..

Hi, you can check the demo website at https://kmdr.sh with no installation required.

And some new CLI programs don't ship with their manpages at all. I've also seen some manpages that don't match the specific version/release of a program installed on the OS.

It was very accurate in my case. Zip Code was right.

Just added VOZ to the airlines list.

The curious kid (and geek) inside of me would love to see this happening. Thanks a lot for the feedback!

Now accepting Flight # of length > 1

The Flightaware API.

I tried other services, including: - https://aviation-edge.com/premium-api/ - https://developer.flightstats.com/

This could be the case where the airline reuses the same flight number for different routes. AFAIK Southwest does this a lot.

The schedule you see is originally created by the airlines with some days in advance

Now accepting Flight # of length > 1

I just added AXM to the list.

I just found this large dataset [1] of airlines on github. It contains more than 6k records, with their ICAO and IATA codes.

[1] - https://github.com/jpatokal/openflights/blob/master/data/air...

Thanks. I've added JetBlue Air (JBU) to the list.

When I was developing this I noticed Southwest uses the same Flight # for a many different routes.

oops... I'll make sure to add it asap. Thanks for letting me know!

Thanks for letting me know. I'll add it to the list.

Yes, the app is only useful when you have the flight number at hand.

Thank you for reporting this. I didn't know there were Flight # that short!

I'll fix it.

That'd be awesome. BTW, some flight tracking services do show detailed information about the airplane, like service time (age), etc... I might give it a try

Hi, Thanks!

Data is coming from the FlightAware API.

Good job and Good luck.

Thanks!