5,676 karma · joined February 28, 2011
Add to this hard digital sovereignty requirements: continuity of service must be guaranteed for decades. All this requires quite a special setup in which commercial entities are rather tolerated than welcomed, but they may still make more sense than a government agency so constrained by budget process that they cannot hire any decent engineer.
it is not, as long as focus is on goals rather than on solutions (applies to everything). Nobody needs a view or a workflow. Everybody has jobs to be done. That is the starting point in process design.
This is the funniest thing about customization of enterprise products. They spent hundreds of years on user research and product development, so chances are high that their standard solution is sufficient for your problem, and you don‘t need anything else. Yet too many people are tripping on the hard problem of enterprise products: the custom fields, which they hardly even need.
„Everyone does that“ is definitely part of decision-making process almost everywhere, but I personally have not seen companies where it’s just a cargo cult rather than a reasonable strategic choice. The obvious benefits are that it’s easier to find implementation partners, the costs are predictable and your users may already know the system, so you won’t have unnecessary friction in your ops.
* assisted coding, not full code generation
Good that you are asked. Did I say anything like that in my comment above?
You dismissed A/B testing as unnecessary. That is sufficient for this judgement. A/B tests mostly run on the happy path scenario of a customer: An A/B test breaks, the company is losing money at light speed.
The loading-related issues overall may eat 0,5-1% of the revenue. It is not something that should be an afterthought.
An user opening a web page is not expecting a full-blown app with multi-second loading times. If that happens, they bounce, and you loose revenue. Web is supposed to have very short time to first content paint and very short time to interactive, the shorter, the better, less than 0.5s is the goal. It can deliver that, if built properly. Many SPAs, bulky JS apps are built this way for developer convenience, not for end users. The only real use case for SPA is when you deal with a lot of local data. A spreadsheet, document or image editor, a diagram tool (but then wasm is probably a better choice).
You may say, you are not building enterprise grade frontend. But if you are small enough, you don’t need SPA either.
Let‘s say you have 5-7 dependencies to load, but 3 of them timed out because your train entered the tunnel. Your app ends up in incorrect state, fails silently and UX degrades unpredictably. This is where the conversion often drops visibly and the reason SSR is now a go-to solution for any marketing website.
Outside of a sufficiently large organization „seniority“ of a developer doesn‘t make any practical sense. So, technically you can assign yourself any label, but that would be weird thing to do.
A freelancer is measured by portfolio, a computer scientist in academia by publications, an OSS contributor by the volume and impact of contributions. In either case, it‘s proportional to the effort spent on learning and building.
Anyway, regardless of employment status the measure of your professionalism is not defined by only something you can learn from the books. Experience matters a lot: it‘s nearly impossible to succeed in stakeholder management or presentation of your solutions by reading anything. You need practice and feedback. Senior engineers aren‘t those who excel in writing code: fresh CS graduates are supposed to know algorithms better. Senior engineers can contribute at full scale of SDLC themselves and support others. That is much easier to achieve in a professional environment rather than working on amateur projects.
> The only way an international business is going to consider investing in French workers, for example, is with relatively low salaries to offset the inability to fire them.
> Strong worker protection? Expect fewer highly paid roles (wage compression)
For European startups it’s different motivation. Lower salaries than in USA are an advantage, but job security isn’t a show stopper. First team is hired in fixed contracts, which may be converted to permanent with growth. In scaling phase you add external support, with e.c. 20% of workforce coming from outstaffing, so that you can react on the market and scale down when needed. If you are big enough to be called international business, you will not hire in one of the most expensive locations in the world (USA) unless you have a good reason. There exist other easy-to-fire tech hubs, and it’s not a big problem in Europe anyway (it’s just some more effort to execute, but even with payouts it’s probably cheaper than in US).
> Make it difficult to evict tenants? Expect more stringent requirements from landlords
In Europe there’s less homeless people. It doesn’t work like that.
>Enact rent control? Initial rents are going up, new builds are disincentivized.
It’s not rent controls that make markets inefficient. They are reaction to NIMBY regulations and disincentivized home ownership like in Germany. Root cause is uncontrolled extraction of scarce resource (land) and the solution is actually to scale down for-profit rental market while aggressively subsidizing ownership and construction.
And the reason is not just rules of engagement - such targets simply have negative value for attacker.