The type of questions you are mentioning are basically saying different people would need different configuration options and come up every time you design any complex technical feature that is going to be used by millions of people. These are mostly product and UX questions, and NOT engineering ones. The only engineering problem I can think of is the latency in getting real time billing information.
The way you usually solve this is by having sane defaults, and giving users different mechanisms for configuration based on how complex their configuration needs are. This can take a tiered approach.
As an example, simpler and straight forward things (such as disable egress traffic from S3 if the bill exceeds X) can be in the UI itself. Then, for customers who need more control, an option to configure via json or yaml similar to cloud formation. For anyone who needs even more giving an option to call a customer defined lambda function would give them the ability to at any metrics and take appropriate action.
1. How do you actually have a billing system reach out to every other system? It has to resolve the resource, network with it, have IAM permissions, a network route, etc.
2. How do you handle consistency?
3. How do you make it responsive?
4. How do you add this to every billable entity?
I mean, it's just a shitload of work, and all of that just to get to a terrible idea.
> The way you usually solve this is by having sane defaults, and giving users different mechanisms for configuration based on how complex their configuration needs are. This can take a tiered approach.
The sane default is you pay for what you use, and you can listen to billing events and build all of the logic you're talking about if you want to.
I don't use tiktok myself, but from what I've seen their core user group is (mostly young) people doing irresponsible and silly things to get views on the platform.
I don't think showing how irresponsible you are is the best way to convince an employer to hire you. Maybe this will work for certain positions like "social media manager" that some companies have, but as a general job board it will conflict with the main use of tiktok.
>I don't use tiktok myself, but from what I've seen their core user group is (mostly young) people doing irresponsible and silly things to get views on the platform.
TikTok isn't all that different from YouTube. Like YouTube, you can find a lot of stupid or outright irresponsible content. But also like YouTube, there is a ton of amazing, informative or outright entertaining content on the platform.
In short, TikTok is whatever you want it to be. Just like YouTube.
Whenever you aren't the target audience, you can't assume that what you've seen is a random sample. Presumably, you were the target audience for whoever was showing you those videos of people doing irresponsible things.
I use it sometimes and most of my feed is just funny commentary by people in similar life situations or who have similar viewpoints. I'm sure there are people doing irresponsible things, but I just wanted to chime in and say that it's not strictly for hooligans.
I don't think so. There are a ton of companies that are desperate to fill positions right now, and Gen Z teenagers probably don't qualify for unemployment benefits, so they'd be willing to take a shitty job for some cash.
Plus, maybe the idea that someone needs to present themselves a certain way to the public to be hirable is a millennial thing. This could be a glimpse into the future of a world filled with Gen Z adults, who have internet culture and mannerisms in their DNA.
Thanks for the link, I didn't know that was a thing.
Having said that, this sounds like "Hey guess what? We are gonna snoop on you, and profile the hell out of you and leak all of your sensitive data all over the place (filenames can be) all because you are a paying customer"
That's about the worst way to disrespect a paying customer. Is there a way to easily identify companies that does this, I can avoid them?
No, they don't need to snoop on you. Just fire a single pixel saying this is a user that they would like to find more of. FB does the rest based on data in FB, not on Backblaze. The mistake was them just adding it to the online dashboard because that's the easy way to automatically include paying users.
> "easily identify companies that does this"
No. And this can happen for a lot of reasons as explained so even harder to check for.
It's scary to think that a company that seem to have a decent policy on privacy / data collection practices at one moment is just one step away from some marketing manager or MBA changing that. It's really hard to gain customer trust once you loose it, and in BackBlaze's case it seem to be for marginal if any monetary benefit.
I think part of the reason is that most of these companies don't value customer trust.
> Most enrollees will finish in six months or less
I am not convinced that you can learn the skills and knowledge necessary to be an effective software engineer in six months.
However I think it will be an awesome avenue to improve your skills if you already have some background.
I am not convinced that you can learn the skills and knowledge necessary to be an effective software engineer in six months.
Of course not, that takes years of practical hands on experience to learn. Many people can work as programmers for a decade without mastering those skills.
6 months could however be enough to learn enough to a start being productive as a junior member of a larger development team.
I fully expect new engineers to come in very green. There is so much breadth to software engineering that I understand that they will learn half of what they need to know on the job.
Never mind that, six years from now, much will have all changed anyway. (I've been at this a few decades now and, with Swift, I've now learned language #6 for my job.)
Only the Android dev associate program is related to software engineering. I don't think anybody going into this program has expectations of acing a technical interview at Google with their Coursera certificate of completion.
But it might be attractive to people that are interested in exploring the area without the overhead of a full CS curriculum.
Anecdote: I'm in Australia, salaried. And I'm getting fucked. 200+ hours over time over the course of last year. 0% pay rise. But we got $1000 stocks pre-tax which equated to a little over 0.6% pay rise. Yay /s
I'm voting with my feet though. Should be getting a job offer (hopefully!) in the next few days.
Yeah I've done a lot of unpaid overtime as well, don't even bother to count it mostly, what's the point.
But being salaried is still superior for the large majority of people. This becomes more evident the older you get, when benefits like maternity/paternity leave, long service leave, paid annual leave etc become more useful. There is also the matter of getting a loan - huge disparity based on employment status there.
Another factor is if you fall sick or can't work as usual for some reason.
Australia has laws which make it hard to get fired (unfair dismissal legislation), providing even more security to the salaried.
One of the examples on invalidating cache on write has the following code, which is buggy. If the DB call fails, then cache cache would have data that was never actually committed. Cache coherency is hard.
Are there any guidelines on how to prevent such incidents in the future where management overrules engineers /subject matter experts because of deadlines / profit etc ?
Can we learn from other professions such as doctors on how to handle these better? I believe it's very rare for a hospital administrator to over rule a doctors decision when it comes to patients health.
I think this is down to the way Google implemented labels. I looked into this when I moved all my email off Google's servers and noticed they just list them as folders on IMAP, so a client would have to implement a special google-specific way of dealing with them. There are other ways to implement labels in IMAP (I've forgotten the exact details but I did it successfully while interacting with the IMAP server using `openssl s_client`).
I may be wrong but my understanding is that this is just a limitation of Gmail's IMAP implementation. Every IMAP client I've tried so far displays tags as separate folders.
The way you usually solve this is by having sane defaults, and giving users different mechanisms for configuration based on how complex their configuration needs are. This can take a tiered approach.
As an example, simpler and straight forward things (such as disable egress traffic from S3 if the bill exceeds X) can be in the UI itself. Then, for customers who need more control, an option to configure via json or yaml similar to cloud formation. For anyone who needs even more giving an option to call a customer defined lambda function would give them the ability to at any metrics and take appropriate action.