1/2
@Crompton_India, Complaint raised on May 6 for a non-working fan. Ticket CBL26050618513 was closed without fixing the issue or my confirmation.
Priority complaint CBL26051203375 raised on May 12. Multiple escalations on May 16 & 19. Every time promised resolution in 72 hrs.
Help shape the future of AI in geospatial! Check out the Cesium AI Integrations repo where we’re sharing examples around
- MCP servers and tools
- Skills and agentic workflows
- AI‑powered developer experiences for Cesium
https://t.co/okBi6X3uLp
#CesiumJS#GenAI#Agents#MCP
Describing System Architecture: Summary
The series about the arc42 method to document system architectures is over.
As promised I leave you here the list of all the posts.
This one is a perfect candidate for a bookmark!
1. Introduction and Goals
https://t.co/yGDDyVNGd2
2. Constraints
https://t.co/UK8zapOi23
3. Context and scope
https://t.co/aepR3UX4b0
4. Solution strategy
https://t.co/xLx03v64tV
5. Building block view
https://t.co/Gx5OlWrAm0
6. Runtime view
https://t.co/7UKD98A5WH
7. Deployment view
https://t.co/3EYxz9oxb0
8. Concepts
https://t.co/Bja7ts3MLC
9. Architecture decisions
https://t.co/rDkwbInpWF
10. Quality
https://t.co/QIBMMiWvnD
11. Risks and technical debt
https://t.co/qnFRqFFPKW
12. Glossary
https://t.co/11lSXklfnP
In this series I used the official arc42 doc as a base. I added my experience with the template and the method hoping to have stimulated your curiosity.
In case you want to experiment with the template, here you can find the file versions in different formats, with or without explanations about the chapters.
https://t.co/WpJfxrAZdx
There are also other template in the main download page if you are interested: https://t.co/Pro1yRk9GK
Follow me, If you are interested in more Software system architecture, software engineering and team mechanics topic.
Explaining 9 types of API testing. The method to download the high-resolution PDF is available at the end.
🔹 Smoke Testing
This is done after API development is complete. Simply validate if the APIs are working and nothing breaks.
🔹 Functional Testing
This creates a test plan based on the functional requirements and compares the results with the expected results.
🔹 Integration Testing
This test combines several API calls to perform end-to-end tests. The intra-service communications and data transmissions are tested.
🔹 Regression Testing
This test ensures that bug fixes or new features shouldn’t break the existing behaviors of APIs.
🔹 Load Testing
This tests applications’ performance by simulating different loads. Then we can calculate the capacity of the application.
🔹 Stress Testing
We deliberately create high loads to the APIs and test if the APIs are able to function normally.
🔹 Security Testing
This tests the APIs against all possible external threats.
🔹 UI Testing
This tests the UI interactions with the APIs to make sure the data can be displayed properly.
🔹 Fuzz Testing
This injects invalid or unexpected input data into the API and tries to crash the API. In this way, it identifies the API vulnerabilities.
Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐜𝐡𝐞𝐚𝐭 𝐬𝐡𝐞𝐞𝐭. After signing up, find the download link on the success page: https://t.co/LZvUK3yNjV
Did you miss Google I/O?
@twerske recaps all the exciting Angular news from last month's event in our latest blog!
Check it out as you prepare for I/O Connect this summer: https://t.co/h250D5nhrq
Angular 16.1!
Launching today, we have two exciting RFCs on the future of Angular:
🛃 built-in Control Flow
⏳ new Deferred Loading Primitive
Get started with 16.1 now with `ng update`!
https://t.co/WOoGfgTrOs
🎁 did you know that you can lazy load #angular services?
🤔 now, what about a decorator that lazy loads services...
🤯 ... with custom strategies: mouseenter, inViewport...
⚡️demo: https://t.co/hhxYhXL0oM
#javascript#performance
In what order did you learn your programming languages?
Me:
1. Basic
2. C
3. Java
4. Assembly
5. C++
6. PHP
7. Python
8. Ruby
9. Objective C/Swift
10. Scala
11. Go