Hacker Newsnew | past | comments | ask | show | jobs | submit | valzam's commentslogin

If this works `git clone me@github.com:me/mine.git release_01 && ln -s release_01 /var/www/me/mine/current` then your Docker builds should also be extremely quick. Where I have seen extremely slow docker builds is with Python services using ML libraries. But those I reallly don't want to be building on the production servers.

"ECS would have worked for 99% of these apps, if they even needed that."

I used to agree with that but is EKS really that much more complicated? Yes you pay for the k8s control plane but you gain tooling that is imho much easier to work with than IaC.


Wait a minute, if this is on AWS then what are we talking about? On-prem k8s sounds fine to me but you don't have the ECS option.


I always feel like I am taking crazy pills when I read these threads. The k8s API and manifests config feels like a create standardardized way to deploy containers. I wouldn't want to run a k8s cluster from scratch but EKS has been pretty straightforward to work with. Being able to use kind locally for testing is amazing and k9s is my new favourite infra monitoring tool.

Even if you just run on 2 nodes with k3s it seems worth it to me for the standardized tooling. Yes, it is not a $5 a month setup but frankly if what you host can be served by a single $5 a month VM I don't particularly care about your insights, they are irrelevant in a work context.


Do those use cases need LLMs? Probably not. but if good results can be had with a day of prompting (in addition to the stuff mentioned in the article, which you have to do anyway) and a smaller model like Haiku gives good results why would you build a classifer before you have literally millions of customers?

The LLM solution will be much more flexible because prompts can change more easily than training data and input tokens are cheap.


> Do those use cases need LLMs? Probably not.

One of the points of the article is the importance of gathering data to support your conclusions.

> prompts can change more easily than training data

Training data is real, and prompts are not. I don’t think this is an apples to apples comparison.


I don't disagree that very numerical tasks like revenue forecasting are not a good fit for LLMs. But neither did a lot of data scientist concerns themselves with such things (compared to business analysts and the like). Software to achieve this has been commoditized.


As others have mentioned, one big issue is that every company does these things differently and just because someone texts you a link doesn't mean it's phishing, even though it feels shady. In Australia I have had calls by immigration officers on supressed numbers that wanted PII over the phone without being able to tell me what the purpose of the call is.


Wow, this is tricky. Even though you can look up the official number you will likely not get through to the same person.


The average person self hosts literally nothing, why would it be different for inference? Which benefits severely from economies of scale and efficient 24/7 utlization


Ok but "Business Email" wasn't exactly invented yesterday...


Which is my point. They did basically nothing new internally and will be able to capture what...10-20% of overall business suite market?

That’s genius


I think people are mainly confused because the AirPod Pros are quite competitively priced compared to other higher end offerings. The Max are so far off the market that it doesn't seem to make any sense and it seems unlikely that apple couldn't make up for lost margins with higher volume. Maybe they just literally can't/don't want to produce many of the Max and price them accordingly.


I'm delighted to see somebody else who refuses to use the pompous syntax Apple promote for these things. Entire thread full of people uncritically accepting that they should be referred to in actual conversation as AirPods Max as if it's a term that deserves more grammatical respect than most of them would give to attorneys general.


Uff, COBOL written in Norwegian, talk about a narrow target to hit for hiring :)


I see mostly Java/Kotlin and Maven.

Pretty modern stack. I would start a government service using those today.


He is probably talking about this repo: https://github.com/navikt/DSF

Description translated:

> This system was one of the oldest IT systems in NAV, and ran in production for 51 years, from when the National Insurance Scheme was introduced in 1967. In January 2018, Presys was put into production, which together with Pesys became the successor to DSF. At that point, DSF was also shut down. The system is written in PL/I.

It's like the Apollo 11 code, but for social services.


Mostly PL/I but a few files of COBOL too, e.g. https://github.com/navikt/DSF/blob/main/src/GML/FO04D1X1.cob...


Who needs a Jones Act when you can have processes like these?


I mean it's not like Stripe was founded yesterday. Stripe: 2010 Paypal: 1998

I'd argue that 99% of the "internet gdp" happened after Stripe was founded


I mean I know what it means but how can you corpo speak so hard that it's pretty much unclear what the change even is


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: