Why do we build CRM Systems at Lime? What is our strategy with that? I've written a post on this over at our new product blog at Lime:
More content will follow on this blog to share our ideas, thoughts and processes on how and wh…https://t.co/PX3eQwf2IK https://t.co/GtEvj4Y1qG
Trainee at Lime is a great way to start your career! This was how I got started back in the day, and haven’t regretted it once! https://t.co/uoW5iYFnFg
At Lime we have the modest ambition of being a world leading SaaS provider with a best in class modern cloud offering! Would you like to join us in build a kick ass cloud platform? The challenge; create a scalable PaaS like infrastructure that is easy to…https://t.co/DhBRb1QIgm
THINK LIKE AN EPIDEMIOLOGIST:
The CDC’s recent announcement that the Delta variant has an average reproductive number of 6-9 has a lot of people concerned & many are asking me about whether this means we need COVID boosters.
Let’s talk through the math of how we might decide!
If the goal is to dig a hole, keep digging. If the goal is founded on ideas, the inspiration has to come from somewhere, and it probably won’t spring from overwork and exhaustion. It might during a walk in the woods, while reading a poem, or after a dinner with friends.
As you scale, you add people with low tolerance for risk, but high tolerance for process.
Left unchecked, the "process people" will overwhelm the "risk people".
Adding process is natural, taking risk is not.
You need to push and support the taking of calculated risks.
This is a story about how I lost $10,000,000 by doing something stupid.
Ten. Million. Dollars.
Literally up in smoke. Money bonfire.
That’s enough to retire with $250,000+ in annual income.
Here’s what happened…
In Finnish we don’t have gendered pronouns.
These translations from our gender-neutral language into English reveal a lot of bias in the world and in tech RT @annabrchisky: Maailma ei ole vielä valmis. Eikä ole teknologiakaan.
#InternationalWomensDay
escape room concept:
- you are a software engineeer
- there is a production issue related to a legacy codebase
- no one knows how it works
- various credentials are scattered around the office on post-it notes
- there's some printouts of git diffs
- you have an hour to fix this
Consulting service: Your 25-person company is drowning in complexity with microservice architectures, serverless, and SSR. I say "your app will fit on two Heroku Standard 1x dynos and one Standard 0 database. $150/mo total. Eat the 100 ms of extra latency." You pay me $10,000.