harrylucas

Wanted to check if this actually provides a unified api? E.g. each category of integration will return the exact same data shape? From the looks of the video I'm still making a call to slack's API `users.list` and have to write the code to paginate slacks api (e.g. the next cursor).

It's much simpler then that. The answer is 100% on the home page though

I always get confused with AGPL and seems to have differing opinions online, so wanted to ask here. If I use Lago in my app, and don't change it all, do I need to opensource my entire application?

Yeah instantly my thought. Also since it’s only in “request access” mode it’s not something that can be ticked off eg not really apart of the list. Also the landing page for it feels like it’s written in the same style.

Definitely not against advertising the product but make it more explicit

Metomic | London UK | Full-Time, Remote-OK (UK Hours) | https://metomic.io | £75-£110k

Metomic helps companies discover and control their sensitive data footprint across their cloud applications. We're an engineering first, data driven company looking to change the way companies manage and protect their sensitive data.

We're looking for a range of front and backend engineers to help us scale out the platform. We're looking for individuals who are pragmatic, value good communication, respect and innovation.

Frontend: https://app.otta.com/jobs/RElTazIx Backend: https://app.otta.com/jobs/cFBzNWFy

You can also reachout to michelle <at> our website domain for any questions

[Backend+Frontend Roles][London, UK][£75k - £105k]

Hey !

We are hiring both Backend/Fullstack and front end engineers at metomic (metomic.io).

At Metomic we're out to change the world data privacy and compliance by giving companies the power of data without the risk.

We are in early stages but have some great traction and a very exciting couple of months ahead of us here.

Tech we use:

* Frontend: React / Typescript * Backend: Typescript Node (most likely will change), Docker, Neo4j, Postgres, RabbitMQ, ECS + Terraform.

If it also matters - we are much more towards the FP side of the scale when it comes it FP vs OOP.

Checkout our jobs here if you are interested:

*Backend/Fullstack*: https://app.otta.com/jobs/cHFyZ09p *Frontend*: https://app.otta.com/jobs/WE5VNkdi

This is really the big problem with DDD microservices. Whilst I'm a huge fan of the two, my go to is to always start out with a monolith and enforce boundraries within the application that could potentially become microservices at somepoint in the future. Even go as far as to use an in-memory event-driven system in the monolith. Then and only then when the need arises do we pull it out into it's own microservice.

This has various benefits but the biggest one being you get to play with the design of the 'microservices' before actually committing to making them microservices allowing you to make better informed decisions. The harder part is that it does require stronger discipline and if not done correctly, a harder transition to microservices (e.g. pulling out the components)

It's going to sound super simple, but initially you really just want to try and have as many conversations as possible with your users.

Firstly though, you need to have an idea (doesn't have to be perfect or 100% right) of who your target segment is. These are the people whose problem you are solving - and therefore initially are going to hold more weight with their feedback.

Once you have identified these users - use a combination of current users and potential users to get feedback from.

Some ideas:

* Email (like you've been trying) - Try and be candid and frank. Put yourself in their shoes - why should they respond? If it's a generic email their probably going to be of the mindset of either 'Someone else will do it' or 'I can't be bothered'. If you make it unique and more personal you're going to have a higher reply rate - but obviously a higher time commitment. I'd also suggest pushing for feedback calls rather then just messages. A call with a target user is worth its weight in gold.

As other users have suggested - offering a giftcard in exchange for a feedback call is also another valuable route if you can afford it.

* LinkedIn: Depending on your business (B2B or B2C) you can follow up with these users and potential new users on LinkedIn. Again this comes back to being somewhat more personal. Explain who you are etc.

* In app messaging: If they are constantly using your app - ask them while they are there in the midst of it. Don't be spammy though (this is approach we take mainly with delighted).

Lastly, once you have gotten your feedback - don't just take it at facevalue. Try and really understand what problem they are trying to solve as the solution might be completely different then the one they were thinking of.

E.g. if you were building an analytics app and someone gave feedback that they want to be able to export the data. If you take that at facevalue you will most likely build a tool that exports their data. However if you dig deeper and try and understand why they want to export the data, you might be able to solve a bigger issue for them AND for more users. E.g. if they come back and say they want to do XYZ with the data beacuse that means they can then gain ABC insight from the data - you might be able to add the ABC insight into the dashboard instead, skipping the need for export and customer work.

If you want more of a hand feel free to reach out! I'd be happy to help you out!

[1]: This is actually a problem we are trying to solve with Delighted so I feel your pain - https://getdelighted.co

What one do you take? I currently take allergy tablets every day and would love something to just help it

100% agree that typescript has it quirks and definitely agree about import maps most likely going to be the way you use deno.

However there are tradeoffs with everything you use.

It really comes down to which tradeoffs are the right ones for you, which may not be the same for someone else.

Author of the artcile (me) or Author of Deno?

Oops that was definitely a mistake on my side! Good pickup though, I've updated it to include a link to a full list :)

I think its only the natural progression. there are definitely some flaws with it, it isn't perfect. However, the tradeoffs really do seem to swing in favor of deno.

Interesting, I'm assuming that this wouldn't be possible on iOS devices? E.g. would installing a calculator app on iOS allow someone to route traffic through my phone? (obviously without me granting vpn access to said app).