Emerging Market Software Blog

The IT Technology Chasm

published on 2019/05/11

This is a very cool project that allows people to run Swift on Web Assembly. This project represents the bleeding edge of software development technology that allow static languages to produce software that runs on a browser by targeting a standard. Blazor.NET technology allows .NET developers to use C# and F# to target Web Assembly.

On the other spectrum, the majority of developers and IT departments are running on mature and legacy systems.

For all of this variety of reasons and more, the majority of companies that are at the pinnacle of succes in America are quietly running Windows Server 2012 behind the scenes.

And, not only are they running Java on Windows 2012, they’re also not doing machine learning, or AI, or any of the sexy buzzwords you hear about. Most business rules are still just that: hardcoded case statements decided by the business, passed down to analysts, and done in Excel sheets, half because of bureacracy and intraction, and sometimes, beacause you just don’t need machine learning.

Vicky Boykis

The approach we take in SilverKey for our technology stack reflects on this chasm.

For our data storage and related infrastructure services, we are very conservative. Most of our project rest their data foundation on tried and proven RDBMS technology such as SQL Server and Postgres. We use RabbitMQ for messaging and Redis for caching. Our ORM of choice has been continuously developed since 2003.

Our choice of JavaScript framework, Vue.js, is also conservative. We choose it because it is sensible and does not try to do too much.

On the other hand, we are very aggressive in using every advanced development framework such as ASP.NET Core 3.0 (still in previews). Our very popular ASP.NET Core samples is up to date with the latest version of ASP.NET Core 3 previews. We start using Blazor.NET to our mainline development. We have been using Flutter before it reached 1.0 last year.

So far this dual approach has served our needs well in delivering software for our clients. We do keep in mind that not everybody take or able to take our approach.

Remote work is the future of work

published on 2019/05/08

Foster is an evangelist for flexible work. Zapier has been all-remote since he co-founded it eight years ago, for good reason: no overhead costs, the ability to recruit from anywhere, satisfied employees and therefore better retention. With the advent of cloud computing, video-conferencing and instant messaging, arrangements like Zapier’s are becoming more common. According to the U.S. Census Bureau, 8 million Americans now primarily work from home, with more than half of them working for companies, not themselves.

marketplace.org

Remote work makes sense whenever applicable.

  • It reduces the demand for large office space.
  • It allows flexibility for employees with special needs.
  • There is no need to commute.
  • It allows people to stay in their cities instead of moving to new city.

All of us in SilverKey have done work remotely. Some of us do it full time. We simply arrange the way we work accordingly.

Open source extension for automated failover and high-availability in PostgreSQL

published on 2019/05/08

Today, we are excited to introduce pg_auto_failover, an extension for automated failover in Postgres. It takes care of keeping your Postgres database available, so you don’t have to. pg_auto_failover is focused on simple, automated failover built on Postgres streaming replication, without any external third-party dependencies. Here is how it works:

Microsoft Cloud Blogs

This is amazing. Postgres is our default RDBMS of choice due to its features, stability and open source nature. This extension will add more reliability options to Postgres databases and it looks simple to use.

Open Source Project is hard

published on 2019/05/05

I urge the Requests project maintainers to transition their project to a more normal, less dysfunctional governance model. You can acknowledge his contributions without buying into his personal mythology. His insights are not irreplaceable. You know this situation is harming you and your users. You and your users are more important than his ego.

vorpus.org

Modern software relies a lot of open source software. This story is specifically related to a popular Python library but the lessons can be learn by all practitioners.

Tangentially related lecture: the hard parts of open source.

Collaborative engineering has more problems in collaboration than engineering. Those 'soft' skillsets do not correlate well with technical expertise, especially when filtered through asynchronous (and often pseudonymous) text-based communication. Additionally, some foundational assumptions about the nature of improving technology and society turn out to not work so good.

reddit

Small is beautiful

published on 2019/04/29

a tweet about the Hertz project

Source

Software project is hard but huge firms do not have better success rate than smaller firms. The inverse is true. There are plenty of evidence of disastrous software projects performed by the big 4.

Hertz is suing for the $32m it paid Accenture in fees to get to that aborted stage, and it wants more millions to cover the cost of fixing the mess. "Accenture never delivered a functional website or mobile app," Hertz claimed.

The Register

If you want to get something innovative done, go small.