As a Brazilian, i'll let my nationalism escape a little bit to say that it is awesome to see such an incredible work done by a fellow brasileiro. This gives me the same feeling of awesomeness that I get when I see José Valim's work on Elixir.
I only wish I could be as diligent and focused to do a thing like this, because I think it would be so much fun. I bought the Crafting Interpreters book a while ago, but still haven't got time to actually go through with it.
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build: - web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
Why would you want to abstract away the underlying database?
Wouldn't it better to already use the target DB to cattch potential issues earlier? Also to avoid creating another layer of indirection, potentially complecting the codebase and reducing performance?
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build: - web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build:
- web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
"Personal information fuels much of AI innovation so people need to trust that organisations are using their information responsibly," it said.
No, we do not. First and foremost, in our current society, trust should be earned, and not understood as already given on first sight. Second, even if said trust is earned, it can be lost.
Most of these companies have shown, time and time again, that they cannot be trusted with personal information. To give credit, some companies do put up a disclaimer that you should not provide sensitive information. But that is only acknowledging that they are going to use in a public way, i.e. everything you feed into AI models is going to be public.
And finally, advances in AI do not require personal information. Not ever. Just because we CAN provide personal information, it does not mean we SHOULD provide it.
That does not address the fact that yes, inheritance is one type of subtyping polymorphism, and that many languages have them via OO paradigm.
Yes, there are other forms of subtyping, but saying that many languages don't have subtyping just because they don't have these other forms of subtyping is either cluelessness or satire.
I use Proton on Android and I can write a new email using one of my aliases. Maybe it was fixed recently.
Regarding n° 2, I think it will never be fixed, given the nature of the service itself, in which all emails are stored encrypted, and the encryption keys are in the server.
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build:
- web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX)
- services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069)
- serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda)
- microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus)
- data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom)
- small CLI apps to help automate common tasks (Rust)
- integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests
- proper documentation for common services using OpenAPI specification (Swagger)
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build:
- web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX)
- services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069)
- serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda)
- microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus)
- data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom)
- small CLI apps to help automate common tasks (Rust)
- integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests
- proper documentation for common services using OpenAPI specification (Swagger)
SEEKING WORK | USA and LATAM | Remote | Software Engineer
I am a software engineer with 6+ years of experience. If you have a need for microservices, or monoliths, as backend features, I can build them for you. Also trying my best at creating full-on web applications using HTMX and Spring(Java)/Axum(Rust).
Expertise: Currently building microservices as an abstraction interface to manage, monitor, configure and provision network devices
Current project: Taking a Node-based project for device monitoring built for lab-only use to have features such as authn and authz, proper device registration and discovery, SNMP V3 auth features, README documentation and on-prem installation via docker-compose
Again, kudos to Uncle Bob for reminding me about the importance of good software architecture in his classic Clean Architecture! That book is my primary inspiration for this series. Without clean architecture, we’ll all be building firmware (my paraphrased summary).
What does clean architecture have to do with building firmware or not? Plenty of programmers make a living building firmware. Just because they don't need/can't/want to apply clean architecture in their code, doesn't mean they are inferior to those who do.
Furthermore, after a snippet which I suppose it is in Kotlin, there is this:
While mathematically a square is a rectangle, in terms of behavior substitutability, it isn’t. The Square class violates LSP because it changes the behavior that clients of Rectangle expect.
Instead of inheritance, we can use composition and interfaces
The Liskov principle is about one of the three types of polymorphism (so far): subtyping polymorphism. Which is about inheritance. Composition is _not_ subtyping. And interfaces (be it Java's or Kotlin's) are another type of polymorphism: ad-hoc. Even Wikipedia[1] has the correct definition:
Ad hoc polymorphism: defines a common interface for an arbitrary set of individually specified types.
Therefore, the examples of interfaces aren't compliant with LSP as well.
I understand the good intentions behind the article, but it left much to be desired. A proper research to at least fix the glaring errors should have been made beforehand.
I only wish I could be as diligent and focused to do a thing like this, because I think it would be so much fun. I bought the Crafting Interpreters book a while ago, but still haven't got time to actually go through with it.
Well, maybe one day...