|
|
PartsBin an Electronics Part Organizer - A updated version available!
JaxCoder.com
|
|
|
|
|
Did she died on the Nile ?
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Peacefully in her sleep. Not murdered… I wrote.
|
|
|
|
|
But she could have been sleeping on a boat on the Nile.
|
|
|
|
|
Death, she wrote.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
But was it murder?
To err is human. Fortune favors the monsters.
|
|
|
|
|
#Worldle #263 2/6 (100%)
🟩🟩🟩🟨⬜↙️
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
These apps with JavaScript Backends are the future...if you can't fight them join them....
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
abmv wrote: JavaScript Backends are the future...if you can't fight them join them....
I just registered and am an Official Card-Carrying Member!! OCCM's Unite!!!
|
|
|
|
|
Olivia makes all the customer data easily viewable by all users and makes it easy for customers to view what other customers are buying and for how much.
Olivia puts the app "in the cloud".
|
|
|
|
|
And that is the interesting thing.
This doesn't mention the MAJOR POINTS:
1. Where does the data come from? - A DBA did a lot of work
2. How does Olivia know how to connect to that data? - A developer holds the hand to get it working & is blamed when it doesn't.
3. What is her security level that she can read / write data? Who set all of that up?
Honestly, the data is the difficult thing. Yeah, probably if you have the data stored properly anything is easy.
There's just a lot of missing parts in that Dog & Pony show video.
And, it's kind of irresponsible because managers all over the Universe are yelling at people, "It's very easy because I saw the 2 minute 15 second video!!!"
modified 11-Oct-22 16:23pm.
|
|
|
|
|
And then she can analyze it with Power BI - one of the most developer intensive BI solutions around. Oh and Power BI hooks you into the entire MS server eco system.
And it is every managers wet dream!
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
And, and, and ...
... The customer bought EVERYTHING!
|
|
|
|
|
|
Oh, well, I see the neighbours are buying som adult toys
|
|
|
|
|
We just took the course: "marketing hype 101".
I'm in!
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
P.S.
“That’s one sure tip-off to the fact that you’re being assaulted by an Architecture Astronaut: the incredible amount of bombast; the heroic, utopian grandiloquence; the boastfulness; the complete lack of reality. And people buy it! The business press goes wild!” -- Don’t Let Architecture Astronauts Scare You – Joel on Software[^]
|
|
|
|
|
I have joined their webinar once. I have tried all their tutorials. The marketing videos and the ads lied. Microsoft's Power Apps suck. I would rather use old trustworthy WPF and Entity Framework if someone ordered a native Windows app from me.
Also there's no way a non IT manager can make her own proper program with Power Apps. Yeah.. she will leak all consumers' data to each other.
|
|
|
|
|
Very interesting. Thanks for sharing your experience.
That is exactly what I thought from watching the video too. It's just 100% hype.
|
|
|
|
|
I can't get my head around how one can avoid technical debt, because I think now it only something created after the fact.
consider making a new product: I, ME, wants to make version B of the product, because it will be better, meaning less "technical debt" (being bugs, and code short cuts, which will need refactoring to make for performance or means to expand features in future)
but I need to make version A to get to version B.
Sure with experience, version A might be closer to B, but this "inferior" version will still exist. With unlimited resources we could make version A a prototype, but practically A allows for generating some revenue to cover the starting costs.
Now from an outside viewer, they have the benefit of observation and can point out some technical debts that will be incurred.
but that outside viewer can also be your self, after making version A, and taking a step back to observe and go ah, yeah, this would be better if changed.
You go buy something with credit, you can see what the debt will be BEFORE accepting.
But can technical debt be observed before hand? Not include the, well well go with Option 1 now, and transition to 2 next year. You have already created what Option 1 is, thus in the stage of observing.
not sure what the point is, kind just felt like when someone new comes into a team, and first thing they start mentioning is technical debt this and that, and like, yeah, no sh*t, its easy to critique after the fact, how the projects you made before coming here looking.
|
|
|
|
|
|
Greg Utas wrote: I wrote an article that touches on a lot of what you said: The Software Rewrite[^]. I can highly recommend that article. Particularly the advice to refer to a proposed re-write as "re-engineering" to avoid scaring people.
|
|
|
|
|
I don't know what is worst...
- Thecnical debt
or
- hystorically grown (in Germany "Historisch gewachsen")
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|