|
Rod Johnson
@
springrod
Sydney / Bay Area
|
|
CEO, Atomist. Creator of Spring, Cofounder/CEO at SpringSource, Investor, Author
|
|
|
4.853
Chíos
|
761
Seguindo
|
30.338
Seguidores
|
| Chíos |
|
Rod Johnson
@springrod
|
12 h |
|
And it's got to stop and it's got to stop fast.
|
||
|
|
||
|
Rod Johnson
@springrod
|
12 h |
|
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.
|
||
|
|
||
|
Rod Johnson
@springrod
|
12 h |
|
When Eton sends their prime ministers, they're not sending their best.
|
||
|
|
||
|
Rod Johnson
@springrod
|
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.
|
||
|
|
||
| Rod Johnson rechouchiou | ||
|
Brian Goetz
@BrianGoetz
|
21 de xul. |
|
In order to understand this tweet, you first have to understand “abstraction layer”. Most reply-ers seem to have failed this test.
|
||
|
|
||
|
Rod Johnson
@springrod
|
22 de xul. |
|
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.
|
||
|
|
||
|
Rod Johnson
@springrod
|
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. twitter.com/kennybastani/s…
|
||
|
|
||
|
Rod Johnson
@springrod
|
22 de xul. |
|
Assuming that you'd query that data anyway, they shouldn't make any difference. Plus materialized views are an option in some databases
|
||
|
|
||
|
Rod Johnson
@springrod
|
22 de xul. |
|
Put your DDL in source control
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
I would certainly not recommend building a *whole* system that way, nor did I
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
Right. And that's sad
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
Largely in SQL. If not, the logic should certainly be elsewhere
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
They're usually expressed in SQL, not some mapping
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
I doubt I'd want to join
|
||
|
|
||
|
Rod Johnson
@springrod
|
21 de xul. |
|
Too many app developers undervalue the potential of triggers, stored procedures and views as an abstraction layer when using an RDBMS.
|
||
|
|
||
|
Rod Johnson
@springrod
|
20 de xul. |
|
Defining it in XML was the core problem.
|
||
|
|
||
|
Rod Johnson
@springrod
|
20 de xul. |
|
Good idea. Horrible in practice. And slooooow, at least in the benchmarks I did
|
||
|
|
||
|
Rod Johnson
@springrod
|
19 de xul. |
|
"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.
|
||
|
|
||
|
Rod Johnson
@springrod
|
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.
|
||
|
|
||
| Rod Johnson rechouchiou | ||
|
Atomist
@atomist
|
19 de xul. |
|
|
||
|
|
||