Jorgeu's code @jorgeucode - Tumblr Blog

Aprender un nuevo idioma.

Para las personas que nos cuesta aprender varios nombre de la misma cosa, aprender un nuevo idioma es más que un súper reto.

Comenzamos con clases en el colegio y luego a clases privadas sin tener mucho éxito, intentamos por internet, lo que venga porque para obtener mejor trabajo, mejor sueldo, mejor vida debemos comunicar nuestras ideas a diversas personas y lidiar con diferentes culturas.

Más que una herramienta es una forma de vida, puesto las palabras que suenan diferente pero es lo mismo para ciertas culturas tiene altibajos de intensidad e importancia, entonces no es solo aprender un idioma es aprender la cultura de las personas a las cuales nos dirigimos para no ofender apesar que sabemos el idioma.

Aquí voy intentando una vez más portugués esperando aprender su cultura, tradiciones y de esa manera no olvidar tan fácil las palabras.

😜🤓

Preparing for something new

Can’t say much about it but a new challenge is raising here. I hope I can be up to it and keep growing as a professional.

There is always the inevitably comparison with leading role models. Something I have learnt in time is that you have to swallow your ego and recognize you don’t know everything and that there is smarter people you should listen.

I don’t have a problem with AJAX

I do have a problem with the abuse of it

You’re getting older when...

You try to remember for how many years you’re using a particular piece of software and it goes beyond 10 years.

Today: Eclipse for 12 years

Alarms everywhere

The importance of alarms. Don't ever underestimate them or complain about their annoyance. Put alarms for high cpu, too many calls, too few calls, disk near full, non-success return values, and more.

Define what's "normal" and try to make alarms on every metric getting out of range. It can be annoying but also can avoid greater harm.

Inserting gist in tumblr

https://gist.github.com/1395926

Perl regexp is slower than grep

I was processing some logs and transformed the big script I had into a single perl script. Then noted it was taking more cpu and was slower than my previous ugly script that evaluated the main regexp with grep -P.

As usual went into stackoverflow and found this http://stackoverflow.com/questions/14453584/which-is-more-efficient-perl-pattern-matching-or-grep

Basically, the default perl implementation isn't "state of the art". I'm in shock!. Fortunately, you can use a different engine like a someone suggested in a comment to the accepted answer --> https://metacpan.org/module/re::engine::RE2

That's why I love stackoverflow. So much easy to access knowledge.

#perl #grep #linux #regexp

How testing have changed my career

Reload the page or just give it a shot or two was my testing at the beginning of my career back in 2005. At that point my code/bug ratio was huge. Most of the time were spent recompiling and running again just to go back to the code to hunt that line creating the problem.

About 2008 I move a company where I was the main developer. Maybe too soon for my experience but I felt ready for the challenge. I started to make small ephemeral integration tests in a main method to run in the command line. I didn't tested everything that way though nor call it unit or integration testing. I was still building and giving it a shot for the most part. Also, there were a lot of production testing with customer requests as recreating those scenarios had a cost. Still, testing and mocking could help.

When moved again in 2011 I finally had the chance to work in a organization where testing started to become a daily thing. Also continuous integration with hudson/jenkins. I started to capture bugs in an integration test and the fixing it. Not all the time though but I got the understanding that the bug will announce itself next time. We can pack with that subject and move to the next problem. Its like feeling freedom to break things, innovate, let the code evolve with confidence that the core components were still working correctly.

Then moved to Amazon and now I'm worried about code coverage of unit tests, accuracy of integration tests, approval tests during continuous integration, documenting how to safely deploy and verify its working on production as expected. Much more engineering, confidence, and so on. Any line of code will be executed millions of times per hour. Even smaller optimizations have a huge impact and no matter how silly a test case look, it will serve for a long time with hundreds of code changes a year.

The way I design software component changed forever. When I make a constructor my priority #1 is how the testing set up will look like. Untestable classes aren't possible anymore (like those final and that constructs its dependency inside). The holy grail is being able to mock everything outside the class. Sure, sometimes we can relax the requirement specially with legacy code.

I remember when I said I that I had not time to write code that test the code. Sure it adds extra developer hours when making changes because some tests might break here and there but now I know that manual testing + rolling back production because of an undetected bug costs way more than maintaining the test code.

Hope I were able to write this in a generic way so it can be digested by any developer no matter the language.

Happy testing.

#software #engineering #testing

The better I do testing, the bigger the problem I can be involved

I will write more about it. But for now I just want to say that unit/integration testing is one of the more important skills a software engineer can have. I remember myself underestimating its impact and considering that people talking about it were charlatans. What a mistake!.

Go and learn more about unit testing, integration tests, and anything related.

Lucky kids these days have stackoverflow. I had to learn almost without internet. Envious!

Who listen for ports in Linux

# netstat -tanp | grep LISTEN

#linux

A nice way to tell Hibernate to stop trying to save dirty objects. What we tell it in that method is "no fields have been changed". For long time we struggled with hibernate trying to be too intelligent saving object we didn't intended to. Now the beast is under control.

#java #hibernate #dirty object flush

Fogus on Scala

Scala, like C++, is extremely flexible in allowing you to pick and choose which 20% to use for your enterprise software needs.

— Fogus (@fogus) enero 28, 2014

#scala #fogus

Ruby puts buffer non-sense

Set this to make it work as the rest of the world

STDOUT.sync = true

#ruby

AWS SDK For Ruby

When working with the EC2 interface you have 2 options: low level client and the "activerecord like" instances interface.

Here is the doc for the low level client: EC2 Client

And this is for the "idiomatic" one: EC2 Instances

Is was very helpful to read these docs.

Create a new instance?

instance = ec2.instances.create(:image_id=>'<your image id>', :instance_type=>'<your instance type>', :security_groups=>['<the security group>'])

#ruby #aws

AWS SDK for Ruby do a good job emulating the idiomatic 'activerecord like' way to create/read things

#aws #ruby

Hey Adobe is doing the right move with Flash Pro. Now with HTML5 animations. Great!

#flash #adobe

Trending Blogs

Recently Viewed Blogs

Jorgeu's code