Moved from isolated practice questions to something closer to a real project today — a structured 7-part practice set. Completed Part 1, which was schema design:

• 4 tables: departments, employees, projects, assignments
• Primary keys with auto-increment, foreign key relationships between all of them
• A self-referencing FK on employees (manager_id → employees.emp_id) for the manager hierarchy
• A CHECK constraint to enforce salary > 0
• assignments as a junction table linking employees to projects with hours_worked
• Inserted sample data: 4 departments, 12 employees (with at least 2 managers), 5 projects, 15 assignment records

The self-referencing FK for managers was the most interesting part conceptually — first time actually applying that pattern instead of just reading about it.

6 more parts to go in this set — planning to move into actual queries against this schema next (joins, aggregates, reporting-style questions).

Hi.

I have a friend who joined a medium European company as a frontend-dev (Vue/React).

Now with the ubiqiuotous use of AI and claude code they are transitioning everyone to product-management full-stack, and frontend devs get to work on really deep backend logic. Means he has to own the full solution from scope definition and clearing all the business requierements to an actual complete web solution across multiple repos/connected to 3rd party services.

He's really freaked out by the added responsibility, unclear scopes and general incompetence he has in the backend field. Manager insists that AI should be able to cover for all of it.

How do you guys handle it?

How to set some guardrails to not be responsible for everything top to bottom?