bazza451
Bring this into a professional workplace and watch yourself get laughed out of the building
They article shows the “alarming” first message of the Twitter threads then if you look at the further analysis (in later replies) it’s from a function which is rage shake which is a bug reporting tool which then the researchers say oh ok no problem…
The main issue is resourcing is pretty much ALWAYS awful as their goals (maximum resource billing) don’t align with yours…people go on about it, but the term body shop is pretty apt.
I was in a leadership position and its pretty standard operating procedure for you to ask for a senior Java developer and be told you’re getting a junior Python test engineer just because it’s whoever is sitting around twiddling their thumbs (…and that’s from an internal perspective, if you’re the client you’ll just get lied to about their skills)
This basically leads to teams being comprised mostly of people who have absolutely no clue what they are doing - Is no wonder that a lot of the projects either fail, go over budget or have severe performance/security issues…and as a bonus you’ll get charged per day for a person as much as a permanent FAANG employee costs.
Worst offender I saw in my time doing it was Sapient, they seem to just bring anyone off the street, pure incompetence.
IMO they’ve added every feature under the sun but not bothered on focusing on quality, some things just don’t work at all, or you get stuck with horrific performance issues. If we weren’t so far down the line with it I’d rip the whole thing out although it’s causing so much pain I might just bite the bullet and do it anyways
I did see MikroORM the other day and looked promising so cheers for the quick review, if anyone else has any recommendations would be good to hear!
I’m 12 years in professionally and still loving every second of it! Currently been slugging out Leetcode problems all hours of the day to try and get myself to an org with a proper engineering track. So maybe further down the line I still might be able to solve computer problems (in some way or form) during my day.
I really hope to someday to be able to come onto HN and do the same thing as you :)
You have to use Azure ADFS for things like office 365/teams, so would make sense for people to keep all their eggs in one basket.
The split stack resources thing is extremely difficult to manage due to serverless not supporting CF params. so you have to use CF cross stack references which are horrible or hack in support like we did.
I’ve seen issues where you can’t put the value of a variable as an arn in an event due to the poor abstraction across the top of it as they’ve tried to make it cross provider, completely pointless. Just breaks.
Stick with cf/terraform if you’re starting a big project.
They seem to be piling all their energy into creating mocks for new (paid) services when it might be worth consolidating as the original mocks have a lot of issues.
- Documentation is non-existent, expect to trawl through github issues to work out how something works as it’s quite opaque (api gateway invocation)
- CloudFormation implementation is completely broken (no intrinsic functions) so unless your stack is simple you’re pretty much required to use any AWS api based devops tools (e.g. Terraform)
- API’s are not fully complete, means terraform either breaks on redeploy when it tries to get a resources status or at best case triggers redeploy of certain resources each time (the most exotic thing we’re using is SNS)
- Test suite is...light, seen a few things go through their CI and break it
- There’s a bit of non-consistent behavior - you’ll set an env var and find it’s not implemented for a certain case and be left scratching your head
- Expect to have to make pull requests yourself to fix things
This isn’t a winge, I understand it’s partially open source and you can just fix the issues yourself when they come up like we are doing. But just a heads up for who may naively look at it and think it’s a silver bullet...you’ll have to go through all these steps.
On a new/fast evolving product I prefer to have a solid suite of integration/e2e tests and a lighter unit test suite near the edge of a server with no mocking of deps (e.g. if it uses a db, spin up a local instance). I would also test something that is non-trivial to understand or a critical dependency in the system e.g. a rules engine.
The reason being is - the code is in so much flux that the internal interfaces change constantly. In agile new requirements come along and you end up chucking a lot of the old code out of the window and wasting time.
As you move towards completion of the project and the internal interfaces shore up then increase the tests. So when it’s in maintenance mode someone else can easily make modifications and has documentation on maybe why something works in a certain way
Just to pick your brain (I’m an ML noob and it triggered an idea in my head). I was wondering if GPT-2 could be used to generate small paraphrases for an input sentence for search suggestions? e.g “I’m going to the mall today” -> “I will be going to mall today”.
Anyone know of anything similar but without that steep learning curve?
Having a partially sighted consultant come in and point out the deficiencies and how they use devices was extremely helpful. A lot of sight impaired people use Apple devices as their voiceover support is excellent, Android is getting better but you will find a lot of differences between their implementations in versions which is extremely frustrating. For desktop on windows JAWS seems to be the most used which again has its own way of parsing.
I don’t know if it’s changed but my advice would be plenty of manual testing, there’s really not much else than actually using the devices with voiceover enabled to test if things actually work properly. And it’s also a case of compromise and picking what devices to support as fixing something on one reader will inevitably break another.
Hope that helps :)
But I’ve seen so many people get themselves into trouble by using dynamodb as a silver bullet and not thinking heavily about the design of their data. If you try and use RDBMS patterns (PK and FK relationships) there’s a whole heap of pain due to atomicity only being on one record in one table. Some times you can’t escape these patterns as well as it is the best fit for data or you require strong consistency of your model (e.g. financial).
They released dynamodb transactions (for Java only) but from what I’ve seen that just increases the complexity of solutions, you end up with more reads/writes per call and a heap of other stuff surrounding your data. Serverless story currently for stuff like this really has drawbacks
I agree, it would be cool for someone to do the same thing for Typescript, I seem to remember a repo a while back on Github that said someone was experimenting with it - cant for the life of me remember where though!