simplecto

The sooner you start something and start failing. Get yourself into a feedback loop of try/fail/try again/fail less/etc/etc

You can read and research all day long, but that does not build skill.

Test your own ideas by writing and sharing. Hopefully the feedback you get from peers and anons online will be helpful.

Learn to use a real debugger, not just print() statements

Breakpoints, value peeking, step into, step over are incredibly value especially on larger blocks of code

Interesting take!

Could status updates just be another "post type" in wordpress parlance? Then have those post types are treated differently across your site.

They would have their own RSS feed (syndication, yay) as well as a my-feed/ page.

I also agree about the amplification factor. If one wants to acquire readership then one must play the social media game in some form.

Frustrated with the dual choices of Google and Bing, I decided to build a narrowly focused search engine to see if it can deliver better results. My first experiment covers the Django ecosystem.

I figure by curating my own index I can, over time, get most of the results I typically need when in a developer workflow.

Feedback, critique, and heaping praise always welcome :-)

You should head over to Indie Hackers (https://indiehackers.com)

Wow. Maybe one idea to mitigate in the future is to be registered one multiple tlds and at multiple registrars. Have your client libraries round robin request to the .com .net .whatever. That way your existing customers still have service.

I’ve never done this, just spitballing ideas

You need to reach out to this guy. Hes written a book on the subject.

https://themouseless.dev/

Interesting! You should put a side-car blog up and talk about the challenges and lessons that came from building this thing. I've been doing that and was able to ride the front-page of HN for about 18 hours. Link in profile.

Also, I see that you are in Norway?! Hej from Sweden :-)

This is neat. Points for execution!

I did this for the first iteration of my side-project using my camera to "take a photo of a photo".

I did a side-by-side comparison of screenstab vs iphon6 taking pic of screen. original screenshot as control

Here: https://imgur.com/a/urRmG2S

WFH means we have time on our hands to do comparisons like this. LOL

This is the exact template. All the real selling happens over the phone

It reads like a Buzzfeed style advertorial for Oculus and all the Apps offering up content.

I once mishandled the api keys and endpoints for dev and production environments, effectively send dev alerts as prod and prod as dev.

Anyway The business was seasonal and entering spring (our big sales time), and I see a flood of errors coming. In on DEV environment.

I silenced them because I figured someone was working on it. Nope. Our customers were working that checkout process and the payment gateway was failing hard.

Yeah, so 12 hours later I get a fire drill call from VP finance asking why his morning reports report no sales.

I was too green to realize my mistake right away and took another 2 hours of bumping my head on things before seeing the glaring mistake.

Impact: 25 to 30k but maybe less as customer service made lots of follow up calls to close sales.

Love your customer service people. They are the ones who humanize your mistakes.

Sure! These are either on my list or already here:

[1] - https://gumroad.com/l/staff-engineer

[2] - https://www.taschen.com/pages/en/catalogue/graphic_design/al...

[3] - https://gumroad.com/dvassallo#PBkrO

[4] - https://www.goodreads.com/book/show/55614257-this-is-a-swedi...

Yeah the game has changed. Burned some money on LinkedIn ads last year. It was more of an exercise in learning how to create campaigns and place creative.

In the end all you need is one post to go viral (or hit the front page of HN) and it is off to the races for a while.

I've decided to put that money into my content.

Geek out a bit on camera and audio equipment.

Hire a part-time editor for videos and podcast.

Buy some e-books off gumroad.

I think I'm happier for it.

One quick win that might catch most of the bots is using CSS to hide an dummy form input.

No human will see it if their browser properly renders, but bots using CSS selectors might fill it in. If you see that field is filled in then you have a high probability of it being a bot and can drop it.

I'm amazed how often this question pops up. And I like that there are so many managers out there.

I will throw my own hat into the ring:

https://www.curabase.com

It is a side project, but I use it as my daily driver. I keep saying it is a bookmark manager, but perhaps is is more of a directory builder.

I launched here a few years ago, and then life got in the way.

Anyway, its back and I've been running monthly sprints to improve it for myself.

Have a look and shoot me some feedback.

I use Ghost [1] for my blog (self hosted), and the drafts folder is perfect for me to jot notes and collect thoughts over time.

My work-flow is like this:

  1. It usually starts with a thought on a post-it or notebook
  2. Bring that immediately into a draft on ghost blog
  3. Start brian-dumping fragments, thoughts, sentences 
  4. Group fragments together under headings, which get a clever title
  5. that forms the bones of the thought. Some thoughts get evicted or pushed into its own separate draft.
  6. Back-fill each section with research and supporting materials (links, pictures, code snippets, etc)
  7. write a tldr;/summary on top. Conclusion on bottom.
  8. share draft with colleagues and mom
  9. publish

[1] - https://ghost.org

True, but the content of the message could contain identifying information. This is not an easy issue to solve.

What a nice sentiment, and one I am completely on board with. I've likened my "digital puttering" to my father whiling away the hours in the garage during my childhood. Some hammering, some grinding, and my mother occasionally taking out a cup of tea.

And to build on that there was a cool video recently about a forensic pathologist in Houston who makes kitchen knives. He's not scaling, but it seems that it is a hobby that he loves.

https://www.youtube.com/watch?v=2VPSlfz65h8

This reminds me of the debate format they had in one of the British publications. Was it FT or Economist?

Either way, great idea. best of luck!

We need more search engines. Is there a way to see which rss feeds are in your index?

Google has lost the battle against the legions of SEO pros (both white-hat and black-hat).

Everyone else just pays to play.

Here, just look at this: https://preview.redd.it/p4h7aspjnx761.png?width=960&crop=sma...

Search "learn django" in google and not one result above the fold is an organic link.

I want universal copy-paste like Apple has between devices. It would be great to have that between my Macbook and my Windows machine that I use for video calls/streaming.

I support this. I would gladly consider paying for this product should an enterprise customer come along.

In the mean time the free version lets me learn and experience the full product.

Ha, ok. I added this as a feature request.

https://github.com/undernewmanagement/3cosystem/issues/25

Not sure it will get much attention, but thanks for the input.

I’ve been a customer for years and enjoy having access to their team via slack.

I recommend giving them a spin— nice to have players other than the big three cloud providers.

Hah. Quite a few:

https://www.3cosystem.com -- a simple startup events calendar. I'm surprised it is still up. It scrapes the Meetup API firehose, filters for tech events, and drops indexes on 65 cities world-wide. It never gets updates, and I'm surprised it still works.

Traefik handle websockets just fine. You just need to make sure Traefik can talk to all the backend services on the right ports.

No. You can do that much easier in docker swarm.

In my case I just take the 5-10 second downtime in between container restarts.

Typically the process to update an application is to push up a new image and then tell docker to stop the old one, and load the new one in its place (yes, I know there are 0-downtime ways, but lets keep it simple).

If you put both processes in the same container, then you cannot simply upload a new image and restart the container. This is where it gets very complicated, error prone, and not in line with what I understand to be current best practices with docker.