I was thinking about "it shouldn't be easy". I talk to a lot of founders, and there's a subset that sees SaaS as a "hustle game." You find a niche with a problem that can be solved without a sizeable technical effort—maybe even with a no-code platform—and then the real work is marketing it. A lot of SaaS culture promotes this mindset. This is why we had to start a SaaS developer community: The SaaS communities didn't see engineering as a central concern or capability. It was all sales, marketing, and customer support. The problem with this mindset becomes apparent the first time you try to buy a product from one of these SaaS companies. Talking to the founder with your customer hat on. At some point, you raise a problem and ask, "Does your product solve this for me?" And the founder says, "Oh no, we can't solve this one. This is really hard. We solve these other things." "Right, these other things are nice," you say. "But I need the hard problem solved. I know it is hard, so I'm looking for a product that solves this for me". At this point, you can go in circles for a while, with the founder trying to convince you that you shouldn't want the hard problem solved because it will be hard to solve. The thing is, most of the easy problems are not that valuable. If they were valuable and easy, they'd be solved already. You may get lucky with an overlooked, easy, and valuable problem. But luck is not a strategy. The real value to customers is when you solve their hard problems. Ideally, you solve them so well that the world forgets that this used to be impossible.

Join us for our 20th anniversary! We will celebrate 20 year of aicas in May. You can find our virtual events at lnkd.in/duVai7m.

The latest Draft of RTSJ 2.0 has been posted: aicas.com/download/rtsj/rtsj… More than 80% has been implemented. #jcp #aicas20yrs #rtsj

Here are some more of the group!

The Final Approval Ballot for RTSJ 2.0 has been accepted by all members! jcp.org/en/jsr/results?id=62… #RTSJ #jsr282

Celebrating 20 years of the OSGi Alliance with Dan Banndera! #OSGi #EclipseCon

Happy to welcome Amazon to @jcp_org and looking forward to their participation in the community!

The first day of sessions at #EclipseCon19 are complete! Today, @mmilinkov presented his State of the Community Keynote!

So does that mean that if Rick Perry asked Mr. Trump to jump off a bridge, he would do that too?

JSR282 Draft 76 (aicas.com/cms/sites/default/…) has been posted for Public Review! #rtsj #jcp

Thanks to @Twitter for hosting our JCP EC meeting today @TwitterSF - we value your support for the @Java community serving on the EC!

We are now ready for Public Review! Draft 72 is available here: "aicas.com/cms/en/rtsj ". #rtsj #jsr282

Unintentional Object Retention is another name for memory hoarding. I find memory hoarding easier to remember, but let us stamp out the use of memory leak for Java programs. That is an unmanaged language, e.g., C and C , problem, not a Java problem. #java #managedlanguages

All issues have been clarified. This is the last internal review before for Public Review! Draft 71 is available here: "aicas.com/cms/en/rtsj". #rtsj #jsr282

This is great and the timing is good since the specification is finished! #RTSJ #JSR282 x.com/ericjbruno/status/1002…

Memory Leaks in Java are a myth. A memory leak is when memory is no longer reachable. In Java, one can only hoard memory, but not leak it! There is always a path to memory that is being hoarded.

RTSJ 2.0 Draft 67 is now available: "aicas.com/cms/en/rtsj ". The specification is complete, but some small issues for Affinities needed addressing. #rtsj #jsr282

RTSJ 2.0 Draft 66 is now available: "aicas.com/cms/en/rtsj". The specification is not complete and ready for Public Review. Next comes the RI and TCK. #rtsj #jsr282

I am going to the "2017 JCP Party & Awards Ceremony". See you there? eventbrite.com/e/2017-jcp-pa… via @Eventbrite

RTSJ 2.0 Draft 63 is now available: "aicas.com/cms/en/rtsj ". Schedulers and CPU affinity have been harmonized. #rtsj #jsr282