Forem: opt-nc

🥳 We built the cli of our dreams to send sms ❣️

adriens — Mon, 14 Apr 2025 21:48:18 +0000

🤔 About the benefits of `cli`

Since a few years now, we started to design various cli for internal batch usage, on our Java Stack on top of picocli and quarkus, delivered as images, and run on podman.

Our goal was to :

Avoid as much as possible to write unnecessary documentations : each tool should describe himself according to a common pattern
Rely on the best possible practices
And overall : deliver a consistent first-class UX to OPS

Therefore I started to read and follow the following site to follow the best possible guidelines :

cli-guidelines / cli-guidelines

A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.

Command Line Interface Guidelines

An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.

This is the source code for the guide. To read it, go to clig.dev.

Join us on Discord if you want to discuss the guide, or just chat about CLI design.

Contributing

The content of the guide lives in a single Markdown file, content/_index.md. The website is built using Hugo.

To run Hugo locally to see your changes, run:

$ brew install hugo
$ cd <path>/<to>/cli-guidelines/
$ hugo server

To view the site on an external mobile device, run:

hugo server --bind 0.0.0.0 --baseURL http://$(hostname -f):1313

License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

View on GitHub

🎯 Our `Go`(al)

On my very own side I gave a try during a hackathon to Go and goreleaser :

adriens

Jan 11 '25

⏳GitHub Copilot 1-Day Build Challenge : eol, a tiny Go client to manage eols

#devchallenge #githubchallenge #ai #go

Comments 9

2 min read

Then, I wanted to bring my team to the Go experience at the office as sometimes we need to deliver apps to systems on which we don't want or can't install new softwares : so delivering a static binary thanks to Go and goreleaser seemed a good option for effortless cross-compilation... and of course build the best possible UX thanks to Cobra.

So I used this opportunity to sharpen our skill with my team :

// Detect dark theme var iframe = document.getElementById('tweet-1909597554590855170-986'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1909597554590855170&theme=dark" }

And...

Build the best possible cli of our dreams to send sms from a terminal and see what we can deliver and learn from that.

🍿 `v1.0.0` `brew` unboxing

📜 The story behind the product development

As I always say to my team & student, always "Start with why" :

// Detect dark theme var iframe = document.getElementById('tweet-1910458188945867005-564'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1910458188945867005&theme=dark" }

After having drafted my ideas :

// Detect dark theme var iframe = document.getElementById('tweet-1908757267941666914-566'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1908757267941666914&theme=dark" }

Here are the motivations that kept us on track :

Do things extremely :

🧩 Interoperable
🫴 Easy to integrate for anyone (even on legacy systems)
⚡ Efficient
🦥 Useful : make people save time, ie. make more with less effort
📦 Easy to deliver and install
🤩 Beautiful
📉 Fast to build : for an improved Time to market
🟢 Fast to (learn to) use
💡 Inspiring for us and others, eg. create new business opportunities ideas
😍 Desirable : people should feel the desire to use the product and feel joy while using it
🧑‍🤝‍🧑 Create new relationships with people and discover new practices

🔭 What's next

Next, we'll focus on showing and sharing the benefits :

♾️ Continuous delivery tools and automation
📼 New ways of documentation with next-gen tools
🛡️ Security (beacause it always matters)
🦸 One liners (because they're both a cool and efficient way to get things done)
🐧 Classical linux tools
📚 General IT Culture
🧑‍🎨 Creative product design and development

Hopefully you'll like it as much as we do...and will engage yourself on the same kind of way : the #learnbydoing journey 🤗

Microcks for dummies

Supervinh — Thu, 09 Jan 2025 00:19:39 +0000

🤔 Microcks: For Whom and For What?

How can you tell if API documentation:

Is properly documented ?
Is sufficient for effective usage ?
Allows partners/clients to efficiently test ?

This is exactly what Microcks, an open-source tool, promises to deliver. Its benefits have already been explored in one of OPT-NC’s public APIs for agency waiting times.

// Detect dark theme var iframe = document.getElementById('tweet-1862247586411028971-410'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1862247586411028971&theme=dark" }

🤓 Spoilers

📜 Annotations and REST API Documentation Quality

Why document a REST API using annotations directly in the source code?

💡 Clarity for developers: Annotations precisely describe endpoints, parameters, and responses, making the API easier to understand.
🔄 Automatic updates: Generating OpenAPI documentation from annotations ensures that it stays aligned with the source code in a simple and efficient way.
📚 Concrete examples: Annotations also allow adding example calls, helping developers understand practical use cases.

Here’s an example of annotations:

@GET
@Path("/endpoint")
@Operation(
        summary = "Operation summary",
        description = "Detailed description"
)
@APIResponses(
        value = {
                @APIResponse(
                        responseCode = "200",
                        description = "OK response",
                        content = @Content(
                                mediaType = "application/json",
                                schema = @Schema(implementation = MyClass.class),
                                examples = {
                                        @ExampleObject(
                                                name = "Example 1",
                                                value = "{'key':'value'}"
                                        )
                                }
                        )
                )
        }
)
public ReturnValue myFunction() {}

And to describe request parameters:

@GET
@Path("/endpoint/{id}")
public ReturnValue myFunction(
        @Parameter(
                description = "Expected ID",
                schema = @Schema(type = "integer"),
                examples = {
                        @ExampleObject(name = "Example ID", value = "123")
                })
        @PathParam("id") int id
) {}

Validation and Security with Swagger:

✅ Validation of parameters and responses.
🔒 Endpoint security to prevent injection attacks.
🚫 Rejection of invalid values (e.g., negative numbers for non-allowed parameters).

But documentation - and hence its quality - must also be tested!

💼 Enter Microcks: This open-source tool generates mocks from OpenAPI annotations, enabling:

🌐 API testing without actual deployment.
🧪 Evaluation of documentation quality and completeness.
📊 Scoring for OpenAPI compliance to ensure high standards.

With Microcks, documenting is not just writing, it ensures everything works as expected, leading to robust, well-documented APIs. -> ...that can be embedded as part of a CI

🚀 Microcks: Boosting Developer Experience

Thanks to annotations and the mocks generated by Microcks:

📝 Clarity even before development: API functionalities are defined upfront, making communication between developers, test managers, project managers and future users easier.
⏱️ Time-saving: Development and documentation can progress in parallel, optimizing project resources, allowing those depending on the API to start development even before the API itself is implemented.

Microcks transforms how APIs are designed, tested, and shared, creating a seamless and efficient DEVEX (developer experience).

🔍 Microcks and the Testing Pyramid

Among the various representations of testing strategies, Watirmelon’s model stands out as particularly insightful.

🧩 Microcks fits into the Automated API Tests layer, with a particular focus on Contract Testing, ensuring that APIs adhere to their specifications.

🎯 Personal and team benefits

✅ Documentation quality: I was pleasantly surprised by the clarity and precision of the documentation provided by Microcks.
🎨 Intuitive user interface: The UI is simple, intuitive, and very enjoyable to use, making the tool accessible right from the start.
⚡ Developer responsiveness: The contributors of Microcks are highly active on GitHub and respond quickly to issues, which is reassuring when resolving potential roadblocks.
🚀 Unblocking my tests: In my last project, I struggled to mock calls to OpenSearch. With Microcks, I no longer need to mock the calls. I can simply simulate the database to contact, which saves time and greatly simplifies testing.
🔮 Usefulness for future projects: Microcks will be invaluable for my future projects, especially during the development phases. Instead of relying on paid APIs, I can simply use my Microcks mock, which is both more economical and practical.

Microcks has proven to be a powerful ally, not only for this project but also for those to come.

🔁➡️📘 Kafka documentation automation : HUGO, gomplate, Github Actions & pages

adriens — Wed, 18 Sep 2024 20:30:38 +0000

💭 "what's wrong with writing (and maintaining) docs ?"

Very often a single team has a privileged access to a set of data, services, middlewares and you cannot grant access because of technical limitations (sometimes due to limited licences plans), costs, access control strategies
or so many other reasons : there may me plenty of them.

👉 Still, it is not rare that third parties need to have at least a partial access to these resources, for example to develop new services on top of yours.

💸 The cost of manual legacy documentation

The consequence is that you may be asked to implement a Wiki (eg. on Confluence) that your team will be charged to maintain in addition to its core activities.

Then you grant access to this wiki and everyone is happy..or so you think... as

you have just increased the RUN load of your team... and then impacted your own "Time to Market" to deliver new bankable services.

To make simple, the problem with this strategy is that :

😫 It will cost you a lot of time
🏋️ You have to stay up-to-date with sometime - and hopefully for you - very fast changing systems
📉 You waste your team skills & workforce on writing most of the time outdated documentations

♾️ Embracing continuous change

What we want is a SchemaCrawler like portable and static report of our onPrem Kafka so we can embrace the change comfortably and continuously.

🎯 The "What" & the "How"

This post is about this common pattern and how we delivered a scalable data-driven documentation pipeline around Kafka, based on data & CI:

💰 We already have the automatically data prepared & delivered as csv and json by scheduled GH Actions on a third party repository
🦥 On a dedicated Wiki-like repository we clone the part of the data we need
🔁 Thanks to templates & gomplate we transform csv and json into nice markdown
🎁 We build & deliver the resulting static site with HUGO Github Action on GH Pages
🤩 We enjoy the HUGO shadocs theme

💰 Benefits

Below some benefits we immediately got

🔄 Up-to-date documentation
🛡️ Data security thanks to custom obfuscation so the doc can be shared with confidence to third parties
⚡DevEx impact : third parties get informations "as a Service", whenever they need it 24/7 : no need to make an issue...
🤩 Responsive wiki and amazing UI (PC, tablet and even phone)
🌟 Continuously improving documentations, howtos and resources
"🎀 as a Service" delivery
🔗 Linked to classical/legacy static documentations... in both directions
🔐 GitHub driven Access management (Teams, SSO,...)

🍿 Demo

💪 The magic of `gomplate` : `csv` to `markdown`s

The core magic that transforms a single input csv file into more than 100 separate markdown (in less than 1' ) is below :

in: |
  {{ $topics := (datasource "topics") | data.ToCSV | data.CSVByRow }}

  {{ range $i, $e := $topics }}
    {{ $file := $e.name | strings.Slug }}
    {{ tmpl.Exec "topicT" . | file.Write (print "outputs/topics/" $file ".md") }}
  {{ end }}

templates:
  - topicT=template/topic.tmpl
datasources:
  topics:
    url: source/import/auto/kafka/node_kafka_topic.csv
outputFiles: ["csv"]

suppressEmpty: true

🤩 Then HUGO does the rest within GitHub to deliver a whole functional website : the overall process takes less than a minute.

🔑 APIGEE 101: onboarding & authentication

adriens — Mon, 02 Sep 2024 20:50:34 +0000

💭 forwords : "From grocery to supermarkets"

In a few words : you cannot hope for people to use and pay for your APIs and put your digital products & strategy to the next level if you don't showcase them in a proper place : the "developer portal".

Picture taken 17 February 1963 of Edouard Leclerc the French businessman in front of the first butcher's shop he opened in Paris. E. Leclerc wants to reform the distribution system in selling goods at wholesale prices, [...].
In the 80's Leclerc owns over 130 superstores, 350 supermarkets and about 50 specialized shops (sportswear, clothes, do-it-yourself, agricultural equipments stores). Moreover he his the biggest oil distributor in France after the national distributors.

💡 It's all about Customer empowerment

👉 Metaphorically, in the past people were going to the grocery and were asking to an agent to pick the products for themselves.
The disruption came when Edouard Leclerc empowered customers so they could choose, carry and even pay by themselves.

This is what we want to achieve in the digital era : putting self service as much as possible. Everywhere.

❔ About `APIs` "supermarkets"

Developer portals are at the core the digital transformation as they are the place where outer & inner software engineers/architects will come, discover available API products, ideate - and hopefully prototype - on how they will build innovative solutions on top of them thanks to appealing free plans.

🎯 What you'll learn

In this content, you'll :

🥳 Discover the public developer portal thanks to Apigee integrated portal we recently kicked off, in its early - alpha - version,
🔑 Learn how to authenticate
🔓 Learn how to create API keys
🚀 See how to call APIs by yourself

🍿 Demo time

🔖 Resources

Further about the "Apigee API hub" to

"consolidate and organize information about all of the APIs of interest to your organization.":

What is Apigee API hub?

🧱 Custom components 💏 API{GEE} : sms automation w. Power Platform

adriens — Mon, 29 Jul 2024 21:36:55 +0000

❔ About

When I was a kid, I loved to create new toys with my lego bricks kits.

Today...

"I still (maybe even more) love to build new things on top of existing bricks"

so I can:

💡 Ideate something new
🧑‍🎨 Create a playable/runnable artefact
🤗 Enjoy the new tool/gadget
🏬 Share (play with others)
🤯 Plug toys & tools together to create something even bigger or newer

🎯 What we'll see

👉 This post will show how this pattern makes sense in a corporate environment (on a custom tenant) and why it really matters in terms of productivity.

We'll see how, with our SMS API available from the www we can :

📲 Unse our API on APIGEE
🧱 Build the core building block : the Power Platform Custom Component
🏗️ Run a custom scheduled workflow

🍿 Demo

📊 Further about process mining

The Power Platform offers process mining opportunities and tools:

"The business value of the process mining capability lies in its ability to help organizations gain insights into their operational processes and identify areas for improvement."

Below some real life examples I could generate from my very simple workflow:

🥳 Mobitag.nc... 25 ans plus tard, des sms en SaaS via API{GEE}

adriens — Mon, 17 Jun 2024 21:44:54 +0000

❔ A propos

Il y a 25 ans de cela, en 1999, via Mobilis l'OPT-NC lançait la marque Mobitag:

"Mobitag.nc est un service gratuit d'envoi de SMS depuis un ordinateur, réservé aux particuliers et à destination des mobiles de Nouvelle-Calédonie."

25 ans plus tard, l'OPT-NC se dote d'une technologie de portail d'API, d'abord sur RapidAPI, puis d'APIGEE, avec l'ambition d'accélerer la transition digitiale en proposant ses services digitaux... directement en SaaS.

👉 Le but de cette démarche est de permettre des intégrations aisées, en self-service avec:

Des clients finaux (B2C),
Des partenaires (B2B) désireux de développer de nouveaus services sur ceux de l'OPT-NC
Des plateformes SaaS

... ou tout simplement pour lui-même afin d'accélérer ses projets en réduisant le Time to Market.

🎯 Objectif

Le but de ce ce post est d'illustrer concrétement un cas autour de ce service gratuit tant apprécié des calédoniens.

🪝 Ce que l'on va découvrir

Dans la démo qui suit, on va voir, comment:

🦥 Avec très peu de code,
☁️ Directement depuis le cloud (Kaggle)

on peut envoyer un sms de la part de mobitag.nc.

🍿 Démo

🤔 Re-Contextualisation

Lors de l'épisode précédent de cette série:

🛣️ API Marketplaces & innovation, explained and showcased

adriens for opt-nc ・ Nov 5 '23

#api #apigateway #beginners #showdev

avait été présentées les nombreurses opportunités et bénéfices liés à cette technologie, ie. de délivrer du service directement sur le web et manière interopérable... dans le but de faciliter les intégrations,... en SaaS :

🔖 Ressources

📢 About job offers, innovation & data strategy 🔭

adriens — Mon, 04 Mar 2024 22:25:21 +0000

💡 Shift-left thoughts

In IT, we usually think about Shift-left for our stack:

"Shift left is the practice of moving testing, quality, and performance evaluation early in the development process, often before any code is written."

And what if I told you that you need people to write code... and hence that you also have to shift left to embed recruitment process in your pipeline ?

👉 That's the main idea I recently started to explore...which lead me to create this content, in the hope to increase my holistic knowledge of the organization, at scale.

🎯 Context

I'm currently about to launch an exciting recruitment for my department.

In this context I decided to use this as an opportunity to learn more about recruitment process, with the ambition to have a positive impact on its performances and outcomes, at scale.

My goals are to:

🚀 Contribute to "become accelerator of economic and digital development in New Caledonia."
👨‍🚀 Help "reaching Reach High-level technologies and quality of service, innovation,"
🤩 Help implement "new customer-oriented organization,"
🪝 Help "seeking talents" by putting in evidence our data & automation approach

👉 This post is all about that ambition and the resulting journey.

🔭 "Building tomorrow" `aka. OPT 2025`

The OPT-NC has embarked on a profound transformation to meet the challenges of the strategic plan "Building Tomorrow | OPT 2025" and to fulfill its ambition to become an accelerator of economic and digital development in New Caledonia.

High-level technologies and quality of service, innovation, new collaborative ways of working and managing, performance management—OPT-NC is reinventing itself through its new strategic directions.

In this vein, OPT-NC is proposing a new customer-oriented organization, and it is within this framework that it is seeking talents.

The positions available are specified by department. The description of missions and skills is accessible on the OPT-NC website (www.office.opt.nc).

🤔 About

Working with the right people and the right skills is often seen by the end of the pipeline, I mean : you come to work in a team and everybody's already in place.

☝️ But all this starts with a crucial part : you need to get collaborators to build a team.

"Getting collaborators" is indeed a process, with a start date, an end date, documents, people involved, tools, KPIs (how many candidates, how many skills, ...) and of course all these can be described with data.

Today, I'll focus on these data, from many points of views:

The recruiter (the customer of this process) : the manager who's looking for a new collaborator w/ a specific skillset
The HR Team : the team that manages the whole process that has to respect date and rules
The candidate : "The one who's looking for an appealing job"
External Third parties that may benefit from this data for general purpose (researchers, government, public institutions,...)

🦥 Must watch key points

Asking groq why providing job offers as an API do matter
Asking groq why providing job offers as an Open Source dataset matters
Unbox Kaggle dataset
Build new customer experience with data with a first Kaggle Notebook
Disrupt Job offer browsing customer experience w/ unprecedented data visualizations

🍿 Demo

At last, the demo:

🎀 Gift

Finally I added some more data about the Province:

see how with this 5' video:

📑 Resources

🗣️ Speaking about Tech Hiring in 2024

How Will Tech Hiring Evolve in 2024?

dev.to staff for The DEV Team ・ Mar 4

#discuss #career

📍 OPT-NC agencies on Kaggle

adriens — Wed, 21 Feb 2024 20:00:48 +0000

❔ About

OPT-NC has many agencies in New-Caledonia, but getting csv files was not as easy as that, and if you wanted to use data to build datascience, you had to achieve manual tasks.

👉 The purpose of this post is to show how we recently upgraded the Developer experience... and the opportunities it does open.

🎯 What you'll learn

You'll learn:

🛍️ The various datasources we used to build a consistent & up-to-date dataset
🎁 Available dataformats (csv, duckdb)
🎀 How to use the dataset with a dedicated Notebook

🍿 Demo

📑 Related resources

⚙️ Notebook builder (where the data is prepared and aggregated)
🏤 Agences 📍 Dataset
👨‍🎓 Agences OPT-NC for dummies

🤯 Opened perspectives

Delivering data on Kagglle make it possible to play with them with free GPU and...

Amazing Open Source AI models like Mixtral (see Kaggle model card)...

and more recently google/gemma (see Kaggle model card):

// Detect dark theme var iframe = document.getElementById('tweet-1760289388204900633-672'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1760289388204900633&theme=dark" }

... or many other open source LLM models, see :

🆓 Local & Open Source AI: a kind ollama & LlamaIndex intro

adriens ・ Jan 17

#opensource #ai #tutorial #beginners

or simply use OpenAI from your notebook and the AI do the job for you so yo can focus on your storytelling:

🪄 Put magic in your Notebook w/ Jupyter-AI

adriens ・ Feb 14

#ai #python #tutorial #showdev

🛣️ API Marketplaces & innovation, explained and showcased

adriens — Sun, 05 Nov 2023 20:46:25 +0000

❔ Context

Digital Transformation, Data Strategy, monetization, AI & chatBOTs... are all very trending topics.

Yet,... to achieve these goals:

we need to get nicely delivered, secured and easy to use APIs.

To achieve these goals, we need to get well suited API Marketplaces:

🤔 Yet, defining what an API Marketplace is may not be so evident to all us... nor how to implement an efficient one.

👉 With this post and video, you'll discover a practical approach, from the bottom-up, experience driven.

🎙️ Discover

📑 Bookmarks

🏛️ Data Strategy

For more about data strategy, see:

🎯 Data strategy for (not so) dummies

adriens for opt-nc ・ Aug 17 '23

#api #interview #data #news

🎯 Data strategy for (not so) dummies

adriens — Thu, 17 Aug 2023 20:27:19 +0000

❔ About

Sometimes ago, I saw this tweet from Cigref in my thread:

// Detect dark theme var iframe = document.getElementById('tweet-1665988346881908736-921'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1665988346881908736&theme=dark" }

... and as they made it available as a pdf (recently available in English), it was quite comfortable to bring it with me on my e-reader.

After a few lines, the content was so meaningful that I decided:

To put things in perspective for myself to better understand how my current topics intricate are
Share some key points so anyone could benefit of this document... and go further by reading the full version

This post could hence be seen as a teaser for:

Data & Analytics Governance and Architecture: Developing and implementing a data strategy - Cigref

Cigref has published a report on the results of its working group on "Governance and data architecture", co-chaired by Alice Guéhennec, Chief Digital

cigref.fr

🎤 Intro : Live interview

The data strategy, a tool to achieve enterprise goals like:

Create new services
Achieve Operational excellence
Corporate social responsibility
Carbon footprint reduction
...

Élaborer et mettre en place la stratégie data - 03/06

VIDÉO - Ce samedi 3 juin, Alice Guéhennec, DSI du groupe Saur et Vice-présidente du Cigref, s'est penchée sur l'élaboration et la mise en place de la stratégie data en entreprise, dans l'émission Tech&Co Business présentée par Frédéric Simottel. Tech&Co Business est à voir ou écouter le samedi sur BFM...

bfmtv.com

So the big questions are:

How do we handle it
What for

🤯 Change, change, change...

First some context about Expected 2021 IT FTE Change in IT Activities

“While CIOs plan to hire more staff in several areas critical to meeting changed consumer and employee expectations, most will not be able to meet their planned talent strategy goals without also upskilling or refocusing their existing teams,” said Mr. Charlet.

So, in my case, I could see the keypoints I invest a lot:

🦾 Business workflow automation
🔗 Integration (eg. APIs)
☁️ Cloud platforms
🤯 "upskilling or refocus of existing teams"

📖 Develop and implement a data strategy

"The data strategy touches on the very image of the organization, its values, its aspirations and projects
for the future: it really is an issue of transforming the business."

"Data is an asset for the entire organization, not just for one department or business unit. This is why** companies and public administrations are transforming themselves** to make better use of this data, investing in building and implementing a data strategy that can serve their overall strategy."

☂️ The case of External risk of disruptive innovation

"The core business is being disrupted by the emergence of new players on the periphery with a business model based on using data from the original business. The question for companies is how to react."

"The specificity of this external or transversal threat is that it changes the perception of customers, which forces the company to adapt to better meet their expectations."

💡 A good way to sensitize about that may be to bring internal - and kind - disruptive innovation as part of the data culture... so we could make the enterprise adapt earlier thanks to "insiders".

📜 Develop a data strategy

Below some the high level roadmap : seeing it so clearly explained helps focus on the key points to help make things possible.

As collaborators, our mission is to help achieve the goal fixed by strategy with skills and tools.

For example, in my case a way to transform this strategy into action plan may be to:

🧑‍🤝‍🧑 Help develop employee's data culture : by blogging and showing what can be achieved with data and APIs in a way so everyone may understand it
🎯 Get Specific Business Objectives : starting from our Strategic Plan is a great way to do this
🔬 Identifiy relevant data to be used : as we have an up-to date cartography knwoledgebase, this is quite easy to achieve
🏗️ Prepare the architecture and technical bricks : this is where innovation comes in as it makes it possible to learn by doing and start deliver services at low risk but still by deliver services (and helps develop employee's data culture)

☝️ One of the objectives I want to achieve with my team is to :

"translate the data strategy into small steps that each bring value, in other words,quick wins."

So, a daily mantra could be:

"Data strategy is not just a technical issue, it is part of business transformation"

... hence it's our job to make it a daily concern.

📉 Time to market

🏛️ Data strategy pillars

Data Governance: Establishing a framework for managing and protecting data, including defining roles and responsibilities, data quality standards, and data privacy and security measures.
Data Architecture: Designing the structure and organization of data, including data models, data storage, and data integration methods.
Data Management: Implementing processes and procedures for data collection, storage, cleansing, and maintenance to ensure data accuracy, consistency, and accessibility.
Data Analytics: Utilizing data to gain insights and make informed decisions, including data analysis, data visualization, and predictive modeling.
Data Culture: Fostering a data-driven mindset and promoting data literacy across the organization, encouraging employees to use data in their decision-making processes.
Data Privacy and Security: Ensuring compliance with data protection regulations and implementing measures to safeguard sensitive data from unauthorized access or breaches.

These pillars work together to establish a comprehensive data strategy that enables organizations to effectively manage and leverage their data assets.

🧪 Innovation role

Increasing Market Share: Innovation can help companies and public administrations identify new business opportunities and develop new services or products based on data. By leveraging innovative approaches and technologies, organizations can create unique value propositions that attract customers and increase their market share.
Defending Against External Disruption: Innovation is essential for organizations to respond to external threats and disruptive innovations. By continuously exploring and adopting new technologies and data-driven approaches, companies can stay ahead of the competition and protect their market position.
Better Adjustment of Responses to Customers/Users: Innovation enables organizations to better understand their customers or users by analyzing data and identifying patterns or trends. This understanding can lead to the development of personalized and tailored responses, improving customer satisfaction and loyalty.
Improving Operational Excellence: Innovation can drive operational excellence by optimizing processes, reducing costs, and improving overall efficiency. By leveraging data and analytics, organizations can identify areas for improvement, make data-driven decisions, and implement innovative solutions to enhance their operations.

In summary, innovation is a critical component of a data strategy as it enables organizations to leverage data effectively, identify new opportunities, respond to external threats, enhance customer experiences, and improve operational efficiency. By embracing innovation, organizations can unlock the full potential of their data and drive sustainable growth and success.

➿ Disruption and Open innovation ?

Disruption and open innovation play a significant role in shaping the pillars of a data strategy.

According to my understanding, here's how they contribute to different aspects of a data strategy:

🧑‍🤝‍🧑 Data Governance: Disruption and open innovation challenge traditional data governance practices by introducing new sources of data and collaboration models. They require organizations to establish flexible governance frameworks that can adapt to changing data landscapes and accommodate external data sources.
🕸️ Data Architecture: Disruption and open innovation often involve the integration of new technologies and platforms. This requires organizations to design scalable and agile data architectures that can accommodate diverse data sources, handle large volumes of data, and support real-time data processing.
🏋️ Data Management: Disruption and open innovation generate vast amounts of data from various sources. Effective data management practices are essential to ensure data quality, data integration, and data accessibility. Organizations need to implement robust data management processes and technologies to handle the influx of data and derive meaningful insights from it.
📊 Data Analytics: Disruption and open innovation provide organizations with access to new data sets and analytical techniques. This enables them to uncover valuable insights, identify emerging trends, and make data-driven decisions. Organizations need to invest in advanced analytics capabilities and develop a culture of data-driven decision-making to leverage the potential of disruption and open innovation.
👐 Data Culture: Disruption and open innovation foster a culture of experimentation, collaboration, and continuous learning. They encourage organizations to embrace data-driven approaches and empower employees to explore new ideas and solutions. Building a data culture is crucial for organizations to effectively leverage disruption and open innovation in their data strategy.
🛡️ Data Privacy and Security: Disruption and open innovation introduce new challenges in ensuring data privacy and security. With the increased use of external data sources and collaboration with external partners, organizations must prioritize data privacy and security measures. This includes implementing robust data protection measures, complying with relevant regulations, and establishing secure data sharing practices.

To summarize, disruption and open innovation are integral to a data strategy as they drive organizations to adapt their data governance, architecture, management, analytics, culture, and privacy and security practices to leverage the opportunities presented by these trends.

⚡ Risks around open innovation and disrupting case

Open APIs, open innovation, and the** disruption of use cases by third parties** can pose several risks to organizations in terms of their data strategy.

Below some of the risks associated with these factors:

Data Security and Privacy Risks: When organizations open up their APIs and share data with third parties, there is a risk of unauthorized access, data breaches, and misuse of sensitive information. This can lead to reputational damage, legal consequences, and loss of customer trust.
Intellectual Property Risks: Open innovation and the sharing of data with third parties can expose organizations to intellectual property risks. There is a possibility that third parties may use the organization's data to develop similar or competing products/services, potentially infringing on the organization's intellectual property rights.
Loss of Control: Opening up APIs and allowing third parties to access and use data can result in a loss of control over how the data is used, manipulated, and shared. Organizations may find it challenging to enforce data governance policies and ensure compliance with regulations.
Competitive Disadvantage: Third parties leveraging open APIs and open innovation can disrupt traditional use cases and business models. This can lead to a loss of market share, revenue, and competitive advantage for organizations that are not able to adapt quickly to the changing landscape.
Quality and Accuracy of Data: When third parties are involved in using an organization's data, there is a risk of data quality and accuracy issues. Organizations may have limited control over how the data is collected, processed, and validated by third parties, which can impact the reliability and integrity of the data.
Dependency on Third Parties: Organizations relying heavily on open APIs and third-party innovation may become dependent on these external entities. If a third-party provider experiences disruptions, discontinues their services, or changes their terms and conditions, it can significantly impact the organization's operations and data strategy.

🛡️ Risk mitigation 🧑‍⚖️

To mitigate these risks, organizations should implement robust data governance practices*, including:

Data access controls,
Encryption,
Monitoring mechanisms.

They should also establish clear agreements and contracts with third parties to ensure:

Data security,
Intellectual property protection,
Compliance with regulations.

Regular audits and assessments of third-party partners can help ensure their reliability and adherence to data governance standards.

🚀 Last Words

Disruption and open innovation foster a culture of:

🧑‍🔬 Experimentation,
🧑‍🤝‍🧑 Collaboration,
📚 Continuous learning.

They both encourage organizations to embrace data-driven approaches and empower employees to explore new ideas and solutions.

Building a data culture is crucial for organizations to effectively leverage disruption and open innovation in their data strategy.

📑 Resources

Finally, below the way we have mapped our resources as data (used on a daily basis as part of our Digital Transformation Journey):

🗣️ Our speech about "IT holism" at #nodes22 💡

adriens for opt-nc ・ Dec 5 '22

#neo4j #datascience #datavisualization #github

🦆 Effortless Data Quality w/duckdb on GitHub ♾️

adriens — Tue, 25 Jul 2023 06:33:44 +0000

🪝 Teaser (for the impatients)

Do you have a repository that relies on csv files... and want to operate:

🛡️ Protect your data with quality intergrity checks before to corrupt your data
🔬 Check data quality as part of your project lifecycle
📊 Get operational KPIs reporting
♾️ Automate release process to explain your contributors what has been achieved
📦 Deliver data
🤯 Endless usages

🫵 Don't look further, this sort post will cover all these aspects with a practical and highly understandable workflow.

🍿 Demo

Enough talks, let's jump'in:

🦆💻🔁🔧♾️🦆 `opt-nc/setup-duckdb-action`

opt-nc / setup-duckdb-action

🦆 Blazing Fast and highly customizable Github Action to setup a DuckDb runtime

ℹ️ Setup Duckdb Action

This action installs duckdb with the version provided in input.

📜 Inputs

`version`

Not Required The version you want to install. If no version defined, the latest version will be installed.

🚀 Example usage

uses: opt-nc/setup-duckdb-action@v1.0.8
with:
  version: v1.0.0

uses: opt-nc/setup-duckdb-action@v1.0.8

📑 Related resources

View on GitHub

🔭 Further 🎀

Once CI (Continuous Integration) has been done... you can also think (without a lot of efforts) to Deliver that data to third party services, as part of your DEVOPS pipeline.

A this point I see two easy options:

Upload to minio S3 API w/ HTTPS
Use MotherDuck

... which make your data available for new usecases, at no additional effort:

🗣️🤖 Ask to your Neo4J knowledge base in NLP & get KPIs

adriens — Thu, 20 Jul 2023 03:32:29 +0000

🤔 Food for thought

With this content we'll start to uncover a fascinating subject, which is:

The cost/value balance of a question/answer... and "the illusion of gratuitousness"

As you will see, AI (and especially AGI) throws a lot of worries about task encroachment... but also helps challenging deep questions about what is the ratio between cost & intelligence, the impact it does already have on our collaborations... and most important :

"How we join our intelligence and creativity into a hybrid Humain/AI taskforce?"

🗞️ `Neo4j`, `LLMs` and data

In this context no-code integration has landed on NeoDash:

// Detect dark theme var iframe = document.getElementById('tweet-1678866394480525314-311'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1678866394480525314&theme=dark" }

This post will show up:

🧐 Why it matters
🎯 What can be achieved with this new feature (and its potential impact on our organizations & workflows)

🚼 How it works

Before going further, we need to understand that all that we are going to do is:

Ask a question in NLP (in english for now)
Call openai's LLM API to query meta graph APOC and build the cypher query
Get the cypher (the query)
Locally run the cypher against the data
Customize reports

🤔 Questions

On your daily activities, you may be challenged by the following kind of questions that look like (ie. follow the same pattern) :

How many GitHub users do we have ? (as it involves costs)
Who are the people managed by Mr X ?
How many GitHub repositories does Team X maintain ? (involves capacity to maintain a set of services)
How many virtual machine do we have ? (involves size of infrastructures and then costs,...)
How much do we spend on...
etc...

👉 Therefore we built an omniscient knowledge graph that is able to answer a very wide amount of questions about our organization.

Below some zoom-in into graph topology, so you (as well as the LLM we will use later) can understand how to deal with data:

Now we are able to transform a question into a dashboard widget:

// Detect dark theme var iframe = document.getElementById('tweet-1679730751934464000-102'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1679730751934464000&theme=dark" }

🍿 Demo

⚖️ Further on strategies

With that first experimentation started to appear new kind of concerns, in particular the following one:

"A big omniscient giant vs. a myriad of little agents equipped of custom tools."

This section is dedicated to very briefly summarize these questions so we can talk about them and optimize the design of our solutions, the way we could manage & answer incoming questions... and most of our own learning path so we can delegate automated tasks to AI and...

focus on the ones that can't or are not yet automated.

💰 Benefits

As a matter of fact, pretty shortly you're willing to automate questions answering tasks and re-invest that time.

In short:

🔗‍💥 People don't wait answers from your part : they go faster with more freedom, they don't make issues, etc...
🧑‍🚀 You can focus on higher value added activities : you go further and faster & gain in expertise

📊 NO-Code `Neodash`

No skill required
Plug & play strategy
Could be quite expensive during query prototyping phasis (but keep in mnd that OpenAI is regularly reducing the price of its APIs while improving them)
Put in evidence that "Time is money"
Remove the data guys from a potential bottleneck situations where people expect them to produce more knowledge at a faster pace
Very convenient to prototype
Great for high level questions and technically affordable by non-tech people (which sets them free)
No need to know the knowledge graph design
100% AI driven and meta-schema driven
Prone to make misunderstandings and cypher error generation (beware of large contexts, see below) and adequate LLM model setup

🦜🔗 `Langchain` & custom tools

Langchain and the implementation of Custom Tools also is a great (and very efficient) way to setup a dedicated Q&A (for example for chat purpose) agent.

Here are some few points to consider:

Skills required for implementation
Requires to know a preset of questions
Could fall back to the global approach when the chain is not able to find the answser... simply throw "I'm sorry, but with my current toolset, I was not able to find a suitable answer."

That's all for now, hopefully you'll have found this content useful and made you consider new use cases around AI adoption.

📘 Book

Last but not least, reading this book also highly helped considerate new way of thinking the work itself and prepare the ~~future~~ present:

Forem: opt-nc

🥳 We built the cli of our dreams to send sms ❣️

🤔 About the benefits of cli

cli-guidelines / cli-guidelines

A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.

Command Line Interface Guidelines

Contributing

License

🎯 Our Go(al)

⏳GitHub Copilot 1-Day Build Challenge : eol, a tiny Go client to manage eols

🍿 v1.0.0 brew unboxing

📜 The story behind the product development

🔭 What's next

Microcks for dummies

🤔 Microcks: For Whom and For What?

🤓 Spoilers

📜 Annotations and REST API Documentation Quality

🚀 Microcks: Boosting Developer Experience

🔍 Microcks and the Testing Pyramid

🎯 Personal and team benefits

🔁➡️📘 Kafka documentation automation : HUGO, gomplate, Github Actions & pages

💭 "what's wrong with writing (and maintaining) docs ?"

💸 The cost of manual legacy documentation

♾️ Embracing continuous change

🎯 The "What" & the "How"

💰 Benefits

🍿 Demo

💪 The magic of gomplate : csv to markdowns

🔑 APIGEE 101: onboarding & authentication

💭 forwords : "From grocery to supermarkets"

💡 It's all about Customer empowerment

❔ About APIs "supermarkets"

🎯 What you'll learn

🍿 Demo time

🔖 Resources

🧱 Custom components 💏 API{GEE} : sms automation w. Power Platform

❔ About

🎯 What we'll see

🍿 Demo

📊 Further about process mining

🥳 Mobitag.nc... 25 ans plus tard, des sms en SaaS via API{GEE}

❔ A propos

🎯 Objectif

🪝 Ce que l'on va découvrir

🍿 Démo

🤔 Re-Contextualisation

🛣️ API Marketplaces & innovation, explained and showcased

adriens for opt-nc ・ Nov 5 '23

🔖 Ressources

📢 About job offers, innovation & data strategy 🔭

💡 Shift-left thoughts

🎯 Context

🔭 "Building tomorrow" aka. OPT 2025

🤔 About

🦥 Must watch key points

🍿 Demo

🎀 Gift

📑 Resources

🗣️ Speaking about Tech Hiring in 2024

How Will Tech Hiring Evolve in 2024?

dev.to staff for The DEV Team ・ Mar 4

📍 OPT-NC agencies on Kaggle

❔ About

🎯 What you'll learn

🍿 Demo

📑 Related resources

🤯 Opened perspectives

🆓 Local & Open Source AI: a kind ollama & LlamaIndex intro

adriens ・ Jan 17

🪄 Put magic in your Notebook w/ Jupyter-AI

adriens ・ Feb 14

🛣️ API Marketplaces & innovation, explained and showcased

❔ Context

🎙️ Discover

📑 Bookmarks

🏛️ Data Strategy

🎯 Data strategy for (not so) dummies

adriens for opt-nc ・ Aug 17 '23

🎯 Data strategy for (not so) dummies

❔ About

🤔 About the benefits of `cli`

🎯 Our `Go`(al)

🍿 `v1.0.0` `brew` unboxing

💪 The magic of `gomplate` : `csv` to `markdown`s

❔ About `APIs` "supermarkets"

🔭 "Building tomorrow" `aka. OPT 2025`

🦆💻🔁🔧♾️🦆 `opt-nc/setup-duckdb-action`

`version`

🗞️ `Neo4j`, `LLMs` and data

📊 NO-Code `Neodash`

🦜🔗 `Langchain` & custom tools