Category: Technology

Open Source Project: Reach SDK

paschmann

Over the past few years I have found myself re-implementing and re-writing basic features of server, web, mobile or service components. Registration, Login, Forgot Password, Notifications, Search, Help, FAQ, Contact Us, Maps are just a few I can think of, where half way through the development everything seems familiar and I have a case of deja vu. No doubt I have written or implemented a library or service which performs this specific function.

While developing the Changd app I found myself in one of the deja vu moments while writing the email notification service, and decided to pause development, and fix the root cause. After multiple Github issues to support a variety of notification providers, I came across Apprise, a python library which supports multiple notification provides. Since there was not a Node.js implementation, I decided to use Apprise as inspiration and influence for a Node.js library which I aptly named “Reach”. read more

Easter eggs …

paschmann

May unity be the foundation to explore new grounds.

Every so often you get a product which delights you. A small nugget of wisdom, a token of appreciation or well thought out gesture, showing that the company or person who designed, or built the product, went just one step further than they needed to …

/imagine

paschmann

My first experiment with midjourney back in 2022. We were on our way to do some MTB riding with the group. It was all through Discord and predated some of the modern LLM’s (from what I can remember).

My first /imagine prompt:

photograph of a female astronaut inside a space ship with water droplets and the flight deck catching on fire

And a couple thereafter.

Publishing packages to NPM

paschmann

These are the notes/process I used when developing the Node Reach SDK package:

The “Standard” Release Process

Here is my understanding of the steps that are most commonly expected to be run when publishing a new version of an npm package.

  1. Safety Checks:
    1. git pull
    2. git status
    3. npm ci
    4. npm test
    Prepare the Release:
    1. npm run build
    Update the Changelog Update the Version Number:
    1. npm version
    2. Or by hand:
      1. Update version in package.json & package-lock.json
      2. git commit -am ‘2.0.0’
      3. git tag v2.0.0
      Publish to npm:
      1. npm publish
      Publish to Git:
      1. git push
      2. git push –tags
      Create a GitHub Release (optional)
      How to Publish an Updated Version of an npm Package

Enterprise Mobility @ SAP – Why apps matter ..

paschmann

This is another blog post of a series around the enterprise mobility IT team at SAP. We are an internal team focused on managing mobile devices, mobile applications, and developing custom apps for SAP’s 110,000 employees. I believe we have some unique stories, software, tools, and insights to help others in the community considering, or currently undertaking, some of the challenges which surround mobility and its adoption in the enterprise. As an SAP champion, I enjoy sharing and promoting my experiences and knowledge with others through the SAP Community, if you enjoy this post, check out some of my past content.

Introduction

A few weeks ago I gave a presentation on “Why apps matter …” for an annual internal SAP event called SAP Worx. These presentations highlight some of the important internal tools which IT develops to help our employees in their daily lives. While this was internally focused, I felt it could be beneficial to share some of the details and content behind what, we as a team, are focused on from a mobility perspective. read more