Видео

God, please fix the audio. The mouth noises are louder than his voice. Seems like a great talk, to bad I won't be able to watch it, I really want to.

This is exactly why you shouldn't let interns give talks, they give really bad advice, because they don't know any better. When new to parsers, the absolute worst thing you can do is to use regular expressions you copy-pasta'd off of stack overflow, and outsource your own job to a tool like YACC. Here's an amazing video on building a parser using recursive descent, and you'll learn how to create and describe your own grammar if you ever end up doing something like this in an actual production application. ruclips.net/video/SToUyjAsaFk/видео.html

can you share the link to the source code?

nice

Not a bad talk, I would have appreciated a talk more from a standpoint of someone who doesn't have a history of writing parsers though.

new go programmer here and googling this question hasn't helped at all. How do you keep the program from terminating and keep polling? I can read a queue and handle any messages but after that one run the program terminates. using v2 sdk

Thank you!

Very useful thanks buddy

hey! where's the github?

Great!

12 factors: 13:00

GitHub: github.com/slrtbtfs/goyacc-tutorial

Bruh

There's a statement I made in this talk that is no longer true. Amazon introduced FIFO topics for SNS in the Fall of 2020. You can now tie a FIFO SQS queue to an SNS topic, but you must tie a standard queue to a standard topic or a FIFO queue to a FIFO topic.

Great presentation, is there a repo?

Start here 10:30

that was a cool presentation

First time I ever heard the term Taco Bell Programming

Hi, is there any reference guide to learn golang specifically for data pipelines and data profiling?

I couldn’t find Golang Datadog Exporter for opentelemetry? Can you please provide a link below.

This was a very concise and helpful talk. Thanks

This is so cool! i loved this talk a lot

I am CTO of Mumbai based startup and I just want to say that this is f***ing disaster in making, they have completely ignored to make most out of natural ability of go to do AoT compilation and adding extra overhead of reflection at runtime for DI !!!! I hope this guy knows that go doesn't have any JIT like Java to do runtime optimization at first place, then why add extra overhead of reflection which is gone affect performance at runtime ? They are simply making clone of spring framework (Uber already did that with their Fx framework written in go) which is nothing but black magic hell. Many Java enthusiasts are moving onto quarkus+graalvm which completely eliminates use of reflection+JIT and rather uses clean and much secured AoT compilation which takes care of all dependencies at compile time itself, we already have play framework which uses Java's built in service loader class to achieve DI at compile time, google came up with guice which was based on reflection but later replaced it with dagger which is based on AoT compilation.

You also have to consider the performance hit using reflection at runtime for DI.

Nice talk!

really good

Very informative, thanks

Great talk! Thank you!

You can find the code here: github.com/borlinp/amazon-sns-sqs

Great presentation!