We split our monolith into microservices. We did so to make it easier to reason about but morever we did it so that we can apply different data persistence strategies for each entity. A monolith would have us bound to a single persistence type (e.g., SQL) but microservices frees us which makes reasoning the application easier. The monolith didn't work for us so we moved to microservices but we didn't start with a microservice, we started with the monolith and grew and evolved it as we needed too.
I'm a tech lead in a large, distributed application. I disagree somewhat, there's a bit of a unicorn reasoning. If teams don't work well, a tech lead's job is to revive culture and confidence which is going to be harder.
My day to day as tech lead is mostly looking at our board and seeing if people's work loads are just fine. Do I provide mentoring? Sure, when I need too. Do I provide architectural guidance? Sure, when we have big stories that require my review. Majority of my time is spent taking care of my team. Is my team doing well? Absolutely. We communicate well and aren't shy to help each other out. But being a tech lead my emphasis is quality and making sure that my team is on track with that.
Yikes! Maybe it's time I switch to using fresh tomatoes when making red sauce. It's not that hard to skin tomatoes anyways so maybe it makes sense to go in that direction, especially when they're adding that much sugar.
I happen to have 3 brands of tomato sauce in the cupboard. Each 8 ounce can appears to have less sugar in it than a serving of Oreos (14 grams for the Oreos. 5, 7.5 and 10 grams for the sauces). Only the 10 gram sauce has any added sugar.
The cans each say 2.5 servings (to be clear, above I've done the math for the entire can), and I think for many foods, it will be the case that less than 1/2 the can is a serving. So there is something iffy about the comparison in the article (and 20 or 30 calories of sugar in a meal is not a huge concern for most people).
Thank goodness that coffee is something I actually like. I stick to no more than 4 cups a day, 5 cups if I'm feeling lucky. And by a cup, I mean an 8 oz cup (a 20oz to me is 2.5 cups of coffee).
When I was in college I was admitted to the ER for arrythmia. The condition was exacerbated by excess caffeine. I went from a pot of coffee a day to 3 cups a day for years, this included exercise and meditation. I refuse to touch energy drinks; while it gives me a shot of energy, prolonged use has consequences like my visit to the ER due to excessive coffee intake. I'd rather focus on getting the correct amount of sleep and taking regular breaks to recoup my energy rather than relying on coffee to feel awake.
The author addresses social structures and we seem to live in an age of increasing isolatedness amongst people. I thought it would have been a hard read (I suffer from depression) but it's also liberating to see it in a different light.
JavaScript, IMO, forces the developer to do a lot more defensive coding. All API's have contracts. An add() method that computers two numbers shouldn't expect a JSON object. For that matter, your method's contract shouldn't return an "any" for the same reason that you shouldn't expect "any" as its input.
What TypeScript does is remove the ambiguity of API development for front-end work. Considering I've worked in some big enterprise wide JS projects, TypeScript answers the question "Wtf is this returning?" which lessens my debugging time because I know exactly the type of the object being returned.
Your arguments are actually kind of moot. When you write in Java, you're really just boiling it down to an intermediary language. Should you write it in IL? Why not C/C++? Why not assembly? Shoot, just handout punch cards again and let's get to working. Abstraction isn't the enemy here, it's the value of the abstraction that gives value to it. TypeScript isn't so much an abstraction as a superset but it's static typing alone is worth 1000x over.
If you're expecting one type and get another, you have to handle it, right? Documentation is important in JavaScript by virtue that code contracts are never enforced due to implicit typing.
JavaScript makes this process optional, and it only needs to go wrong once to become a problem.
Personally I saw over a million dollars lost and an entire team laid off after a piece of code started working with a value that was expected to be a number but wasn't.
> If you're expecting one type and get another, you have to handle it, right?
Depends. You could debate the same philosophy wrt C and null pointers. Should you check all your arguments to see if they're null, if the documentation/specification says they should never be null, or accept undefined behaviour and segfault?
In practice, most code assumes everything is checked, sanitized and used correctly at the outer most API boundary.
That's a straw man. While no one is forcing me to rent it out, it's common courtesy to let your landlord know of any activities you wish to pursue. After all, it's not your property you're staying in, there's a reason why you're renting it. After all, people rent out their homes on AirBnB for leisure. What porn film makers are doing is capitalizing on AirBnB rentals by circumventing not only regulations (not a fan of but sometimes it's necessary) but they're making a profit from your property. Not to mention the fact that they left this person's house a total mess which is already a dick move on the film makers part.
> What porn film makers are doing is capitalizing on AirBnB rentals by circumventing not only regulations (not a fan of but sometimes it's necessary) but they're making a profit from your property.
What many people renting property out on AirBnB are doing is not only circumventing regulation (regarding, e.g., short-term occupancy rentals) and rental contract provisions (with their own landlords), but also making a profit from someone else's property.
AirBnB has largely grown, and knowingly leverages (with deliberate structure to try to keep the legal risks that result on other parties in the transaction), exactly this kind of evasion of regulatory and contract restriction to make profit off of other people's property.
So, while its been well-known to occur on the side of the transaction renting-out property via AirBnB, it shouldn't be too surprising that it happens on the other side of the transaction as well.
That's not a straw man. It is a rather cavalier and entitled attitude, however, and I agree with you that it should be common courtesy.
I have noticed a common attitude in the technology sector and amongst gamers, that if you can get away with it, then you are effectively allowed to do it, and if you're "smart," you'll heartlessly exploit all such opportunities that come your way. (Note that I am in the technology sector and would be called a "gamer" by many.)
Underlying such an attitude is the unspoken belief that being "smart" makes one superior to the average person and therefore somehow entitles one to such exploitation. My opinion is that people who express such attitudes are scum who will stab you in the back if the reward is great enough.
>> I have noticed a common attitude in the technology sector and amongst gamers, that if you can get away with it, then you are effectively allowed to do it, and if you're "smart," you'll heartlessly exploit all such opportunities that come your way. (Note that I am in the technology sector and would be called a "gamer" by many.)
I think that attitude is found across the population in general, not just tech, not just gamers.
I've seen way too many people take the "better to ask for forgiveness than permission" tack with a lot of things in life.
>> After all, it's not your property you're staying in.
Actually, it is your land. You have a property right. It isn't eternal or unlimited, but while you are renting the location it is in fact "yours". Landlords are not allowed to run around on rental properties like they own them. They don't. Their rights are curtailed for the duration of the lease. This big deal when landlords start performing "random inspections" for things like grow ops.
You have an occupancy right -- a right to quiet enjoyment of your residence, with constraints on landlord entrance/interference under non-emergency conditions... not the same thing as property rights.
> What porn film makers are doing is capitalizing on AirBnB rentals by circumventing not only regulations (not a fan of but sometimes it's necessary) but they're making a profit from your property
