Greg L. Turnquist

Sr. Staff Technical Content Engineer @CockroachDB, Best-Selling Author, Conference Speaker, YouTube Content Creator.

[Greg L. Turnquist @gregturn]

I'm leaving social media...

...forever!

https://t.co/i4qzro9WwZ

[Greg L. Turnquist @gregturn]

😂

[Greg L. Turnquist @gregturn]

@therealdanvega @reneritchie Text me when you get the answer. I’ve heard about this coming out for three years.

[Greg L. Turnquist @gregturn]

I miss this!!!!!

[Andrew Price @andrewpprice]

3D artists today have no idea how to build this

[Greg L. Turnquist @gregturn]

@RyanDGriggs Funny seeing the replies that realize VOLUME of interest is BAD...

[Greg L. Turnquist @gregturn]

What happens to your database that you just can't kill when you suffer a regional failure? Find out on today's episode of SELECT STAR!
https://t.co/CFmOgAU0CT

[Greg L. Turnquist @gregturn]

@deepakl_2000 I haven’t read a Java book in ages so not sure I can recommend the best.

[Greg L. Turnquist @gregturn]

I started off with Java 1.1, which was the material in Java In A Nutshell, 1st Edition.

This was the version that had AWT but not Swing.

And I also had a copy of Visual J++, and was REALLY frustrated that half of the code in that book DIDN'T WORK!!!!

[IntelliJ IDEA, a JetBrains IDE @intellijidea]

When did you join the Java gang? ☕
Was it love at first JDK download? 😍
#Java30Countdown #Java30

[Greg L. Turnquist @gregturn]

@ramnivas @ShadajL Congrats!!!

[Greg L. Turnquist @gregturn]

Are you using .NET and need to use an entity management toolkit? Then checkout how https://t.co/5Elp8CISS7 ties in with CockroachDB on today's episode of SELECT STAR!

https://t.co/TfKobENrLa

[Greg L. Turnquist @gregturn]

You didn't know?

Spotify is the ONLY shop that has a shot at taking both YouTube and Amazon down a peg or two.

* They scooped up Anchor and are becoming one of the top players in podcast sourcing including support for video podcasting. We simply livestream on YouTube through StreamYard, then grab the result and drop it on Spotify along with the same thumbnail and text (reformatted into HTML courtesy of ChatGPT.

* They bought Findaway Voices and thus have the largest audio book distribution outside of Amazon/Audible.

Spotify knows that content creation is growing exponentially and are going wide!

[Greg L. Turnquist @gregturn]

@starbuxman “I want to work on the color schema, but Jimmy says that’s too much stone-shedding.”

[Greg L. Turnquist @gregturn]

@bsideup jQuery?!?

[Greg L. Turnquist @gregturn]

@chrylis Pretty sure that was the same bundle I bought. I think was Visual J++ with NT threw in on the side.

And I jumped at it for that reason.

[Greg L. Turnquist @gregturn]

I had a copy once with my copy of Windows NT.

It had the coffee cup logo.

It could run maybe half of the code in Java In A Nutshell.

[IntelliJ IDEA, a JetBrains IDE @intellijidea]

Dig the past, find surprises. 👀
#Java30Countdown #Java30

[Greg L. Turnquist @gregturn]

😂

[CockroachDB @CockroachDB]

An inside look at how CockroachDB leverages the Network Time Protocol (NTP) along with software-based compensation techniques to achieve reliable time coordination across database nodes.
https://t.co/OIlkdgsZBR

[Greg L. Turnquist @gregturn]

In T-5 hours, @robreid_io will be joining us to talk about migrating your apps to the database you just can’t kill, along with a host of other topics.

Don’t miss it!

https://t.co/C7iICofWbv

[Greg L. Turnquist @gregturn]

1. I’ve mentioned SQL as the “first” DSL for quite some time. It’s evident that a sub language aimed at data querying that is simple and easy to read his this mark.

2. Even more importantly, the market has spoken. SEQUEL was built to be “reachable” by more than old gray neck beards. And reach it has. A past colleague of mine once said “SQL isn’t rocket science.” And he was right. And easy to use declarative query language has cemented relational database access across the industry.

When seasoned pro coders, fledgling beginner coders, business analysts, and even program managers can approach SQL and harvest value everybody wins.

And a winning solution will continue being used.

3. We tried ORMs. And they are still somewhat popular. But people putting them back on the shelf when confronted with challenging situations. Performance issues. Impedance mismatches. ORMs are proving to NOT be the universal solution that SQL is.

Yes, don’t let your users provide unsanitized inputs to your queries. Doh!

I have spoken with industry veterans than when confronted with hard requirements often must shed every ounce of unneeded “help” possible and get their hands directly on the SQL.

Sounds like SEQUEL may have hit its original objectives quite well.

[Sean McBride @bushidocodes]

The original SEQUEL paper from 1974 is mostly focused on the "console language" use case that Uncle Bob highlighted. Used in this way, SEQUEL enabled direct querying by business analysts that wouldn't know what Edgar Codd meant by "first-order predicate calculus" in his relational database papers.

In fact, the language is called SEQUEL because the previous language SQUARE used terse math-like syntax, and this was considered too difficult for such non-technical business users. SEQUEL was made more verbose and English-like to be more approachable to non-technical business folks that might only run a few queries a year. Other tools designed with this target audience include COBOL, CODASYL data languages, and the RPG language.

While the paper doesn’t mention embedding SQL explicitly, it does make a few implicit references that hint that this was perhaps under consideration as a future enhancement.

First, the introduction opens as follows:

As computer systems become more advanced, we see a gradual evolution from procedural to declarative problem specification. There are two major reasons for this evolution. First, a means must be found to lower software costs among professional programmers. The costs of program creation, maintenance, and modification have been rising very rapidly. The concepts of structured programming have been introduced in order to simplify programming and reduce the cost of software. Secondly, there is an increasing need to bring the non-professional user into effective communication with a formatted data base. Much of the success of the computer industry depends on developing a class of users other than trained computer specialists.

The paper then goes on to focus on the second reason. However, the introduction begs the question: might SEQUEL also be somehow used to simplify programming and reduce the cost of software?

Additionally, the paper calls SEQUEL a "sublanguage." Does a sublanguage imply a superlanguage? If so, that term might be 1970s for "embeddable DSL."

Given the fact that relational databases were considered a next-gen CODASYL, and CODASYL was an evolution from the DATA DIVISION in a COBOL program, it seems very likely that embeddability in host languages was in the mind of IBM Researchers.

Source: https://t.co/oValzIGlPE

[Greg L. Turnquist @gregturn]

Five of my sites got hacked.

EVERYTHING is up for grabs.

One had been built up with a python script run by GitHub actions published to GitHub pages replacing the previous Wordpress site creating my own https://t.co/OIpYy4FI1K. It’s a LOT faster now.

Another has been my personal name site. It too was Wordpress. Now it’s statically generated @astrodotbuild site run by GitHub actions published to GitHub pages. It’s a LOT faster now and easier to manage.

I’m in the middle of rewriting my @ProCoderShow site and using a lightweight shopping cart service that may let me ditch a couple more expensive SaaS tools, cutting costs in half. It’s also MUCH faster!

And with Cloudflare in the equation, caching static html will be MUCH better!