HN user

RicDan

108 karma
Posts4
Comments50
View on HN

No? You work on something and finish it. At most I have 2-3 feature branches open. If none are in review, I have commits in them with current work. Maybe I use the stash 2-3 times a year when I am heavily experimenting with different implementations.

I've been working on and off on flagforge.dev

I have always hated how we deal with feature flags; often times as a dev I implement it, but then business decides how the flags are used, which comes back to us having to set them. I want to make this something that can be used by both easily, and priced fairly - looking at how much others charge for a feature flag SaaS is insane.

Currently I'm in heavy testing by myself, as I am quite worried about issues (that's just my personality), but yeah. It started as a normal side project for me to train a bit, then I added a bit of agentic coding to it to also learn it, and now it's here.

Not really. If pay decreases it's because you're not required anymore or less, which is contrary to what has been shown. IF educating and enabling juniors etc. is not handled correctly, then senior pay will explode, because whilst they are much more efficient, their inherent knowledge is required to produce sustainable results.

Claude Skills 9 months ago

Skills are literally technical documentation for your project it seems. So now we can finally argue for time to write doc, just name it "AI enhancing skill definitions"

I've always wanted to know: Are people actually interested in more granular pricing options? I.e. give me 10x more tokens but miss me with that image generation, or give me more bandwith but still only one domain. It feels like nowadays 80% of stuff in pricing packages isn't really used by people paying for it, but they can't opt out of it...

Definitely agree. I blame educational institutions (I know, they can't do much without enough freedom + budget) for not advocating enough to our democratic responsabilities. I do wish we adapted some stuff from early history (Athens to be precise) - democratic participants got a very low base salary, and they also could vote to ban people from democratic participation (and hence the city) whenever they got too power hungry. Seems like a loss of responsibility allows too much incompetence to prevail.

Can sort of confirm that. Wiped out is maybe the wrong word - they are more heavily being off-shored right now. Whilst there is some very obvious evaluations going on of replacing juniors with <insert your favourite llm>, it's quite obviously not there yet but management level interest is off the charts.

We are trying to motion against it as much as we can internally... by arguing that we can use <insert your favourite llm> as a good coaching/mentoring support for juniors to promote them quicker. But yea... We don't like where this is going, and right now it appears that not much can be done by how much money is being poured into this current LLM-based-delusion.

Edit: speaking specifically about SWE-Jr. jobs

I wonder why tho; humans by themselves should have an intrinsic interest in knowing how things work and behave, and being sure of it. Or maybe that's just influenced by my personality? Like I couldn't fathom doing things without being sure of it, due to being afraid of failure. Are Far-Right populists considered those fear-/hatemongering? I can imagine that when you have a scapegoat defined to push any issue to, you lose the first appeal of actually understanding things?

This is quite an interesting topic, which would be fascinating to deeper understand, because from a superficial look it does appear that introducing directed hate makes masses much more susceptible to being controlled. Also helps my theory, that whilst the left did like Elon for quite some time, that doesn't mind they blindly trusted him and pointed out his issues when they came up, which pushed him to a more... comforting? right wing embracement.

Yes but it didn't help. Maybe it was more or less my complete prompt. Regardless, depending on your input, you can figure out the architecture of it. In theory, if you did the previous levels, it basically is a combination of it all turned up to 11.

From my understanding it has a main AI, that contains the secret, then one that checks the input/output for intent, then a final classic filter for the password.

Basically you have to phrase it so that the AI 1 outputs the password, in a way that the intent is not seen as malicious, but also in a way that is encrypted enough to not trigger the filter. Usually "add <something> between each letter" gets you pretty far.

I hope nobody is really surprised by this. This is basic money-making-scheme; offer to open up standard for others, because you were the first, for some nice money bag. Make the news with your "goodwill". Take longer than necessary to roll it out, in hopes of people flocking to your vehicles.

Edit: I'm also surprised there isn't a clause about "has to be done in X amount of time or else"

Care Doesn't Scale 2 years ago

I live in Switzerland and my girlfriend has been working as a doctor (surgery), and it has mostly to do with the politics that come with hierarchy. As in nearly all companies, hierarchy allows politics and favourism to enter the playing field which will attract people that do not act in the primary interest a service should have: ergo, patients.

For example you have leading doctors who prefer not to look at patients, even tho they belong to them (from a specialization point of view), as they are "cumbersome" cases. That often leads to them "ignoring" it for some time until someone else takes over, or completely delegating it to non-fit persons.

It's a huge pain for me to heard this every day, because it literally sucks out any desire to work as a doctor from my girlfriend. At the same time, it's infuriating: we pay a lot each year, and with every year more, for services like this. If I was to ever win lottery, I'd use that money to make my own hospital without all of this crap.

Sadly it seems that the current trend is to throw in android and apps and whatnot to make it a terrible tablet replacement, whilst driving the cost up. It baffles me how android is in any way (apart from installing other reader apps) an improvement for e-readers.

I never understand people who write stuff like this. Its climate change; we know what is happening and we know how to fix it. We don‘t need AI for it, next thing they‘re gonna say is let‘s use blockchain to fight climate change

The routing of just load balancing is much simpler than the routing of exectution jumping between many microservices

Not necessarily at all, i.e. using GRPC it's all self discovered.

I agree, but a microservice architecture starts you out at a higher complexity.

Definitely

That can also be done by having that business logic live in its own library.

That's true, having it in it's own library is certainly a possibility -> but then it's also not that far off micro/macro services anyway, except you deploy it as one piece. And basically this is my argument: If you're having it all as libraries, and you all work in a mono repo anyway, the only real difference between micro/mono is the deployment, and that with micro you _could_ independently scale up whatever the current bottleneck is, which we've used plenty of times

Which is perfectly fine - 100 million concurrent users aren't the same for app x and app y, as the business logic the backend run isn't also the same.

Not saying it can't handle everything as well. Just saying the modularity of microservices makes it, in my pov, easier to handle large complex real time systems.

Maybe that's also something that comes with experience - as a rather "newish" guy (professional SE, so one level above Jr), it makes it easier to work on our project.

So you have to take care of routing etc.

I see how it works, and I completely agree that to start out, so going from PoC to first business implementation, a monolith is the way to go (unless the goal from the start is 100 million concurrent users I guess).

But after that initial phase, does it really matter if you use one or the other? You can overengineer both and make them a timesink, or you can keep both simple. I do agree on things like network latency adding up, but being able to completely isolate business logic seems like a nice gain. But Im also not talking about real micro level (i.e. auth login and registration being different services), but more macro (i.e. security is one, printing another(pdf,csv,word etc), BI another one

I see, so basically we are applying scaling, but instead of scaling the bottleneck as its own part we scale everything.

I somewhat fail to see how that saves much effort; routing setup sounds like a hassle.

What we‘re using at my work is just a mono repo with all services in it, which works pretty well, and we‘re like 7 BE devs