noli @ noli @programming.dev

Posts

1

Comments

86

Joined

2 yr. ago

Compiler optimizations like function inlining are your friend.

Especially in functional languages, there are a lot of tricks a compiler can use to output more efficient code due to not needing to worry about possible side effects.

Also, in a lot of cases the performance difference does not matter.

1. The skerton was (is?) A good entry level grinder that will give you very decent results especially for immersion-type brews. It's what I started on and what I still use for on the go use cases. I haven't looked at entry level hand grinders in a while so I guess some developments have happened since I got mine. (Based on a comparison video from james hoffman at the time)
2. God yes, I tried a friend's 1zpresso and the difference in both grind speed and effort is noticable.

Funny story actually. After year 1 I was in peak condition, year 2 was normal, year 3 I gained weight. Year 1 I worked slowest and year 3 fastest. I just became way more efficient :p

I was garbage collector for 3 years as student job.

Not a single person in the company has done such a thing. We did dumb shit all the time but that wasn't even close. I feel sorry that you decided that 1 person represents a whole industry

As long as you use proper lifting form it's not that hard on your back. Without it you won't last long though.

Also here in belgium all garbage collectors I know earn more than the teachers I know.

You get most of the day off after having worked a full day + still need a full and thorough shower + have low energy because it's a physically demanding job

Src: did it for 3 years as student job

Running is not as extreme as you think, a lot of it is just carrying on the momentum of the truck after you jump off, other tham that it's mostly just brisk walking.

The heavy stuff depends, regulations typically impose a limit on weight but a lot of people don't follow it. You learn to use proper lifting form quite quickly though or you'll get a hernia

Src: did it for 3years as student job

It's honestly not that shitty of a job (see my earlier comment https://programming.dev/comment/8949488 )

Source: did it as student job for 3 years.

Fun fact: the main reason garbage collection is unhealthy is because you spend all day in the fumes of public roads & the truck you're hanging behind.

Source: was garbage collector for 3 years as student job & we got a small hourly bonus for it.

Did it as a student job for 3 years. I was paid roughly 50% more than with all other student jobs.

Honestly collecting garbage is not even that bad. I got paid to do fitness all day, spending time outside while chatting with my coworker. The people sorting the trash, that was who we felt bad for. They had all the downsides of the job with none of the benefits.

You mean that instead of having a binary blob you have a generator for the data?

Why? Cause shops are open on sunday? Having no workers rights makes that a lot easier

You cry

Depends on how deep down the rabbit hole you want to go :p

• creating a new variable that contains the updated value
• recursion (e.g. it's not possible to make a loop that increments i by 1, but it is possible to turn that loop into a function which calls itself with i+1 as argument)
• avoiding typical types of operations that would update variable values. For example instead of a for loop that updates every element of a list, a functional programmer will use the map function, which takes a list and a function to apply to each element of that list to create an updated list. There's several more of these very typical functions that are very powerful once you get used to using them.
• monads (I'm not even gonna try to explain them as I hardly grasp them myself)

I want a roof python now

Good luck reaching an unwilling horse's eye balls

I also vaguely remember such a story but there the aliens got fukd up because when all hope was lost humans just started kamikaze-ing their ships. Spite is our superpower.

If you get prep time you could set up some traps.

Assuming both sides see it as a fight to the death, the horse will also engage so you could just run away into a bunch of traps. All you need is for the horse to injure a leg in one trap and it's done for. I think even just some holes with a couple spikes would be enough to injure and maybe even sprain an ankle.

Without prep time you're pretty doomed, I think your best bet is either climbing up a tree to buy you some prep time to make a spear out of the branches or worst case diving in, aiming to do damage to its legs (unlikely) and hope you are able to get out without being trampled (unlikely)

Dogmatic statements like this lead to bad, messy code. I'm a firm believer that you should use whatever style fits the problem most.

Although I agree most code would be better if people followed this dogma, sometimes mutability is just more clean/idiomatic/efficient/...

In functional programming, everything is seen as a mathematical function, which means for a given input there is a given output and there can be no side effects. Changing a variable's value is considered a side effect and is thus not possible in pure functional programming. To work around this, you typically see a lot of recursive and higher order functions.

Declaring all values as const values is something you would do if you're a diehard functional programmer, as you won't mutate any values anyway.