I only got quite simple tests tbf, but I don’t look for senior positions. Main thing is to just get the problem solved writing decent code (if it’s a home assignment) or to walk them through your reasonings

The only time I got a leetcode waste of time it was a Dijsktra/A* problem (which I failed)

Why? Tech tests are fine, absurd complex tests for shitty jobs are not

chroot chroot chroot!

I am CHROOOT

Dude, what you wrote is cockiness^cocky

I liked using CLion for both Rust and C++, now I see they outright deprecated the Rust plugin

Left is clearly more readable, after you read comments. I think the example is bad though, and in most cases right would be clearer

I guess so that if I leave, they won’t be fucked

JS/TS, Rust-ish, and CPP

Yeah, probably. In the end maybe I will end up using c++ cause a coworker is pushing for it (although he knows nothing of the language). Ironically, I’m the one advising not to cause I know I don’t know lol

The project is brand new (as in, the integration backend doesn’t exist), I have to code and architecture it

It’s not web backend

What existing code? I have to write the whole thing from scratch

There is no codebase, I have to write it from scratch. Also nope, I’ve religiously avoided Java so far

Tell me you know I’m from an Italian company telling me I work for an Italian company

Yeah but knowing why something was made in that way would greatly help. The problem here is, the design is unreliable (just today we found an error in the design which changed an INSERT to a simple SELECT) so if we knew why certain things were made that way it would make our job much easier (in the end we have to ask if something weird was meant that way or it’s a design error)

I think you misunderstood, I’m the one implementing the API and writing the queries - alongside a coworker that doesn’t have BE experience. I’m not the one who made the DB though, neither is he, and the design is not very reliable

EDIT: writing it out, I swear, makes no sense at all

Oh I’m not the one who designed the DB, I just implement the endpoints and stuff for this particular project (my role is that of a FE dev).

I asked cause:

• they were saying that between me and my coworker, who actively work on the project, and the DB designer, the communication is poor. Which is obviously true since we were handed out the DB with an oral, confused, explanation for a complex DB so we have to ask a lot of questions or ask for very small fixes (sometimes a column is missing etc, nothing that important though);
• they didn’t foresee how interconnected the part 1 and part 2 were. Let me explain how stupid this is: the data from part 1 are mostly read only, which are provided from part2. We knew about this from day one, but it was never added to the visual design [which to this day is still in the making, so it’s incomplete]… and neither to the DB.
• when they actually went to work on part 2 - months later we had the green light to work on the project - they had this sudden realisation: the data are interconnected, we have to rework part 1! (which would have been completely avoidable)

The DB is already made, but they had to change it cause they didn’t plan a huge portion of its logic beforehand even though they knew about it. This resulted in major changes across the whole schema, while we were already working on implementing the various features

The DB is already made, but they had to change it cause they didn’t plan a huge portion of its logic beforehand even though they knew about it: this resulted in major changes across the whole schema

The DB is already made, but they had to change it cause they didn’t plan a huge portion of its logic beforehand even though they knew about it: this resulted in major changes across the whole schema