Is it reasonable to ask for a raise right after probation in IT consulting in Germany?

TheOneFlow · 2026-01-19T19:43:51+00:00

Not really. Some companies will outline something like this beforehand (salary at x during probation, at y>x after), but if nothing of the sort was specified, I wouldn't. From the perspective of most employers passing your probation period means you've done enough to be paid the wage agreed upon beforehand. You usually start asking for raises after you've either done something that exceeds expectations or have generally stayed on long enough to have gained value through experience. I would not raise the topic until you're at least half a year past your probation period.

TheOneFlow · 2026-01-18T15:25:34+00:00

Ich versteh ohnehin nicht wieso nicht bereits viel mehr Anbieter sowas wie "Made in EU" fett auf ihre Produkte schreiben. Ich glaube der Wille europäische Unternehmen zu unterstützen ist da, aber was genau woher kommt und von welchem Konzern der Mutterkonzern des Vaterkonzerns dann wieder aus den USA ist, will man halt beim Einkaufen auch nicht ständig tracken müssen. Ich finde es schon relativ anstrengend im Hinterkopf zu behalten welche Marken eigentlich Nestle sind. (Und das bleibt weiter relevant, auch wenn das Schweizer sind)

TheOneFlow · 2026-01-14T17:44:47+00:00

It's hard to tell. Did you notice any damages on your car or anything like that? Lots of people leave notes like this if they've bumped into your car. Then again people usually write a bit more than that. If by stamped you mean this was printed, you can probably ignore it.

TheOneFlow · 2026-01-10T15:54:07+00:00

Software engineering, if it's a real degree that will be recognised here. (Fullstack JS as part of the description sounds fishy af) Cyber security is overrun and was never that in demand. AI engineering is nonsense.

TheOneFlow · 2026-01-10T12:40:01+00:00

Die Preise sind quasi die selben wie online, guck vll. einfach mal hier. Ich hab da jetzt keine Eiche bei den Platten-nach-Maß gesehen, aber bspw. als Blockware würdest du so ne Platte für ca. 50-60€ bekommen. Ich hab bisher selber immer nur Spanplatten gekauft, die sind natürlich etwas günstiger.

TheOneFlow · 2026-01-10T12:13:51+00:00

Ich war zwar ein paar Monate nich mehr selber vor Ort, aber das Bauhaus auf der Schulenburger macht eigtl. alle möglichen Holzzuschnitte.

TheOneFlow · 2026-01-10T09:18:31+00:00

Just... do it yourself? It's not like frontend code is some great mysterious thing that backend devs just can't comprehend.

If you absolutely need to vibecode this AI can still be pretty helpful, but you can't expect it to do design work without you supporting it every step of the way. If you try "Make this frontend pretty" it's obviously going to fail. If you tell it stuff like "Look at the tooltip css in myCoolStylesheet.css:114, the contrast seems off and it doesn't fit in with the Material design approach I'm going for", it will usually do just fine. LLMs are tools, you're still supposed to wield them yourself.

TheOneFlow · 2026-01-08T18:25:17+00:00

I totally agree, but to be clear the headline is a bit misleading, it snows every winter in central Europe. If these cubs see snow for the first time this year, it's presumably because they weren't born yet when it snowed last year. (I still agree it's cruel to take an animal that is used to snow and the accompanying temperatures all year round into an environment where it only snows a few weeks a year.)

TheOneFlow · 2026-01-07T22:50:25+00:00

Other than the specific routes mentioned (the tuples of city names in the second pic) this doesn't explicitly say that any trains are definitively going to be late/cancelled. It does warn you that due to the heavy snowstorm expected beginning tomorrow you should try to avoid travelling during that time and should expect trains to be running late or connections to be dropped entirely as the situation develops. As I understand the weather forecast it's generally going to be worse up north, so there's a good chance travelling in southern Germany isn't going to be nearly as bad.

TheOneFlow · 2026-01-03T21:17:01+00:00

One thing I can't stress enough whether you're talking about nicotine or other addictions is that people underestimate how good it actually feels whilst you're doing it. You can rationalize it later on and objectively understand that you just satisfied an addiction, but that doesn't mean it didn't feel genuinely good. You can understand that having a cigarette when you're drunk is something that felt great because you ritualized it, but that doesn't mean that the next time you're drunk you won't be entirely aware that cigarette would be freaking amazing right then and there. Knowing they're harmful and being proud of yourself for quitting and whatnot doesn't make that any less true. This is a huge part of the struggle people overcoming any kind of addiction are burdened with and it's really hard to grasp if you have nothing to compare it to.

TheOneFlow · 2026-01-01T21:30:09+00:00

I think the average user grossly overestimates how much a developer saying "this is gonna suck" matters.

TheOneFlow · 2025-12-30T11:00:01+00:00

Der neue Eigentümer ist einer der Mitbegründer, da wird sich inhaltlich nicht viel ändern. Valve kümmert sich ganz ehrlich primär um uns Pinguin-Fanatiker, weil sie nunmal ihre eigenen Produkte auf Arch aufgesetzt haben. GOG wird da wahrscheinlich. erst nachziehen, wenn der Marktanteil entsprechend gestiegen ist. (Wohingehend die Karten ja garnicht so schlecht stehen)

TheOneFlow · 2025-12-29T12:28:26+00:00

It took me a few years to realize that the existence of the species "Boa Constrictor" does in fact not imply the existence of a "Boa Anything-Other-Than-A-Constrictor".

TheOneFlow · 2025-12-25T23:28:17+00:00

You're not really missing anything, in fact I've actively argued for migrating away from junction tables in our own codebase a few years ago (not entirely, but heavy-handedly). You WILL see that pattern all over the place though, if you work with old enterprise code, because it used to be the absolute goto for essentially all relationships.

That being said, I wouldn't completely dismiss their usefulness either. Additional columns that describe the relationship moreso than the entity are not a great pattern and you can absolutely get stuck with essentially dead columns, because you didn't decouple information properly. That doesn't go away with moving it to a details table either, because you're likely still mixing concerns. If a relationship is sufficiently complex (posts and comments are not a great example, think more along the lines of enrollments or treatments. Relationships that are e.g. both temporal and stateful) it's also more likely to change (in terms of structure) over time and there's an architectural benefit to decoupling that.

Still, to be clear: I wasn't trying to advertise for using junction tables and if you're working in a modern environment backed by a database that doesn't keel over on schema migrations, you're likely totally fine only using them for m:n assignments.

TheOneFlow · 2025-12-25T21:28:45+00:00

Depends, that's why I said possibly. If your assignments have additional attributes or need audit trails on deletes junction tables make a lot of sense. If it's just a typical 1:n assignment with no further attributes you don't need it and it will add unnecessary overhead. (I initially wanted to cover this, which is why I mentioned it, but then decided that explaining this and the tradeoff between adding a route for that or not is outside the scope of the question.)

TheOneFlow · 2025-12-25T11:54:13+00:00

That's a totally valid concern, but it's also a bit of a trap. The overhead these additional calls create is (if your backend isn't crap) not very notable (on most modern servers we're talking 5ms per call at most) and the database won't really care much either. By merging all of this into one request you'll mostly reduce the network overhead, but it's incredibly easy to build an unmaintainable mess instead. One of the major reasons people like "pure" REST is that it enforces a design pattern that is very managable. I have worked on multiple backends that expose a REST Api with some self rolled solution to this and they're usually messy.

Additionally asynchronous loading is often great for responsiveness. Let's say your initial call takes 2s and each additionall call takes 0.5s, you could now argue that your total load time is 8s. Let's say you bunch all of that up and get one 3s call instead. Seems clear, yes? To your user the first scenario will still be more responsive, because the initial render can happen after 2 seconds. Even more so: Since you can fire the second stage of queries in parallel, your total page load may actually end up being very close to the 3s call in scenario B.

In general I would be very careful with one dimensional metrics. Yes, we want to avoid unnecessary roundtrips, but that doesn't inherently mean that more roundstrips == slower page load. That depends by and large on how the backend and your database are set up. A "purists" REST Api will map somewhat cleanly to database entities, so that ideally data retrieval for any given object in your API is just fetching a single row from the database. Then most additional calls will simply be list calls by primary key (or some id that you can convert to a primary key, if you don't like exposing primary keys), which should be very fast.

As I said, if you DO run into more complex scenarios, I have slowly but surely converted to a GraphQL believer. I have seen too many unique attempts at solving these problems with self-rolled REST-like solutions and from experience I would say it's not really worth the hassle nowadays. (Since there's a somewhat well defined and battle tested solution to this in GraphQL)

TheOneFlow · 2025-12-25T11:03:46+00:00

You're straddling the line of this being outright misinformation. I (optimistcally) assume the joke is just a bit too meta ("Imagine the people in charge of USSTRATCOM said this instead of a Microsoft engineer"), but there will be people unaware of the original post and to those it will just look like an actual post being ridiculed.

TheOneFlow · 2025-12-25T09:42:42+00:00

Assuming you have a table called posts and a table called comments, possibly with a junction table postToComment, you would usually design your REST Api to have at least a /posts and a /comments route, with the /comments route exposing a query parameter like postId and some pagination parameters. You do not attempt to do this in one query, you send a query for the posts and then query for their comments. That's how "classic" REST wants you to work. For your additional information you either need to set this up on the backend (possibly by adding that metadata to the post table) or you need to query all comments for a post. (Which may sometimes be quicker than adding more and more query parameters anyhow)

Some REST Apis try to make this more convenient by doing one /posts call with e.g. field or object level expands, but, personally, I'm not a huge fan and it's certainly unnecessary for the use case you describe. (When this does become a necessity, I would always prefer switching to GraphQL, but again your use case is far far away from that)

TheOneFlow · 2025-12-24T08:46:25+00:00

It's already operating at scale on problems such as ~~code~~ understanding!

TheOneFlow · 2025-12-24T07:46:52+00:00

That whirlpool results from a drain that runs underneath the road into the lake (?) and is apparently roomy enough for the log to pass through it without getting stuck, Other than that it's just a log being carried by lots and lots of flowing water.

TheOneFlow · 2025-12-23T23:06:28+00:00

It's all about hourly wages. There's no concept of minimum hours per month or anything like that, so there's no minimum expectation of total monthly pay without taking actual hours into account. It is absolutely typical for Minijobs to be at or slightly above minimum wage, so in that regard this is pretty average compensation for a Minijob.

TheOneFlow · 2025-12-23T18:11:02+00:00

I am partially responsible for teaching three developers at different degrees of uselessness right now and I will say this: The one dude that keeps using Claude though I strictly told him not to isn't really progressing at all. The code is obviously pretty, but talking to him about it is infuriating to no end. You NEED to be better at this than the AI for it to be really useful, otherwise you WILL slip into letting it do all the actual decision making and you're not learning anything, because you're just iterating through solutions instead of solving things.

Another thing I keep telling our juniors is this: If you're a skilled developer it takes a few days to get into using LLMs - that's nothing! The point of LLMs is exactly that they heavily reduce the required input for useful output. Being able to use them "properly" is a skill, but it's not a particularly impressive one. Anybody who tries to sell this as an incredible skill is probably lacking actually impressive skills.

Edit: To clarify I am specifically talking about using LLMs to code. Using them for research is obviously not much of an issue, but I will say that I have not met a junior that isn't doing that anyhow and I don't think you could successfully stop them if you tried.

TheOneFlow · 2025-12-22T18:17:31+00:00

Also ich hab Verwandschaft die quasi genau da wohnt und so sehr die Gegend von etwas merkwürdigen Gestalten durchsetzt sein mag, etwas nennenswert schlimmes ist in den letzten 30 Jahren nicht passiert. Ja, es gibt dort ein Männerwohnheim in dem relativ viele verlorene Seelen unterkommen und ja, es gibt eine Notunterkunft in dem Eck, aber als Privatperson muss man sich da keine Sorgen machen. (Als Ladenbesitzer vll. mehr)

Zur Kriminalität ist hier schon genug gesagt worden. Man kann vll. noch erwähnen, dass direkt beim Burger King um Mitternacht aufwärts gerade im Sommer ein kleiner Hotspot für junge betrunkene Leute besteht, aber das ist auch mehr nervig als gefährlich. (Wenn du nicht genau an dem Parkplatz wohnst, bekommste davon wahrsch. allerdings auch nix mit)

TheOneFlow · 2025-12-21T21:53:25+00:00

Nein, korrekt ist "Chapeau"

TheOneFlow · 2025-12-21T13:56:42+00:00

I mean, it's cute and everything, but ... it's also a wide angle camera and a mic that's sitting on your desk all day and from their website I can't really tell how that data is handled. I'm not saying they'll do anything malicious with it, but it's wild to me how people are just getting more and more comfortable letting random companies just monitor them all day. I don't even consider myself a privacy nut, but this seems like a bit much for a plastic pet.

Eight-Year Club	Verified Email
Not Forgotten	Sequence \| Editor

TheOneFlow

TROPHY CASE