wolfeidau

I have been using Cody in VSCode for a couple of months, and I am getting a ton of value out of it.

The key things I love are:

1. It really knows how to summarise a code blocks, this can be helpful to review code in other projects, or provide a refresher to your own, it misses very little!

2. It is very smart when it comes to filling in gaps in log statements, error messages or code comments.

3. Copy and paste is mostly dead, given a small hint it fills in the gaps for common patterns and is way less error-prone, and follows my prevailing style once the project is up and running.

4. Writing tests, this really surprised me but a lot of trivial, and some not so trivial ones are generated by Cody.

Things which annoy me when using Cody:

1. Suggests when writing in markdown are not very helpful, most are wordy, and always positive, it is almost impossible to get a negative or even snarky sentence out of it...

2. Inline suggestions are a bit annoying at times, it really doesn't "know your code", or that of your libraries, for common std library calls it is great, but anything more complex or obscure it is mostly wrong.

3. It is somewhat bolted onto VSCode using some creative solutions, with VSCode only allowing more fit for purpose APIs to be used by GitHub Copilot, which is sad.

Overall it is doing a lot of the heavy lifting turning my code into English, and either entirely building tests, or fleshing out enough for me to just tweak the code a little so big from me.

What a wonderful story, certainly brought a tear to the eye and a smile to my face.

Thanks for posting o/

Great work on this, it really is a weak spot for a lot of aws developers, myself included.

I would love to see more work on the AWS side to address this with integration to keychain, 1password and the like.

Great suggestion, will add that as well

Fantastic work and props for open sourcing the site.

I will be reading the code to this one!

Thanks

Great stuff looking forward to seeing more ARM based hosting services.

Been using labs.online.net for a few months and it has been fantastic.

Good luck!

Great post really enjoyed it.

Also a big fan of golang, loving the posts by people using it in anger.

Thanks

Great read, it is very interesting reading about the process you followed designing and building a hardware project from scratch.

Hopefully this encourages more people to have a shot at building something interesting, and write about it.

Thanks a lot.

I have learnt a small amount of it a few times, I use and rely on RabbitMQ every day so it is important I know a bit about it.

That said I just can't get over how bizarre and jarring the syntax is, this paired with the configuration structure and error messages really make it hard to get into to.

Having seen a few talks on the subject I tend to agree, more recently I am using golang for most of the things I intended to do in Erlang.

The reason I chose this route is to stick with a syntax which is common to all the languages i use day to day, while exploring a new, but much smaller toolset for building concurrent applications.

It seemed to me a much wiser route in the long run.

That said I still like the Erlang runtime and the modules it provides, if only the authors of the language could chart a course out of this unusual and sometimes frustrating syntax.

On elixir, I really hope this catches on but unfortunately like coffee script you will still need to get your hands dirty in Erlang if you want to wrap any existing libs or modules available in the runtime, or debug the crazy error messages it produces from time to time.

Enjoyed watching these so far, great to see someone stepping up to help get people started with golang.

Thanks

Yes one of goals is to open source the entire platform.

Great tutorial, look forward to the next one.

Clojure, and indeed LISP is one of the things I would really like to learn but most of the tutorials have been way to academic in there format. This one so far has been much more focused and clearer on the intent of the language.

Thanks

I really wish that HP, Dell or anyone else would do the same in Australia.

I cannot for the life of me buy a laptop with ubuntu preloaded today.

I look forward to this initiative spreading further :)

I currently use a couple of things:

* Heroku

* ec2 using awsbox for dev with push deploys https://github.com/mozilla/awsbox

If you want SSL support and have a few apps then heroku can be a bit expensive, also monitoring is a paid addon.

Lots of choices at the moment which is awesome.

+1 on the excellent news, makes it especially easy for hobbyist like myself to mess around with this sort of thing.

Awesome to see use of vagrant to get started quickly!

Great new site, love the 'browserify v2: less features, more unix!'

Look forward to trying to this out.

Very disappointed with the people that made these statements, they should know better.

Kicking other peoples puppy is never cool, people forget where they started.

Some times you have to take this sort of crap on the chin and keep hacking away, the best thing you can do in situations like is just ignore them.

I think in this case they have realised how stupid their statements where and are hopefully truly sorry for the hurt they have caused.

Also a note to those with many followers, don't be a dick.

Working a small development shop I can tell you that if we buy an off the shelf workstation it can take almost as much time to clear our the crap ware and configure the drivers as it does to build a machine from parts, even considering the work it takes to quote/order/pickup/assemble a system.

It is a very sad state of affairs when NONE of these vendors offer a service to sell you one without crap ware..

This costs small business so much time it is a very bad joke!

Great news, would be a welcome addition to JRuby!

Interested to do some testing as it comes together and see what I can help with.

After some consideration I would probably err on the side of caution and either use something like IPSEC AH (Authenticated Header), or build a session key exchange protocol using something akin to it's two phase approach, or even just perform HTTPS based request to exchange session keys.

This session key could then be incorporated into each of the HMAC signatures and would be refreshed on a regular basis similar to how IPSEC does it.

I have used AH in the passed for log data which required the receiver to verify the source for auditing purposes, but this was quite some time ago, these days most systems just either use SSL or IPSEC with ESP.

Reinventing the wheel is probably not the best idea in this case.

Will add a note on this to my blog post for completeness.

For more information on IPsec see http://en.wikipedia.org/wiki/IPsec

I am interested as to how this would be done with a REST API.

Would it be required that a client perform a pre call for each request, or for a window of requests possibly.

I have seen this sort of thing in SOAP aka WS-Security with their SecureToken.

I mite try put something together an example and see how it works out.

Thanks for the comment.

Yes what I should have said was repeatable signatures are hard across large strings.

Having just worked on this with a few people implementing independent implementations everyone got at least one character wrong, and therefore a complete missmatch of signature.

For those involved this was pretty frustrating.

Site is a joy to use, and enjoying the new design touches.

The iTunes option is a great addition.

Keep it up!

Great talk, love the commentary relating the the index contributions by the Russian contributors really impressive work.

Read and write performance improvements are something that will directly improve even current applications.

Talks like this provide valuable insight into what is going on in this amazing project.

Great post, it is great to see startups being open about how they architect their systems and overcome issues with scaling.

This sort of information helps people building the next group of startups save both time and money.

Keep up the great work!

Great post, not only did it present a good argument, but it also explained a bit about AMD which I had never heard of before.

Thanks

Hacking around with it now looks awesome, especially love the background effect on the documentation page.

Enjoyed this talk, should certainly be taken with a grain of salt but overall some great lessons to learn.