tathagatadg

Thanks for making this - like others commenting here, working on something similar, but more for personal email workflow rather than a product. I'd definitely like to give it a spin - the screenshots (ahem video) would be great.

Just installed it and started using. It is timely as I have to fill a number of forms today on government sites so looking forward to using it. What are some best practices you have come up with for reducing the cognitive load for the trigger lifecycle - that is detect the need, come up with one that fits an easy to retrieve mental model? Namespacing obviously comes to mind, and some trigger design should be as conflict free as possible, yet brief:

  :i.a - address
  :i.n - name
  :i.p - phone

Debating if I should feed my zsh history to chatgpt and as it to come up with some. Any other advice from the power users?

Wouldn’t it be nice to have a planet like rss feed from these?

Came here to see if it was the same person, though I felt very sure with the throwback web design - back when each page had its character, and you had to save the page for offline reading so that Dad wasn't pissed at the phone bill! And when the code worked - it was validation against all the previous failures (and rejections) in life! Oh the joy of sending message from one computer to the other!

Thank you Beej.

This guy AI-s! (Artificial Imbecile - literally)

I have been searching for the same answer myself. Blogs, or long form narrative consumption have morphed into newsletters and substack is the king there solving the problem for both consumer and publisher.

Note Scott Hanselman, Bryan Cantrill, Adam Leventhal, Cal Newport, Derek Sievers, Tim Ferris etc. - a lot of the OGs still maintain their own real estate on the internet. These are outside the walled garden pruned by algorithms of megalomaniacs. Whatever format you are producing content, there is an essay at the core of it. Personal blog could serve as an archive for that.

Recently Oxide and friends did an episode to address this topic - I'd highly recommend that episode and the podcast itself. This was in context of the book launch https://www.manning.com/books/writing-for-developers. I've just made through a few chapters of the book, it will give you a lot of good reasons and framework on how you should do it.

If your aim is building a readership, consider the following questions: - Why do you want to grow an audience? - What do you have to offer to that audience so that they'll come back? - Is long format prose their preferred medium for consuming the message?

I love to see investment in tools like these, so thank you so much for working on it and packaging it.

Another useful tool that I don’t see cheered enough for is vars(). When integrating new api-s, you’d often find yourself at pdb(or ipdb) prompt pretty printing(pp) loaded variables and attributes calls - pp(vars(foo)) has been a great friend reducing the burden of dot walking.

One thing I have longed for, but never took the time to research though, is pagination - your debugger window is often fighting for screen real estate, so data rich API calls becomes a little jarring.

Hook. And imagine the targeted ad revenue - where else do you have people with different spending powers strapped to a seat with nowhere to go? You have already given the flight operator your verified identification. Amazing new opportunity for data resellers.

My nephews on both side of the pond (one in London and one in North Carolina) have received smart watches for their 10th birthday. Mom can call you, you can call mom. Find My for easy tracking by parents.

Curious to learn what other strategies people have developed for hackathons, specially in a post Copilot era, how do hackathon participants perceive the landscape has changed?

This takes me to my childhood. My dad was an electrical engineer in India and worked at a ship repair dockyard. He once came back with a few shelves and cabinets for our kitchen. These were taken out of ships that were getting cut up in their dockyard. They were complete mismatches in aesthetics but it did not matter to his "why waste such functional ..." attitude. He was excited about what his "workers" could salvage from the ship. Mom didn't care as this was an old house where we have been living for generations and functionality trumped aesthetics.

The most intriguing part to me was the wooden cabinet was painted white with something stencil printed in green. My best guess was that was a Cyrillic script, and about twenty five years back, it wasn't easy to decipher what they meant.

Those cabinets are still hanging in our old house. Next time I'm there, all I need to do is pull up my phone and translate that text and get a kick out of what the original intention was for the sailors and what my mom is storing in it!

This is one of my favorite sites - I came to know about during my first trip to Europe and used it the next time to get information on even which side of the train to get the seats on for better view and a table. I am so glad it has retained its look and not become like every site on the internet that require a GPU to load.

Just a quick note - I added both the books and checked out immediately from the two different urls in the comments and placed the order - before going to the home page. There was a discount option if you buy both the books together - which it did not apply at the checkout. So if you are buying both the books, do it from the homepage. Great job on the product as well as the webpage!

Yet another article about how LLMs will shape the end user apps.

That was a great read, thanks! Have been thinking about this for sometime - remember the "filter bubbles" that we used to talk about recommendation engines in walled gardens of social media? Just like that got weaponized to meddle elections, when someone with great resources (think state actors) spots this as an opportunity, could they poison/bias the opinions generated by OpenAI LLM services? It might be easier/profitable to attack X's Grok - it has favored entry points that can be bought, and track record of being useful in previous attacks. May we live in interesting times!

I am curious to learn and incorporate strategies people are following in a remote/hybrid first world for collaborative knowledge work. Was inspired to write down my thoughts about Cal Newport's book A World Without Email, after trying to incorporate principles from it daily at work where dual distractions of email and slack reign supreme. What has worked for you that you think other people/teams should try?

Excellent list - Inspired and intrigued - thanks for sharing the list. I hardly get to do sit down and read, and became heavily reliant on airpod+audible after the baby - do you want to share a little more on your reading habit? Like did you get everything on kindle or paperbooks etc. Thanks again ...

our guide told us there used to be traffic jams in ancient Rome as well - when we were standing at the traffic light waiting to cross the road. so humbling to feel a thousand year back someone might be standing at the exact place waiting to cross the road and get into the Colosseum for the games ...

What about coaches? I wonder what state of art softwares look like these days now that iot is so common place. I remember Bob Woolmer, so ahead of his time - had an idea that the batsman would have a mini display so that they can rewatch the last ball before playing the next one.

tell us more about it ...

I owe a lot to the python language and the community. One thing specifically stands out with Guido is humility. Smart, successful and kind ... empathy for others - from the language design to focus on readability, to helping new comers - what an amazing role model! It is no surprise when you see that reflection in the python community at large.

Very cool! love the simplicity ... A UI based tool that I have found very useful https://maps.sygic.com/

thanks - was trying to figure out how to get it to the bottom! IMHO, it should be default bottom!

Neat! I have a dream - just like we have issue templates, have organization wide email templates for internal communications. If every email sent in an organization, adhere to 3 to four email templates - that would take away so much of the cognitive load of parsing each snowflake and extracting the meat out of them. As soon as you see a label in the first words of subject you know what you are dealing with - like "bug", "defect", "enhancement" - put "delay", "escalate" etc. Instead of a free form text box with no word limits, there will be more fields that enhance decision making - voting buttons, highlights like you see on medium.

The word limit will stop the mind dump and make you be precise with the focus on reaching a goal.

Some more unpopular ideas:

* A discussion would have follow up limits. Time or number. No month long threads, or 100 replies in half hours. Beyond a limit, it will automatically schedule a meeting for in person discussion to conclude on decisions

* email quotas - you can only send n emails within m hours to p persons

Show:

* give an architecture walk thru

* give a directory walk-thru

* show the hot modules. something like

  git log --pretty=format: --name-only | sort | uniq -c | sort -rg | head -10

* if can generate a dag of module dependency, that would help

* walk thru of the test cases

hands on:

* Ask them to add log messages at strategic places (find needle in haystack)

* Add new test cases in areas with low/no coverage

both are very low risk ways to get familiar with the code base

I don't know if they are ok with you taking the liberty to make some changes to google docs.

There is an add on called Code Blocks that you can install on google docs for free. Huge language support - but don't expect it to be a fully functional ide.

Other than that, you'll want to turn off auto-capitalization, and spell checking from Tools->Preferences.

I have a playlist of Bryan's talks - he is from a different planet!

That is just great to hear.

"A two-front solution could be really great. We need developers to write their best resumes, and we need employers to write their best job descriptions. Having them 'speak the same language' on concise accomplishments, metrics, technologies will make more automated matching a lot (a lot) easier." - 100%! This is the market place that Linkedin has been trying to create - but hasn't worked very well, right? They have largely solved the problem of structuring the resume data - which is definitely useful, but I don't see much of that on the job description side. The matching algorithms can only rise up to the level of quality of the input data - the resume data, and the job description.

There are similar problems in the dating industry, but mostly you can be sure both parties are putting their best efforts for creating better input.

I think honesty is also a critical part of the equation. And if the Linkedin or indeed could encourage both sides to reveal what they value deeply - that would things more useful. May be a few why questions rather than just checkboxes and drop downs that can be filled quickly. Candidate: Why is remote working important for you? Job poster: Why is a self-starter important for you? That would help bring out the uniqueness for the candidates and helped the matching algorithms.

Will look forward to seeing your product on Show HN - best wishes!

What I find funny is how little time and effort is put in writing the job description. The interview process is mostly very generic and the questions hardly in alignment to the role. As a profession we try hard to be correct about creating clear specs that can be translated to unambiguous steps for a machine to execute, but when it comes to hiring - we write ambiguous specs, toss it over to recruiters who are poorly equipped.

Here are some thoughts: - When the new position opens, the team (say the scrum team) collaboratively writes a job description based on the current backlog. Let's not leave it to a manager or recruiter who is writing the job description. Use the company/team's mission and values as guidance to see who an ideal candidate would be. This is like writing your stories.

- Then write the filtering criteria based on the typical day to day skills - what are must haves, what are good to have, what is ok to not have. This is like write your test cases.

- What are the areas where the team is lacking. Try to get skills/qualities that will, for lack of a better expression, raise the bar of the team. This is like your retrospectives - and if you have notes from your recent retrospectives, they should help you identify what you are looking for.

- This better spec should help the recruiters, and also give the candidates an honest look into the team.

- For the interview, go back to your previous sprints etc. and build questions that are simplified models of what a typical story would look like. Instead of asking to invert a tree, may be it would be better to talk about how a particular problem you solved and see the approach the candidate would take. Give the candidate all the tools - their favorite editor/ide or whiteboard, whatever they prefer.

Can trees be uniquely identified? If yes, use tree-fingerprint and incentivize increasing age of unique trees. In return you get carbon offset credits that you can sell to make money. Like crypto, but greener.

EDIT: grammar