Absolutely thrilled to have my first freelance #flutter app in the Google Play Store. iOS version on its way. This app took around 20 days, but the designs are not mine! DM me if you'd like help with an app.
play.google.com/store/apps/det
#flutterdev
Christian Findlay
@CFDevelop
Freelance #Flutter Dev - DM or LinkedIn for Apps | Writer | #dotnet | #GoogleCloud | #gRPC | #Azure | #Firebase | #Xamarin | #UnoPlatform Course Author
Christian Findlay’s Tweets
Question your first answer. Why should kids learn this? It's a lot of effort. Is it a skill they will really need?
3
Show this thread
I should give you a heads up. A lot of answers are like the response you get to hitting your knee with a hammer.
It feels like a given that kids should learn how to handwrite, but seriously, how often do you actually write something with a pen? For me, it's maybe once a year
4
3
Show this thread
Should we continue to teach kids handwriting?
16
1
12
Show this thread
I missed this but SBF got arrested. White collar crime does more damage to our society than other crime. It's good to see authorities a acting decisively.
3
1
12
I suspect everyone who follows me is technically adept enough not to need this, but just in case:
4
5
So, my conclusion at this point, is that it is not possible to do true dependency injection of Flutter widgets.
I'd really like to hear from anyone who thinks otherwise...
I do realise this hinges on definition to some extent, but the distinction is important.
1
1
Show this thread
In #flutter you can build services with DI, but because of the tree structure it's essentially impossible to do DI unless you pass dependencies through the constructors of the widgets
If you request your dependencies via the BuildContext, like Provider, this is service location
1
Show this thread
DI vs Service Location
DI is what happens when a class receives its dependencies (usually via constructor) and service location is when code requests a service.
#flutterdev #dependencyinjection
2
1
7
Show this thread
I would put it exactly like this as well. You can always refactor more abstractions in if you need them, but putting them there just because you might need them creates unnecessary work at the beginning.
Quote Tweet
In some ways this Todo sample explicitly avoids those patterns github.com/davidfowl/Todo. Write the code required for the scenario to work, then refactor as needed when more scenarios arise. Build abstractions as they reveal themselves.
Show this thread
1
8
Over engineering is on the developer maturity journey. You *have* to go through a period where you overengineer things so you can appreciate simplicity again.
10
43
312
Show this thread
6
25
160
Show this thread
Who else says stuff like this?
🤔
Quote Tweet
Blindly applying patterns bugs me ALOT. I don't subscribe to the dogma, I don't write code that way...
Show this thread
1
6
I lean very heavily towards YAGNI and readable code with minimal abstractions until needed. I appreciate that every situation is different, but like anything it's hard to appreciate the benefits when the "scale" problem isn't evident.
13
21
267
Show this thread
It's Friday so time for spicy opinions. Every single sample ASP.NET Core project I see uses CQRS and the mediator pattern or CLEAN architecture. I'm over the over engineering 🙃. #dotnet
71
107
693
Show this thread
I have a feeling Donald Trump won't be running for president again
2
Wait, what? Twitter has podcasts now?
2
11
Before sprint planning, we do the sprint pre-planning.
Before sprint pre-planning, we do the sprint pre-planning preparation.
#NotMyAgile #scrum
4
18
79
But, most importantly, stop getting sucked in by pundits who push you down a path that's not right for your team or practices. Take the simple approach and stop listening to snake oil salesmen. Piling complexity on your app won't get you to market quicker or more reliably
1
1
Show this thread
Microservices as an architecture exists and there are some large orgs with large systems where it's the right choice. If you work for one of these orgs, you will know.
For everyone else, BaaS is an easy way to get your scalable app running quickly, and with the option to expand
1
1
Show this thread
You found that nobody was even doing microservices because nobody even understood what that meant.
I watched teams flail around trying to build something they knew nothing about and waste hundreds of thousands on failed projects.
1
1
Show this thread
insisting that every app that fails to adopt the pattern will slow to a crawl and fail in the market place
It was almost impossible to get a .net backend job here in Australia that wasn't there to convert an old app to microservices
But, when you scratched beneath the surface...
1
2
Show this thread
This isn't a tweet about microservices per se. There are microservices success stories and I'm not suggesting microservices are inherently bad. What was bad was the sudden jolt from building simple back-ends to some foreign architecture that nobody was ready for, and...
Quote Tweet
Can we finally admit that the #microservices craze was harmful to the software industry?
Sure, they are good in theory, but most teams end up with unmaintainable, slow, unreliable, hard-to-change monstrosities
We now use "modular monolith" as consolation, but I still say back-end
Show this thread
1
1
9
Show this thread
If you want to learn how to build apps that scale and are easy to build from scratch, look into to Firebase, AWS Amplify and other Documentdb BaaS solutions. When you need more control, add Web APIs on top with your favorite language on serverless containers.
1
11
One of the nicer features of bloobit is that you can see the state right in the widget tree when debugging
pub.dev/packages/bloob
#flutterdev
1
"No, we should reject the false idol of microservices and instead embrace the simplicity and elegance of monolithic architecture."
3
2
Show this thread