The trick is to get a good sense of the algorithms associated with basic data structures (list, stack, queue, graph, hashmap,...). They are primitives and almost any standard problem can be solved with those.
What you need to train most is the capability to break down problems: Like I have this input (and associated metadata), I have this context (may be null), I have those constraints (values, ranges, memory space, time, both, or neither), and I need these outputs. Then it's just a puzzle.
I no longer prepare for coding problems other than a quick refresh of the syntax of the main language. And if it's a whiteboard type of things, I go with pseudocode.
honestly, for a senior, the coding challenge is just a checkbox -- because they can use llms, the main thing is making sure whatever code they accept, they can explain from top to bottom.
the coding challenge itself is just a way to make sure that people can understand a request within an existing codebase. as an example, i pay attention to the questions the candidate asks -- questions asked always mean something.
my general assumption with seniors are "they can think high level", which means i "mark them" with that assumption, so for me, the architecture talk is much more important.
at the end of the day, you need to understand what your org needs and adapt.
You could play against an AI right now on the Brood War ladder right now. Granted, you have to make it to S rank first because that's where the bots end up.
Population control, preventing overgrazing, stuff like that. However, the Netherlands (unlike most countries) is basically a big farm with practically no wild nature, so humans manage that stuff already. Maybe I'm exaggerating a tad, but I don't get what benefit wolves have in the Netherlands specifically.
The promise that the ecosystem would manage itself and wolves would just pick the least fit of the herd. It's shown they just like to kill for the thrill. There are cases of 30 sheeps per night in one site.
'Just Place fences' is a common heard thing, however wolves are smart and will just jump over or dig underneath. If you want to make a proper barrier with concrete is just practically unaffordable for the farmers.
They do. But not in large numbers. They are not cheap, take a long time to train and come with maintenance I understand. But apparently they work very well.
Although a quick googling appears to show that there is a compensation scheme in place for livestock killed by wolves, although I see a lot of commentary on it being insufficient.
To the average Dutchy? Not much. To the average European? Also not much. Animal preservation is well and good and all but anything wolves can do for the deer population humans can do. Though Idk how it is in NL, but wild boars are nasty fuckers and we do good to keep them down, so there might be some benefit there, though not sure if damage by boars if offset by damage by wolves.
Wildboars can be quite destructive, as are deers. the wolve was the natural preditor of those animals so the only thing that kept them in check was either hunting, disease or food availability.
In the UK deer over population is a problem for forestry as they eat saplings. So we spend a lot of cash hunting them (good food source, but not widely distributed in shops) Wolves stop that.
For the netherlands sspecifically, where there are deer they eat the trees that provide bank stability (ie willows) Less of a problem now but they also eat the pioneer species that were used to build polders.
Deer carry disease for cattle and sheep as well. although cows in holland are fairly hemmed in, ticks and fleas are less so.
I live in an apartment as well and my area has really good transportation. We don't commute to work with the car. There are various reasons why we did car-sharing nonetheless.
In the end our family decided to buy a car. We got an EV. Our use is sporadic and one could argue that if money was our priority, buying the car was a mistake.
So in this situation, having an EV is fine. The only downside that I found is that I spend a bit too much money on McDonald's. This is because the cheapest chargers are next McDonald's where I live. But it's not a problem, just a funny hiccup.
I understand your viewpoint because but also have you considered that your approach adds nothing to the builder?
I don't mean this in a judgemental way. In your scenario, I spend learning 50 different technologies that I will never use because they are not hired for. Whereas the colleague makes 50 different projects, gets comfortable with the technology and maybe hits an interesting edge case or two to talk about at their next interview, if they are lucky.
I am saying this as someone, who has tried to think about complexity and what not in my projects. But it turns out that I get a lot more mileage from practicing deployment with k3s than know what Dokku and Kamal do and how to deploy the app directly as a process.
> In your scenario, I spend learning 50 different technologies that I will never use because they are not hired for
I'm actually saying the opposite of this. To learn react you also need to know html, css and javascript, so I am saying if you need to make a static website that is just a single page you may as well just write it in HTML. I am saying you should use less technology.
Similarly to learn Docker you need to know bash so you already have the skills to just skip over docker and deploy your app directly by running bash commands on a linux server.
The "50 different technologies" is how I see the flavour-of-the-month cloud platforms that take something that's relatively simple (copying code to a server and running a command to start it) and turning it into a proprietary cloud platform you now have to learn. Whereas you could have just learnt how to deploy software to a linux server instead and have a skill that was valuable 20 years ago, is still valuable, and will still be the way software is fundamentally run in 20 years time as well I am sure. Meanwhile I have no idea what Dokku and Kamal even are - I'm sure they won't last as long as linux and bash have.
I'm sure bash will outlast me. I do hope to work on Dokku for another 10/20/40 years, but if there's a better project out there, I'd be happy to help users migrate and bow out of the deployment space.
I maintain Dokku for the folks that don't want to build and maintain a bespoke deployment process around docker, and the k3s implementation uses helm at its core, so users can eject when Dokku has run its course. I think there is value in that - maybe not for everyone, but at least for folks busy with building product on a budget.
That said, I'm happy to see folks continue to build new tools and iterate on ideas in this space. Definitely cool to see how everyone improves on stuff I - and others - been working on for the last two decades.
I think the gp is saying the exact opposite of what you gave an example for, and in line with what you are saying i.e. less technology.
one more thing is you tried both kamal and dokku, and then made a deliberate choice of sticking to k3s because suits you the best rather than making a mindless descision about using k3s, which most people do!
It's definitely the case based on my anecdotal evidence. Friendships are formed very early in life in Northern Europe and your circle has a tremendous impact on everything. The same is true for Western Europe, but maybe to a lesser extent.
As an EU citizen, I can't tell you if it's true for the immigration office.
But for anything else? Kind of? If you want to move, you have to make an appointment in person to tell them. But it is also retroactive, so you can move and then make an appointment in 5 months and it's fine. The paper that says where you live is very important but it's also easy to get, you just have to show up. Not any time but the times for that are plentiful enough that it works out.
What makes my blood boil is the paperwork for when your kid is born. It feels like they should just be able to retrieve everything from their database but you have to submit a load of documents anyway and it has to be original.
Also, don't try to get married in Germany. Just go to Denmark, much easier, despite the delays if you get something wrong. You can do the whole thing in English and you don't have to translate anything for Germans after, if I recall correctly.
If you don't have to deal with the immigration office, it's fine. If you do, then good luck. I heard it's a pain. For example, in Bremen, it takes at least 2 years to process a citizenship application. It should take a year at most. So I guess if you ever wanted to sue someone and win a slam dunk case, you could do that in Bremen. In Berlin, the citizenship application takes only a few months.
Just for reference IKEA tend NOT to include wall fasteners (or anything alike, e.g. nylon inserts) that alone is a way more involved process (incl. leveling that I mentioned in a top post) than connecting a mdf-board plate (parts) with dowel pins (many parts) and metal screw(s) (even more parts).
reply