288 karma · joined December 30, 2019
I don't work in IT/Software Engineering - I work in law. But when I find fault in other's work, it's a courtesy to let them know and give them an opportunity to address it. It's part of being a team player. I am not trying to be critical of you. It's just reading this reminded me of similar experiences where I was in a similar position to you. They were important experiences. People can feel bad when other people fix their mistakes when they aren't given the opportunity to be heard about it. It's so tempting to just say 'I will just do it myself' but you might find other people react poorly to this.
Of course, maybe things are different in the IT world where it may be challenging to identify who committed a buggy change to the code repository, or perhaps just a radically different culture of work. But at the end of the day we are all human.
It does appear you have developed an awareness of this, given what you noted in your reply to him (and props to you for that!). From there on, his behaviour was misguided and not appropriate.
In Oracle Cloud Infrastructure, after your credit is exhausted, you have to explicitly opt in to billing or else they stop all paid services for you.
Moreover, you can choose to keep billing disabled and use their free services without fear of unknown costs.
AWS have just decided to run with a policy of offering refunds when people make mistakes. Unfortunately, some people are ignorant of this, or too timid to ask for their money back.
In the meantime, a simple mitigation for consumers is to create an isolated guest Wi-Fi network on their router, and connecting IoT devices through that, so that they are kept well clear of the rest of the network. This is becoming commonplace on consumer grade equipment now.
They should pay reasonable (not low) taxes in any event, not subject to the caveat you identify.
I wouldn't really want a different, likely subpar system responsible for queuing and serving requests during that window.
I can only think they are directing it to a different cluster.
I'm actually a bit confused by 'the same UX across OSes'. What does this mean? The mobile UI is completely different to the desktop apps and web app.
Netflix contribute back without any obligation to. But they track the development branch closely, making upstreaming easier than with the PlayStation OS, which presumably is a bit more 'frozen in time', making it much harder to submit patches.
Imagine fixing an issue on a Model 204 mainframe, with a perpetually dwindling number of people you can rely on for help, knowing that if you don't fix it, people don't get their welfare cheque.
High stress, low reward. Unsung heroes in my books.
https://www.smh.com.au/technology/revealed-serious-flaws-in-...
I love IT and programming, but I knew if I made a life long career of it, I'd grow to hate it.
I really like doing IT related things in my own way. I'd always want to do things to best practices and not just get the job done as I was told.
I made the switch out of IT to another field. Configuring a Shibboleth IdP was probably the hardest thing I ever had to do in my IT career, it really pushed my capabilities. SLO wasn't the only hard thing, the whole thing was immensely challenging and every time I'd restart Jetty I'd be holding my breath hoping it would come up again.
More code || complexity == greater likelihood of bugs (including security bugs).
As ironic as a security bug in a security.txt serving module would be, it's probably best we avoid that possibility and let the ordinary, highly scrutinised file serving code handle it instead.
There is no viable alternative for a company wishing to publish an app: you have to target iOS or you perish. Many companies today need to have an iOS app. For example, a bank, or a big chain grocery outlet, probably needs an iOS app to exist in the market. This isn't a tiny niche area which can be avoided.
The only way you can publish an app is with Apple's approval. Therefore, Apple are exercising a significant degree of market power.
In the US, the idea that because a company is private it can trade however it pleases has been rejected since 1890 when the Sherman Act was introduced. It's the same in most capitalist economies. The conduct of companies is subject to reasonable regulation to ensure healthy competition.
I've established earlier that Apple has significant market power in the mobile app space. Because of that, it's fair that we ask Apple to be reasonable when deciding what apps to approve, and the conditions on which they approve them, because they are exercising a significant degree of market power.
This is a space calling for regulation. Apple and Google should not be free to reject or impose conditions on apps as they wish. We have a right, as the people who make rules about how companies may trade, to ask for them to be regulated when they are exercising a significant degree of market power.
Sure, you might have word state -> boolean in a simple scenario. But what if the party alleges the contract, or a term, is void or unenforceable because of the existence of a vitiating factor? What if there are two competing interpretations of a term which depend upon considerations such as the purpose of the agreement?
It would be a very difficult task asking someone to agree to a contract which requires no value judgements. Even more so in the Nordic countries where such agreements are governed through a lens of 'good faith'.
We then wind up making value judgements, weighing the benefits of holding parties to a bargain capable of being determined objectively, on the one hand, and the elusive and complex notion of 'fairness' on the other.
We are then well and truly outside the boundaries of the capabilities of contemporary thinking machines.
Taxation is an area of back end law where lawyers should be worried about automation.
So, unless you resort to an unreasonable suffix of digits, or a potentially unprofessional moniker, you've got no choices.
Then again, email may not be a viable personal communication method in the future. Looks like the future is chat apps.