skinnyarms

3 of the top 5 graph databases on db-engines are open-source.

https://db-engines.com/en/ranking/graph+dbms

As for standards, absolutely. Gremlin and TinkerPop are both common ways to interface with Graph Databases that work across many different vendors.

That said, IMHO graph databases are pretty niche. SQL took off because the ability to normalize data when you store it and then relate it as needed when you query while still getting great performance for large-ish data (thanks to indices and query optimizers) is really powerful.

Am I missing something, it sounds like they are already doing this - not striking off on a new venture.

As for recurring, designers and publishers are always releasing new games and expansions. Games like Dungeons and Dragons, Warhammer, and Magic the Gathering are always releasing updates that encourage updating your materials. There are a few popular game awards, and the top x games from those tend to sell out everywhere.

There are some game shops that encourage playing but I don't know that I'd call it successful...just not enough money moving to justify the space.

I have a lot of fun with friends playing games like this.

Sometimes learning the rules can be tedious and annoying, but the more you play different games the more you see the same mechanics come up and it makes it easier. For us, the highs are worth the lows. We aren't the only ones either, the market is doing well: https://www.prnewswire.com/news-releases/board-games-market-...

You and your friends might be better served with a more casual game...or maybe it's just not your thing.

I'm really happy with the local development story too. We use skaffold to pick and choose which resources we run locally, and then we use the same definition to generate our artifacts which keeps things in line.

It reminds me of docker-compose file, except I can publish it too.

I'm a fan of the show, it was really entertaining to listen to knocking the site over "live".

There are tools that help this: Visual Studio Data Tools, RoundhousE, Flyway/Redgate - I highly recommend investing time in building them into your workflows.

Speaking strictly of schema...

Relational schema are flexible and allow for an optimizer to figure out how best to fetch your data based on the data are querying and filtering for and stored statistics about your data set.

Document oriented storage is great when you don't need the optimizer because you already know how the data is written and read. This means you can bundle it up into small, single fetch documents. No statistics or optimizer necessary. This is great if you understand your use cases really well, and they never change (good luck with that) or you have a large distributed data set that would be tough on an analyzer.

I thought the same till I tried it, ended up being more fun than I realized. If you watch other streamers, you'll see that most aren't racing through - they're just casually coding...socially.

Fellow Orlandonian here, the salaries are not great. I haven't seen the ODevs salary survey from 2019, but if you look at 2018 you're good for the area: https://orlandodevs.com/blog/salary-survey/

I recommend working remote.

I would read that article, and vote it up, but I don't think we need to be harsh towards this one. It's a good read, makes some good points and I'm thankful for it.

Maybe you need to examine what your true goal is. Why do you want a side project? Are you doing it because you feel like you are supposed to have side projects, or because you actually want to accomplish a goal? If it's the former, you could try to align the side project with another goal of yours - say learning some new language or framework.

If you are just trying to build a portfolio you can come up with a (small) "SMART" goal, and commit to completing it. After you reach the milestone you can make a conscious decision whether to continue or not - but either way you have _something_ completed.

https://en.wikipedia.org/wiki/SMART_criteria

I'm excited anytime a technology comes along that makes for great user experience AND developer experience. I can demonstrate the value that Hasura provides to either side in minutes.

The subscriptions are particularly interesting to me, I've never seen anything else that makes web sockets so easy to implement. I'm very optimistic for their future.

I just wanted to point out that Elastic has made some changes in the last year or so that help with security like...

* [Making security bits available with the ("free") basic license](https://www.elastic.co/blog/security-for-elasticsearch-is-no...) * [Releasing Kubernetes Operators with security enabled by default](https://www.elastic.co/guide/en/cloud-on-k8s/current/index.h...)

This has the effect of making most "getting started" guide setups more secure by default, which is good.

Unfortunately this is a new change and those bits are not in the Apache licensed core offering, but it's still a big improvement IMHO.

I really enjoyed the v6 version of this one for Elastic: https://www.udemy.com/course/elasticsearch-7-and-elastic-sta...

And as for Docker, this was my favorite: https://www.udemy.com/course/docker-and-kubernetes-the-compl...

I've watched a bunch of this guys Kafka courses too, and they were all fantastic so I would recommend any thing that he's got if it picques your interest: https://www.udemy.com/courses/search/?q=stephane%20maarek&sr...

Glad to see someone mention this course. It and several other courses that he published were very helpful getting me up to speed on Kafka.

I've had really good luck with programming topics, specifically Docker, Kubernetes, Kafka, and Elasticsearch. These are narrow topics that you are unlikely to find on Coursera and many of the courses are published by well known figures in their respective communities. I have yet to hit a bad one.

Udemy has a 30 day refund policy as well, so you can try a course out with low risk.

I love podcasts and I'm glad for any service that helps me find useful content. That said, I'm not quite getting how I'm supposed to be using this. From a consumer viewpoint, I have a front page recommending episodes and a weekly summary. I get that, cool.

Now if I want to heart episodes to tell other listeners about episodes I particularly enjoy...I go to the website and search/submit the episode...I guess?

Anyway, I'm interested - I just wanted to share my first impression in case it was useful.

Woah, uh...that's weird. Thanks!

I love podcasts and I'm glad for any service that helps me find useful content. That said, I'm not quite getting how I'm supposed to be using this.

From a consumer viewpoint, I have a front page recommending episodes and a weekly summary. I get that, cool.

Now if I want to heart episodes to tell other listeners about episodes I particularly enjoy...I go to the website and search/submit the episode...I guess?

Anyway, I'm interested - I just wanted to share my first impression in case it was useful.

Technical goals: Double down on existing investments, with a focus on real-time analytics and user experiences.

Desired results: • Cloud Certifications (provider TBD) • Competent in Spring and React • Major side projects stable, documented: • Grafka v1.0 • QIT v2.0

Systems • 1 hour every morning, 5 days / week • 4 hour scheduled block 1 day / month

I've always been that way. Before the cell phone revolution I kept a map in my car that got used way, way, way too often. It just never stuck.

I was quite the bike explorer in my youth too. :shrug:

Why so harsh?

This isn't production code published by Microsoft, it's an "enthusiast's take" written by a student learning to code. Most of my college colleagues couldn't make it through FizzBuzz.

Hopefully a bright new programmer doesn't get discouraged by getting smacked down in the top comment on hacker news.

I've hosted several small apps with Netlify, and I recently setup my first blog/brochure type site using Netlify CMS. It's awkward, but it's amazing to me what you can accomplish with a (free) build server, a couple small 3p services, and a CDN with so little effort.

Great dev experience, great user experience.

A quick google of "CFS exercise" lead me to few articles, this is the one I'm reading now: https://www.npr.org/sections/health-shots/2017/10/02/5543693...

The information is sourced from the official CDC guidelines on ME/CFS: https://www.cdc.gov/me-cfs/index.html

Most tech podcasts tend to focus on interviews, but I tend to shy away from those.

There are quite a few shows that are different though, either discussion or news based. Here are a couple of my favorites. * Coding Blocks * Complete Develop Podcast * Six Figure Developer * Weekly Dev Tips

Full disclosure, host of CB here :)

Love this show, you did a great job!

There are a couple of open-source sites I work on to help devs find podcast content.

Qit is designed for finding/playing shows by topic, so you can (for example) search for shows about GraphQL: https://qit.cloud/search/graphql

devpodcasts.app lets you browse shows by latest release or by tag: https://devpodcasts.app/shows

Looks like devpodcasts.app is a bit behind though, so I'll write a ticket and get that fixed up soon :)

If my app runs off multiple API, then the bug in my (for example) commenting API shouldn't prevent users from using the shopping cart API to check out.

How about build-time rendering?

Server-Side rendering tightly couples your front-end to your application server. Scaling the site means scaling up that application server. A bug in one "page" of the app can cause the whole application server to go down.

If you leverage client-side rendering then it's easier to decouple your front-end from the back meaning you can take advantages of things like segregated micro/serverless services and progressive web apps. You can also re-use those services for multiple applications, making it easier to keep the business logic OUT of your pages and in an API layer where they belong.

I agree that SPAs are not the solution for everything, but I think that server-side rendering is on it's way out.