GIDS is the gold standard conference and expo for the software practitioner ecosystem. 72,240 attendees have benefited from the platform since its founding in 2008. An essential destination for developers, architects & senior technologists, the event is five-day whirlwind of enlightening and inspiring talks by global experts, full-day workshops, exhibitions, networking and community. Several thousands have testified to the success they owe to GIDS - from individuals who turned entrepreneurs, to garage start-ups who metamorphosed into full-fledged global operations, to several thousands who have reported super positive career upgrades and shifts. Visit: www.developersummit.com
I don't get it. He talks about the plugin architecture, but it seems to me that everytime a new implementation is added, he rebuilds the client. Isn't supposed for plugin architecture, that the implementations can be attached and detached without a rebuild of the client?
Apparently "declarative" = looks like HTML Find a way to process special HTML attributes so that it behaves exactly like a full-blown jQuery app, structured the same and everything, but written to look like HTML - and you've achieved ✨declarative✨ code.
Except we like it because it prevents all the crazy JavaScript bundle stuff by just only allowing certain behavior on the client. These front-end developers are just idiots who just took the wrong side of a trade-off because it was a fad!
Great lessons. I totally agree that the unknowns could hurt us more after being n in those situation myself -:) In my case it was one dependency that had a different version in prod!
It is copy from this presentation of Justin Pirtle from AWS re-Invent talk ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-GNUSdekIaMw.htmlsi=fqmOFqNwLiCuvYk_ . Even slides stollen
@sergeykichuk2586 Justin Pirtle and I (presenter here) work for AWS Specialist team and the content here is re-used to educate customers. There are also a few new features/capabilities called out in this presentation but majority of the concepts remain the same. It is incorrect to mention the slides are stollen as the copyright is still with AWS. Please let me know if you still have any concerns.
“Oh we didn’t know there was a difference between an Excel file and a CSV file.” 😐 To be fair, it sounds like the team creating those user stories have an excellent grasp on what users are like. Perfect execution.
Great session by Prajwal indeed , I have attended this personally and he could have got 30 more mins to explain the Approach# 2 - Target state republish , If i might ask , is there a github repo link to refer to for this approach ?
Are the libraries and tools used to configure the infrastructure and tools are available to open source community? Are there any blogs on this so any one can try them out?
Around 52:40, the use of `sealed` without `permits` is really clean, but how/when does the compiler determine that `Sell` and `Buy` are the only two entities implementing `Trade`? Or if the compiler keeps track of everything that implements `Trade` whether `Trade` is sealed or not, does the `sealed` modifier just tell it to treat that set as complete, for the purposes of things like pattern matching?
Regarding performance it's self evident that the stream api uses lazy evaluation, but there's another important factor that he didn't mention. Each stream method call creates intermediate objects which are used to build definition of the stream. And when terminating operation is called implicit iteration takes place. Which means that new objects are created for each stream method call. So if your code is critical for performance old-fashioned imperative style is the only way.
Please stop switch in the video. All we want to see are the slides. Keep the 3/4 view with the speaker on one side. We are not here to be entertained by the view switching.
This was very great to think about, especially coming from John Lakos' finely-graduated, granular stuff. I'd love to see a hybridized learning talk about these!
