Category Archives: Web

LinkedIn API change: worst business decision I’ve ever seen

I’m working in the IT since 15 years, I’ve been entrepreneur and CTO and freelance, I’ve seen a lot of good and bad decisions in these years, this is probably the worst ever, take a seat and enjoy the ride.

Since a few days LinkedIn is not allowing developers to create apps that access the “fullprofile” and “contactinfo” APIs. The info that they keep providing to the developers is just the basic profile with has just a couple of contacts information and the working “positions”.

This data is so little (compared to a “normal” résumé) that it’s completely useless.

I’ve three general thoughts about this decision:

  • as a LinkedIn user I can’t use my own data (because hey, it’s user generated content) anymore as I want, and this is making me think “should I keep giving my data to a company that do not give me the possibility to use it as I want it?“. For my point of view the answer is no and I’ll see what I will be doing with my own LinkedIn profile.
  • as a developer I’ll go to some LinkedIn competitor (XING anyone), which I now hope it’s going to grow despite of LinkedIn “monopolistic” position. I really can’t understand what’s on LinkedIn top guys to tell developers “we don’t want you, go use our competitors”. Every company should make its ecosystem grow, not shrink, am I right? They are instead deliberately doing the opposite.
  • as a developer (again) I’ll probably have to build a LinkedIn competitor. I know it sounds simply silly, how you can compete with a giant… but don’t you know that before Facebook there was MySpace? Where is it now? And we have a lot of example like that. So now LinkedIn is encouraging people to create its own competitors and it sounds a little bit absurd to me. It’s like (back in the time) Altavista was saying “hey why don’t you build your own search engine?”. I’m obviously not comparing my position to those big situations…

And I also have one personal thought about my own app called VeloCV:

  • I was telling my users “keep using LinkedIn, that’s your main tool, do not maintain 2 different profiles, you’ll never come here on velocv and modify your profile, everything will always be paired to LinkedIn”. I was being fair to LinkedIn and I was not competing with them, I was part of the ecosystem giving the users some more value to their LinkedIn data (their, of the users, data) to fill a gap in LinkedIn features. Both (VeloCV and LinkedIn) would have benefit from that cooperation.

What I’m doing now with my project?
I’ll migrate my softwares to XING, I’ve already created my XING profile (I never had one before so, again, good choice LinkedIn) and I’ll probably create some more UI to allow people to subscribe VeloCV also without a LinkedIn/XING profile and let’s see what happens. It’s gonna be hard (LinkedIn has 315 milion users, XING 14…) but what should I do?

I would like to hear what you think about this, are you a developer that got kicked out of LinkedIn API access? Are you a user that doesn’t have a fully working app anymore? Please let me know.

The rise and fall on my newborn startup

As a freelance developer I use my résumé almost daily, it’s my main tool to get new jobs. I also have other websites, like:

  • a personal “commercial website”, which is more or less just my CV plus a few other things
  • a tech blog
  • some websites for some of my personal/open source/commercial projects

Obviously I have a LinkedIn profile, which is also a very important tool for my job. Continue reading

Magento PHP developer’s guide

It really was a long time since my last review of books about Magento, in the meanwhile some of you may know that I’ve been to a Magento U class in Berlin and I’ve taken 3 of the 4 Magento certifications. I’ve been through some really busy months but now I should be back on track. Continue reading

Instant Magento performance optimization howto

I just finished reading the Instant Magento performance optimization howto ebook by Packt and I’m about to write a quick review.

First of all this book is short (50 pages), quick and easy to read. Don’t misunderstand me, for me this is a big plus: Magento is a big universe and for me it’s better to have more specialized books instead of one big book covering everything (which is actually impossible).

Performance are also a big trouble for everyone who works with Magento so anyway this book is a little investment for a nice and complete (also if not very deep) reading (but also a practical manual) on Magento performance overview.

The book covers all the aspects of the optimizations, from CSS/Javascript compression to logging to compiling etc. It also covers some advanced topics like mysql configurations and clustering but here I would have liked to see more details (on mysql tuning we probably need more than just a my.cnf sample and on clustering we’d need to talk about percona, how to configure mysql clusters with practical configurations or link to video tutorials).

I’d rate this book 7.5/10, as an advanced developer I would have liked more advanced details but probably this should have gone beyond the scope of the book itself so at the end… it’s totally worth its money and most of all it’s a good read for all the kind of Magento workers, from designers to coders to system managers.

“Mastering Magento” first look

I just received the Mastering Magento ebook from Packt a few hours ago, I’m really out of time in these weeks but I wanted to share a couple of thoughts from the first look at this book.

If you’re a Magento developer, than get it, from a really quick view (I’m gonna review it later) I think I’ll buy the printed copy to keep on my desk, as a senior Magento developer I already know most of the things writting in the book but it is really well written, full of useful information and it will become helpful when you’ve to do something quick but you don’t remenber exactly how to do it or a particular meaning of a Magento terminology.

It seems to cover all the main areas and it has a really lifesaver section which is the pre-launch checklist.
Also very useful if you’re teaching a junior developer/designer and you need a deeper introduction to Magento (this book is not for who didn’t see Magento before in his life).

Another thing I think, it could be easily split in 2 version cause the introduction says that the book is intended for developers and store owners but I think that store owners should not be bothered with all the dev stuff, anyway part of the book would be really perfect to be given to store owners saying “hey this is the Magento manual” :-)

“Magento 1.4 Themes Design Cookbook” review

As I wrote a few days ago, I was asked to review the Magento 1.4 Development Cookbook by Packt so I took the right time to read it deeply and with great attention to point out every pro and con of this mid-length book (249 pages).

First of all the book is available at a price of ~40 USD (~31 EUR) if you want the paper book, or ~32 USD (~25 EUR) for the digital copy (in PDF format), the price is right (maybe just a little high) for a highly technical book like this. You’ll also receive a comprehensive archive of all the code that’s used in the book, really useful for a quick cut&paste to try out things!

Now, I’ve to say that Magento 1.6 is near to be released and still we’ve no book about 1.5, and also if 1.4 documentation is still valid I think that it would be the time to update all the books on the new releases.

Chapter 1: I think it’s completely useless unless for the section about the differences between 1.3 and 1.4, in this moment every designer about to design and/or code a Magento themes already know what can be done and surely has seen enough themes in the wild so I think that we don’t need an introduction or a showcase.

Chapter 2: this is one of my preferred chapters, ok it’s not so difficult but it explains all the basic concept and it’s really needed for the first timers. I think this chapter should have been the first one but anyway it’s great.

Chapter 3: probably it could be merged with the 2nd ’cause it keeps talking about the basic things you need to know when you’re about to start working on a Magento themes, useful but anyway I think none needs a “where do I get inspiration for a favicon” section. The “display products on the homepage” section is instead really useful and raises the level of this chapter.

Chapter 4: first real steps into customizing a default Magento theme to fit your design, with some more basic hits (like enabling template path hints and block names hints) and some detailed info about CMS pages (which actually area managed pretty bad in Magento).

Chapter 5: creating a theme from scratch, pretty advanced things are going on here :) and that’s the kind of things I like the most.

Chapter 6: starts with a useless section about integrating font-face into a Magento theme, actually I don’t understand why this kind of info should be in a Magento book, it should have been in a HTML/CSS one… but finishes with some pretty handy documentation about “navigation” and the “product view” template.

Chapter 7: the part I liked the most about this chapter is about creating a custom block and using it in a layout xml file, other things (adding javascripts or stylesheets) are a little too basic at this point.

Chapter 8: talks about mail templates, pretty basic stuff in the beginning, getting interesting later with variables in emails and a good section about how to integrate external newsletter systems and another one on upgrade-proof email templates.

Chapter 9: integrating social stuff, absolutely basic notions about copying facebook’s html widgets and paste it in your templates…

Chapter 10: print styles, once again I think that this topic should be covered in a HTML/CSS guide.

Conclusions: if you never wrote a Magento theme buy this book, it will help you in a lot of ways. The second time you’ll have to do the same work again… you won’t need it.