itistricky

This was part of a code review in a small project in Go: 'You did not apply SOLID principles and no extensibility'.

At this point I've seen this kind of feedback one too many so, given that I'm just a click away from giving the whole current SW dev party the middle finger and do something more productive with my life, I'd just want to see if I'm alone in feeling that:

1. cargo-culting (uncle Bob et all) has poisoned the field to the point of destroying even unrelated paradigms (at this point I won't be impressed if someone tries to apply SOLID to Elixir)

2. SW eng roles are gatekeeped (this was a take home test) by evangelists of a certain type that make sure that things will keep being done in that way.

3. That way being the way Java ecosystem made sure that nobody with a creative vein and a slight aversion to authorities and bureaucracy would ever set foot in it again. Consistently delivering overengineered BS that build nice CVs and careers and leave companies with unmaintainable overengineered messes.

4. There is yet a shred of actual damned scientific evidence that all this 90s and 00s "best practices" actually lead to better SW. There has been no double blind experiment to measure whether the SOLID principles actually work or their best use is to insure a fat paycheck for evangelists and build CVs. For the record I conside most of SOLID and a lot of DPs just self-indulging rules conjured out of thin air. A case of an academic trying (and succeeding) to impose his hugely impractical views on the real world. Shit that looks good on paper but is actually offering little value and a lot of times is akin to splitting hair.

Anyway. Bye and thanks for the fish.

I think I deserve much more than munching on canned BS by this world's uncles and their minions.

I'm afraid that IT is quite aversive to devs of older ages. I do not seek to understand why and to what extent that is true but I am starting to bump into it.

I think though that there might be specific tech stacks, business domains and roles that might be less aversive to older age and even actively seeking employees in age brackets of > 40 yrs old.

So, the question is, you have seen such patterns?

Thanks

I'm really confused on this. My understanding on Golang's intentions and design is that it is an intentionally simple language lacking most of traditional OO features. The language is relying on interfaces (and Generics?) for doing most of the things you'd do with classic OO.

Yet I see job ads requiring and even classes teaching Design Pattterns with Golang. And by inquiry I see that they're not talking about Golang-specific DPs (that would make sense) but about fitting traditional OO DPs (and principles like SOLID) to Golang. Which in turn seems to me like bending the language to something it was not designed for in order to fit into models we developed for traditional OO languages like java and C++.

Unsure what is going on here and what the consensus on best practice is (if any).

Hi, after a long job hunting period I joined a small remote first company 5 months ago.

Problems showed up immediately in the form of chaos and dysfunctions in the microservices cloud project I was hired in. Let's put it this way: say you get the seminal book on microservices and the seminal book on CICD. Now imagine reading along and doing almost everything from code up to project management the wrong way (essentially keeping on-prem 2000's philosophy and revamp it as microservices). On top of that add vendeta-developers in Asia (I'm in a small offshoot team in Europe) handing down half-baked frameworks (not-invented-here and reinventing the wheel are strong) with minimal documentation and a culture based on meetings instead of documenting things. Developer sandboxes that just don't work and unrealistic deadlines. In short a huge draining mess where I felt burnt out just a few months after I joined and where I honestly don't want to spent another minute.

Almost every attempt of mine to change anything was met with either "yeah we know but we have to live with it for now" or a straight denial to hear me out - brushed aside as a newcomer (I'm senior and was hired as such).

So, the question is, is it unprofessional to abandon ship just 6 months in or given the circumstances is exactly what I should do in order to protect my well being and my career prospects (the project is a slow motion train wreck IMO).

So, I'm job hunting and I bumped into next task:

[system description - you need about 2 mins just reading through it]

1. Implement a new SDK method [method description]. A sort of graph search with limitations regarding scalability and space. Not trivial.

2. Write 1 simple unit-test and 1 simple happy-path integration test for the method above

3. Write a small technical design doc to formulate the technical problem and document your approach to solving it. Discuss the estimated scale of the problem, and propose an architecture for handling networks of such magnitude. Prove your hypothesis with running time and memory complexity analysis of the average and worst cases. How big do you think one's network can be in the absolute worst case? Discuss how you plan to engineer the SDK for testability.

[Another paragraph of hints/tips/dos/dont's that you need at best 5 mins to get through]

[And the punchline]

This is a small task (20-45 min)

-------

This is a small startup in Berlin. No huge salary. The best perk being remote working (which TBH post-covid is a given with most IT jobs).

I consider myself a fairly smart and competent dev but there's no way this task would take me under 2 hours. So, what exactly is happening with recruiting these days? I mean, there are devs that can understand and pull this off in 20 mins but for the life of me I cannot understand why such devs would opt to work for a no-name start up and not go straight to a FAANG. What am I missing here?