HN user

nakovet

294 karma
Posts9
Comments107
View on HN

This is one of the many cases for LLMs that I ask for the intermediate work, e.g. a script that generates random numbers, instead of asking to do the work itself.

I attempted to scrape a one page grid with 800 items and also ended up asking for the Javascript look with document query selector instead of the result as I was hitting all sort of limits, context, or the LLM would do the wrong capture, print it out and get worse responses on next prompt.

We are using a service that abstracts redis from us and requires to be treated like a critical dependency, think RDS, Aurora, Postgres, if they are down the whole site is down. Every job push is a call to this service. Upgrading the service = downtime.

For us this is resulted in a big weak point on our architecture because when the service reboots both job pushing and job pulling stops, with the pushing being on the API side bringing the API down. With containers we could have multiple of them running at the same time, but the shared reading/writing of the abstract Redis locks itself.

We are considering BullMQ, because the architecture is sane: * job push: API writes to Redis * job pull: Worker reads from Redis then writes the completion.

How do you see this issue for Bunqueue? What happens when it goes down for 5 minutes, can the jobs be enqueued? Can you run multiple instances of it, failover?

Our throughput (jobs/sec) is small we do have 100k+ scheduled jobs anywhere from minutes to months from now.

It's on the landing page, there is not even a standalone mode yet, so you can't use it with node.js you need to use with Next.js. All to say, it's just early alpha preview, I would wait the project to mature before considering using it anywhere.

Forget Celery

How do you do background job processing without Celery? Every app/website I ever developed required some sort of background job processing, for Python I use Celery, Rails I use Sidekiq, Node.js I use Faktory. One of the biggest drawbacks (at least until a while ago) was that setting this up had to be a hacky webhook call to your own app that allowed up to N seconds request/response.

Minor thing with the website but the download button is not entirely clickable, if you don't click on the text you don't get to download it, due to the div > a and the anchor being just the text, consider styling the anchor to have the padding so the whole thing is clickable. :)

I love tailwind, used in 3 projects in the past 4 years, it’s intuitive, well documented, simple. I don’t miss the days of emotion and styled components where I would have to think of a name for every styled div in the project, with tailwind a container is just a div and a few classes nothing else. Less bike shedding discussion, less brain cycles spent naming things, less time wasted in reviews.

If you are maximizing income, go work for the company that pays you the most. If you consider other things then it's not that simple: * control on which project you work on * choose your cooworkers * choose your office location * return to office policies * choose process and bureaucracies It's about how many degrees of freedom you want.

It’s expensive and it’s good that other options are available, it’s not insanely expensive though, the people that need the upgrade often make 6 figure salaries and can afford the upgrade although they might not like the idea of paying it, I personally hate it but I know when I buy the machine will last me at least 5 years, which is good enough for me.

I've completed Exercism courses and they are great.

One thing that was obvious to me is that if you want to focus on a specific topic the $15/month subscription is too cheap, you can pay, take the course, cancel because you are done with the course, all within the month.

The other thing that is challenging is that the majority of programmer is either too cheap or "too broke", $15 USD is a meaningful amount of money in other countries with weaker currency, and in countries with strong currency I've met people paying thousands for a university diploma, doing a well paid internship that "could not afford exercism". That's though, I hope I never have to build a business for software developers.

All of that shared experience comes from 3-4 years ago, so prices, models might have changed since that, but if they go under it's sad, their UI and their UX was so clean, fun, interactive, pleasant, etc, it was a joy to study using their material.

Kudos on launching it, I will be trying in a few meetings to see if it goes well, so far I am finding the UI unresponsive, I click and it marks an action item as completed (optimistic update) then it reverts back to unchecked (failed). I asked the assistant what Synergy meant and it just hanged. I liked the use of a fake meeting as an introduction to the product and the action items as an onboarding checklist, I like that you launched with a delete my account as well, most startups take a long time before implementing the exit path.

About Fly but not about the GPU announcement, I wish they had a S3 replacement, they suggest a GNU Affero project that is a dealbreaker for any business, needing to leave Fly to store user assets was a dealbreaker for us to use Fly on our next project, sad cause I love the simplicity, the value for money, the built in VPN.

Everything is an ad these days, check any new content similar to this blogpost, YouTube videos, etc. That said, the article is brief, direct, deliver good points then wraps up with an ad.

Nobody mentions User Experience. SourceForge was terrible, Google Code also, Gitlab has an acceptable UX. Github kills it in most fronts.

What prevents Github Copilot from expanding to FOSS that is not hosted by them in the future? Just how Google indexes and caches the whole internet, what prevents this thing from going to public gitea of FOSS projects and scraping to train their model!?

I love Copilot, will pay for it.

I used TabNine for years, if I recall correctly it was developed by a Waterloo (Ontario - Canada) student and bought by an Israeli company. Once they changed their EULA my security aware company was like can't use that anymore. I provided that feedback to them but I guess I was the only one raising eyebrows. My suggestion is just lower your price to match Copilot, so it's easy on the user deciding between both of you, I am for one sold on how useful Copilot is.

Heroku is a one of kind platform, many tried to replicate, none have come close, the ability to setup a whole app with a few clicks on dynos and add-ons is great. The price was always salty $50/month for 1gb RAM shared CPU, and in the few past years no newly released features comes to mind. As a customer I have no idea what this security issue impact, the communication has been poor as this post does not clarify much, you have to click a status post link to see a feed of what's going on.

The author started the topic really well, be defining a separation between Javascript/Typescript.

I find the examples that followed to be a demonstration without purpose.

After reading them I don't know when to use them, he mentions "type gymnastics" at the end and I find that most of the examples are demonstrations of type gymnastics.

I work on a large Typescript codebase and rarely I need to do abstract typing in order to get something done, Typescript can be used in a very direct and objetive manner and it's usually the route I prefer.

The key takeaway is that they built constraints on the wrong place (prospects vs clients), so they are revisiting their pricing and constraints. It's a good example of listen to your customers.

The author does not suggest how to get stuff done, for that reason I think the title is clickbait. The issues the author has with Scrum are relatable, on top of that there is also rituals, someone recently switch teams and they were happy that we had 1 ritual and on average ~2h of meetings a week, compared to 8h of meetings a week on the other team: planning, retro, daily stand up, pre-planning, grooming, scoping, etc.

I used fossil in the past for my personal projects, it worked great but it had too many features for a solo developer, getting others on board of using it is hard, given git is mainstream.

Due to the shrinking user base another thing becoming more common these days is broken websites on Firefox. Sometimes something small like WebRTC processing, other times the site simply won't load. 1x/week I open a website in Chrome incognito to use it due to not working on Firefox, last week was a restaurant reservation website.

Permission.site 5 years ago

I would like to be able to take a screenshot of the user page (with their permission) using native APIs, that would be amazing for sharing content, bug reporting, etc. Google has a feedback tool that leverages html2canvas.

Alternatively, I tried using DigitalOcean app platform (side note: super hard to Google for help due to the generic name) and it was way harder than setting up Heroku, I invested multiple hours in a few days and when I finally got the app running I was not confident enough to proceed with the migration yet.

Things I've noticed: * Segmentation Fault when deploying a Rails app, Heroku just works. * Ability to add Postgres but no ability to add Redis in the same ecosystem, you have to step out of the app platform, Heroku just one click and you have Redis associated with your app and many other add-ons.

There is a lot of potential on Digital Ocean, it in its infancy, the thing I like the most about it is $ for spec, with a $50 Heroku dyno I get 1GB RAM at DO the specs are way superior.

The blogpost mentions CLI usage and the global naming issues, those are annoying sure, but not the breaking point for Heroku.

The biggest competitor to Heroku IMO it's themselves. The fact their price remain the same even though specs and computational power has became way cheaper.

I would happily keep stuff in Heroku if they revisited their pricing policy.