The Secret Guide To Modern Software Development | Prime Reacts

preview_player
Показать описание
Recorded live on twitch, GET IN

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

Рекомендации по теме
Комментарии
Автор

You know what they say. "If all you have is a Hammer Factory Factory Factory, then everything looks like a nail."

Also i think I can hear Grug reaching for his club in the distance. May god have mercy on that poor employees soul.🙏

AScribblingTurtle
Автор

It's fine though because all the factory factory factories have an abstract base class called that makes it super easy to implement your own FactoryFactoryFactory

georgehelyar
Автор

it's like the old saying: "All problems in computer science can be solved by another level of indirection"
- David J. Wheeler

xybersurfer
Автор

"ChatGPT, build me a spice rack!"
"Looks crooked."
"Good enough..."

TOracle
Автор

Can’t wait for post-modern software development

Dzejded
Автор

The dilemma of having to choose between:
- Spend 1 day, to learn how to design the hammer myself
- Spend 5 days, learning the hammer framework that will become deprecated by next week.

Tech illiterate Management: _"All our competitors use the framework, so we should to!"_
Also Management: _"Why is it taking so long?"_

timmy
Автор

"So there is documentation raises ball-peen hammer)..

blipojones
Автор

This went beyond semantic satiation and now the word Factory means *too* much to me

Celastrous
Автор

This reminds me of when i wanted to learn React, and i wanted to first realise why it is used in the first place. I might not get any resource about what state was, but i sure as hell knew that React state was used to manage state(even though i couldn't find what that state even was then...)

KonradGM
Автор

That's good business advice, sell Kubernetes cluster, CI/CD pipelines, agile methods and UI-/AI-frameworks instead of software people can actually use. Writing software is so 2010.

yannick
Автор

- Oh no. That's a poor man's DI. We don't do that anymore...
- Should I put everything into containers then?
- We had those, but they're too simiilar to service locator, which is known anti-pattern, so we used this cool reflection feature...
- What if I use interface reference?
- That's not a problem. You see, there are these things called annotations, where...
- But I don't know which implementation to use yet
- Of course. This is why you sometimes need a dependency-map.xml configuration file
- They're kinda hard to read...
- I know, right? Our framework has this CLI command that will show everything in bautifully formatted output. Beside that, there's this IDE plugin, already built-in.
- What if I need to select implementation at runtime based on, let's say, user input?
- Oh there are many ways to do that: conditional annotations, factory qualifier injections... you should look at our documentation.
- Sounds complicated.
- It becomes super easy when you learn how to do it.
- Couldn't I just make an if statement in my...
- We've been through this already, Sir. If you want to question industry standards I suggest you look for something else. We're embracing SOLID IoC, domain-driven rapid development - we're talking real work here, not some theoretical academic solutions for "architecture astronauts"

CodeShudder
Автор

Man, this article is such a blast from the past.

Drazzz
Автор

It also kinda reminded me of needing to get a PhD in AWS just to deploy a hello world

alangamer
Автор

As an escapee from Java this was traumatizing.

No wonder I foolishly cling to my own vanilla JS functions rather than opening a similar door to the Modern Web App Dev "easy reusability" nightmare...

DarrenJohnX
Автор

I can't believe we had a whole video about factory factory factories without sh*tting on Java. What has the world come to?

Jebusankel
Автор

hilarious article with a vital point imo

headlights-go-up
Автор

Awesome article.... needed that laugh!

hardcorecode
Автор

Of the 3 factory levels, I get the levels 1 & 3, but it's that sneaky level 2 that can be a little rough to dive into.

JesseGilbride
Автор

the thing is in js world when someone get to know the underlying concept they tend to get to know the underlying problems also and if someone can use base tools to create apps they eventually build a framework of there own with whole other abstractions and now we have a js gaddon so when something like react gives an abstraction we love to hate it as we know something that its not venilla js performancet but when we try the base hammer we need to handle thousands of issues other than which we knew about as we need to know type of right hammer for the task so framework may be bad but provide a one stop factoryfactoryfactory for new commers to start with as most of us in js world mostly arn't creating basic blogs

mehfooz-ur-rehman
Автор

The conclusion is like "Apply first principle thinking also to software development"

sapkra
visit shbcf.ru