vander_elst

It seems this is mainly a scala project and then they are using scala also for the configuration, it probably makes sense for them.

It seems fuchsia might me something for you

Do you have a link? The nearest best I can find is https://www.zoho.com/de/mail/zohomail-pricing.html which is ~12 bucks a year

Wayland is just a protocol that is probably implemented over and over and each implementation might have issues. It's mostly likely the different implementations having issues.

If what's written on the blog is true, the interviewee knows their stuff technically and the interviewers were just bad: they wanted to check some boxes, feel good about themselves and be done. Nonetheless, by self admission the interviewee also didn't speak English very well ("This was my first interview for a foreign company and the first time in life I spoke english") and that could also be part of the problem or something we didn't know is how the overall communication went, this might have played a part in the rejection. A candidate, but also an employee, might be very strong technically, but they should be able to clearly communicate their solutions and play well within a team, having a genius Anarchist might not always be the best. Anyway, from the post, I'd have moved forward with the candidate and if they were rejected they probably dodged a bullet. Best of luck with the next interviews!

Are there performance drawbacks in particular with long pipelines (e.g. something like `cat | grep | sed | bc | paste | ...`)?

Literally watching it right now. The best part of the German sketch is that before the sketch there's a presenter explaining why it's funny.

Why cannot this be solved by written exams?

> 25 prompts

Interested to learn more, is that the usual break even point?

Currently onboarding to go. For me personally, it's too opinionated e.g. for: error handling, mutability, unit testing, naming conventions, lack of features like sum types.

As a new joiner, some things have a "religious" feeling, like: the go gods have given us THE language and we must use it their way, without questioning too much.

I have the feeling other languages are less opinionated and this allows for more ergonomics and comfort when developing.

My method is take an educated guess multiply by 2 add 1 as extra buffer and then change it to the next unit, e.g. day->week, week->month, months->quarter. So for something that it should take 1 day I'd say 3 weeks. It seems a lot but at the end there's usually so much red tape, burocracy and and technical debt that it usually ends in the latter ballpark.

> It's better to have some wonky parameterization than it is to have multiple implementations of nearly the same thing. Improving the parameters will be easier than to consolidate four different implementations if this situation comes up again.

From https://go-proverbs.github.io/: A little copying is better than a little dependency.

Curious to see how the community is divided on this, I think I'm more leaning towards the single implementation side.

Would efficiency improve if they were to use larger machines? Same CPU/memory ratio, but more CPUs and memory? Assuming the have more than ~20 VMS for this..

it would also be interesting to know if they could get away with a single very large machine instead, like h3-standard-88... From a cost perspective it does not seem too far off from their final solution, that's why the assumption that maybe a single VM could handle the load

"Companies with relatively young, high-quality codebases"

I thought that at the beginning the code might be a bit messy because there is the need to iterate fast and quality comes with time, what's the experience of the crowd on this?

Nice idea, but it seems that for some countries the longest possible time off has a big overlap with school holidays, which makes sense. However travelling during school breaks is more expensive, it would be nice to find a way to optimize time off while trying to avoid school holidays.

+1 to this. Smaller datapoint from my side I guess, but anyway, docker is the core of my self hosting setup and it is one of the things that I don't have to fiddle with, it just works.

Working on a monorepo where we have hundreds (possibly thousands) of projects each with a different version and release schedule. It actually works quite well, the dependencies are always in a good state, it's easy to see the ramifications of a change and to reuse common components.

"one monorepo per project (api, frontend, backend, mobile, etc. as long as it's the same project) and if needed a dedicated repo for a shared library."

They are literally saying that multiple repos should be used, also for sharing the code, this is not monorepo, these are different repos.

> the date change will be two hours into the workday. That seems odd

Seconds minutes and hours can change but the day cannot?

> mental math each time

Usually meetings are setup using an app and shared calendars should actually help here, a person can have meeting slots and out of office time, that should provide the same info. logistically I don't see that much of a difference from the current situation

I still hope that someday the whole world will run on UTC0 and there is no more time zones madness. I know the day will likely never come but I like to keep dreaming.

Btw how would a double layered zip bomb look in practice? After you decompress the fist layer the second layer should be a simple zip, but that would need to be manually constructed I guess, are there any links to learn more?

Tbh banning the whole ASN seems a bit excessive, you might be banning sizeable portions af a country.

Code autocompletion. I think it works around 60% of the cases, sometimes it saves some tipping. Performance increase: small. Additionally, I don't learn the API as good as if I were to type it, considering moving back.

How does it compare to ansible? I didn't immediately find a link

Maybe a dumb question, but what kind of programming languages and operating systems were used at that time in the Soviet Union? Were c and unix a thing there as well?

Are there any known legal actions taken for people sharing copyrighted material? I know that in some countries e.g. Germany it is dangerous to share via P2P as it's quite probable that some law firm will sue you.

Has anyone used valkey in production? How does it compare to redis? Can it be used as a 1:1 replacement to redis or are there any caveats?

How do they get all the pieces? Are there programs like certified Lego professional or do they have to get every piece at consumer prices?

From a legal perspective, are there any regulations on these kinds of attacks? Meaning, are they allowed? Are they considered a war crime or maybe this is still a gray area?

They might have taste but they still don't have IPv6. Sorry for the rant, but I'm always baffled that they haven't switched yet. Anyone has insight about the challenges they are facing?