Twitter | Procurar | |
Rod Johnson
CEO, Atomist. Creator of Spring, Cofounder/CEO at SpringSource, Investor, Author
4.853
Chíos
761
Seguindo
30.338
Seguidores
Chíos
Rod Johnson 12 h
Respondendo a @springrod
And it's got to stop and it's got to stop fast.
Reply Retweet Gústame
Rod Johnson 12 h
Respondendo a @springrod
They're sending people that have lots of problems, and they're bringing those problems with them. The press speaks to MPs and they're telling us what we're getting. And it only makes common sense. They're sending us not the right people.
Reply Retweet Gústame
Rod Johnson 12 h
When Eton sends their prime ministers, they're not sending their best.
Reply Retweet Gústame
Rod Johnson 13 h
Pleasantly surprised at how easy it was to add Swagger API documentation to a Node/Express app with swagger-ui-express. The only frustration was silent failures due to formatting errors in swagger.yaml. Sigh.
Reply Retweet Gústame
Rod Johnson rechouchiou
Brian Goetz 21 de xul.
Respondendo a @springrod
In order to understand this tweet, you first have to understand “abstraction layer”. Most reply-ers seem to have failed this test.
Reply Retweet Gústame
Rod Johnson 22 de xul.
Respondendo a @brunoborges
Some types of criminal convictions go away in time, in many jurisdictions. Words on social networks don't, plus they can be taken out of context. We've created a scary world.
Reply Retweet Gústame
Rod Johnson 22 de xul.
Such an important point. Getting the optimal mix of education, incentives to do the right thing, and verification is key. Plus listening. Teams must be able to feed back. Top down approaches are rightly resented, and don't work.
Reply Retweet Gústame
Rod Johnson 22 de xul.
Respondendo a @hsjawanda
Assuming that you'd query that data anyway, they shouldn't make any difference. Plus materialized views are an option in some databases
Reply Retweet Gústame
Rod Johnson 22 de xul.
Respondendo a @kuhn_reinhard
Put your DDL in source control
Reply Retweet Gústame
Rod Johnson 21 de xul.
Respondendo a @JeffGrigg1
I would certainly not recommend building a *whole* system that way, nor did I
Reply Retweet Gústame
Rod Johnson 21 de xul.
Respondendo a @recena @connolly_s
Right. And that's sad
Reply Retweet Gústame
Rod Johnson 21 de xul.
Respondendo a @recena @connolly_s
Largely in SQL. If not, the logic should certainly be elsewhere
Reply Retweet Gústame
Rod Johnson 21 de xul.
Respondendo a @recena @connolly_s
They're usually expressed in SQL, not some mapping
Reply Retweet Gústame
Rod Johnson 21 de xul.
Respondendo a @DoerteDev
I doubt I'd want to join
Reply Retweet Gústame
Rod Johnson 21 de xul.
Too many app developers undervalue the potential of triggers, stored procedures and views as an abstraction layer when using an RDBMS.
Reply Retweet Gústame
Rod Johnson 20 de xul.
Respondendo a @codefinger
Defining it in XML was the core problem.
Reply Retweet Gústame
Rod Johnson 20 de xul.
Respondendo a @codefinger
Good idea. Horrible in practice. And slooooow, at least in the benchmarks I did
Reply Retweet Gústame
Rod Johnson 19 de xul.
Respondendo a @TDwelve
"Thinking about" is fine. It's when things get unduly complicated by *implementing* premature optimizations before the problem space is fully understood that it can get nasty, in my experience.
Reply Retweet Gústame
Rod Johnson 19 de xul.
While premature optimization is evil, it *is* important to ask the question "could this ever be efficient?" Otherwise it's easy to design interfaces etc that are fundamentally broken and will need to change incompatibly.
Reply Retweet Gústame
Rod Johnson rechouchiou
Atomist 19 de xul.
Automate away toil with container-driven automation in SDM 1.6.
Reply Retweet Gústame