Even as someone familiar with Kotlin, it's hard to decipher what this library is doing without syntax highlighting here. The author is using infix functions and custom extension functions on primitive types. Non-Kotlin-natives will scratch heads.
Oh no, I know how it's done, I'm just surprised by it. There are more straight forward ways of expressing the same thing without using infix functions and those extensions (e.g. `val price = USD(100)` or `val price = Money(100, 'USD')`).
I wonder if addressing price fixing in rent prices will ease the regulations around short-term rentals (which have shown to also increase rents by about 3%).
In a rent-controlled area like in parts of Canada, it's not unusual for the tenant to improve the apartment they are renting with the consent of the landlord. This is ultimately to the tenants' benefit. Imagine investing $1200 into new flooring. Spread over 3/4 years of rent controlled rent, it comes out to $25 a month.
This has been the mission of multiple teams under my management.
Are you a designer or an engineer? The perspective below is for engineering:
- Designers are going to be your biggest challenge. There is a wide range of design skill level in leveraging the Figma versions of your design system and you need to have a strong partner in design doing the same thing you are on the dev side.
- Start with primitives. Get everyone using the same colors, fonts, sizes using shared functions. Then introduce theming. This should be universally adopted. Document.
- Rather than roll out a new design system, canonize the most commonly used components into a design system. This way, you get automatic adoption. Speaking of adoption, that's going to be your measure of success.
- Use tools to understand who is using your design system and who is not (there are tools but strong CODEOWNERs files are key here)
- Create documentation and training on the use of the design system. Don't stop teaching others on the use of the design system, especially if they are new to the company.
- Create a contribution model: how and when does a component become part of the design system?
- Take ownership over global components like the nav, headers, and the footer
- I've tried going higher order with form and page builders being part of the design system, but that's a lot harder than it seems
My learning is that a design system is important, but it doesn't get a lot of love in many organizations.
As someone who started in this industry when full stack meant you did CSS and Apache configuration, I'm often surprised by the need for AWS for most startups. A single machine can grow to two machines + a load balancer + a database instance. If you reach that point, then yes, explore AWS. Until then, is the cost really worth it?
I think one of the biggest reasons is just because everyone else is using it, so you need to use it too to either be able to hire people, or so you can get hired at the next gig.
Us on-prem regular server people are hard to find.
AWS/GCP throws tons and tons of free credits at startups, I get why it happens. Especially when they can now say things like “we will throw in AI too!” when every startup is some AI wrapper thing.
A senior role in NYC for 155K (plus bonus, which they do offer) is nothing when you factor in the cost of living.