Why the hacker metaphor is wrong

Celebrating new business should always be normal stuff but for some reasons not immediately understandable it is rarely like that. If the business environment where we all do our own interests was different today probably we do not know about them and there should be no channel to amplify *the hacker metaphor* at all.

And here I try to explain the reasons:

- No one could attack a business interest if this business has some fair foundation basis.
- No one could attack a business interest if most of the people is business driven.
- No one could attack a business interest if the hackers are its founders or the hackers are at its center.

Indeed let's say that our today business environement is far from conceiveing (in the West) any of the above conditions: business many times do not behave fairly; many people is not *appointed* to be business driven; and finally the hackers are going to be excluded from most of the businesses.. One more consideration comes enphatizing that the IT sector and the *virtual world* as we know them - ambitious arrival of many of today big medium small size businesses - have the hackers works at their foundation.

Joke: Github blog is finally out..

Hey Jude, Github blog is out?

This is just a mere joke. Please take a seat in our cafe enjoying your talking..

Help, HR is from the Sales!

We live in a world full of unconfidence: monsters, violence and viruses. But this time I dreamed the worst stuff as possible: what about if the HR became the best sellers inside tech companies?

Let's analyse the new scenary. An HR should have to:
- analyse the technology and its competitors
- define the best search and approach
- define the target audience to reach
- optimyze its own hr profile
- define a publishing strategy
- publish ads
- define strategies to reach audience
- analyse results
- define new strategies

Let's say it together:
I will never do sales!
I will never do sales!
Let's generate leads..

Leads? Oh, noo..

Personal introverse view

(to not confuse with "metaverse")

Recuiting was never an easy job.

There are persons and persons, attitudes and attitudes: and saving the day has never been a job for everyone.

Not rarely, also in the IT offices there are important confrontations among employees, one all the jobs doing fully in charge of different projects and responsibilities, the other one enjoying its day like at an eve parade. I call these latter the "cheers girls", for simplicity reasons only..

Don't missunderstand me, in this world we are in the need of everyone (apart who bring the Covid home, maybe), but all this matter make me think that the job of the HRs must upgrade and concentrate enough in understanding not just the beauty of a person, interiorly speaking, but if the given person is or could be fine for a certain job. Because ie. for a software developer concentrated on tasks, efficency, coding simplicity and minimalism "probably" is just a little overwhelming meeting the cheers girl while dancing on its own desk.

All of us are surely in the need of nice "girls" able to grab the "business" but franckly speaking distinguishing them from the optimal code guru should be necessary, IMHO.

So, waiting the HRs that, beside discriminating on gender and veteran status will upgrade to correctly disguise about "the cheers girls!" I suggest to write down this one taken from my personal memes: despite the stupid stuff of the kick-ass what I can do to save the day?

I'm local: yes or no?

Today, there is a new, last trend that bet on the "local business". Question popping up soon: is it convinient to be classified as local business?

Prefance: if you go to East, like in China, you are very quick to realize that any size business entity is playing - taking advantage of some easy web instruments - to target the global market. And last quick discovery: if you export certain categories of products you can fit in the scope of some government special tax discounts or free trade zones.

In the West the environement conditions are very different and being local today it is mere matter of sizing business (to not confuse with business size).

We take the example of us, in NuMode. NuMode is a software developer from Bologna, Italy:
- If we advertise NuMode like a developer of Italy (like we generally do) we will never have market in China.
- If we advertise NuMode like a developer of Bologna (like we generally do) we will never have market in Milan, the main business center of Italy.

Said that it appears clear that being local it is not interesting at all? Good point!

Joke: no tablet? aya-ya-yai

Consciously escaping from the Ubiquity market is like sticking on amulets and horns all the life. Misfortune can be tough.

You are welcome to seat in our café and use our tablet, eheh

The software developer ocean

Managing a software business today is like a looping serie of waves:
the achieving job wave (iterated)
the archiving job wave (unforgetable)
the rebasing business wave (final solution)
and again..the achieving wave, etc.

Frankly speaking there is also "the content job wave" - even much trandy today - but let's say..that kind of stuff that doesn't take to any developer emancipation : )

Standalone software vs Internet

There is little need for fantasy to grasp that the software world has been divided since a while between two kind of *think tanks*, the standalone software one and the Internet one. And this is a shame.

A shame because since the very beginning of Internet, the network has been under the microscope of an important part of the IT scholars; franckly cause today no one could write down software that doesn't use any kind of web service; and finally because Internet since its origins brought great openess.

There are positions and positions about all this matter but we want to reveal you two quotes from our lives to support our personal opinion that most of the noise against Internet is just for business interest:
I see little commercial potential for the Internet for at least ten years, Bill Gates.
You are a mere nazi to work on the web, an anonymous software engineer.

Since 25 years ago, when we started up our careers we didn't stop to be enthusiastic about *the knowledge economy*. And for the same reason we, in NuMode will continue to support the web dispite any partisan interest and exactly for the matter of its great openess.

No backend, live in sec

We all come from a school: the old one of coherence, minimalism and simplicity or the new one, that one of "biblic methods length".. but any school you come from they teach two stuff you should implement:
- frontend
- backend

I haven't said yet, in NuMode we come from our own school where content and TTM became *our keywords*. And to understand that we passed by a project (Gallery) spending just 2 YEARS into database, engine algorithms, translitarates, etc. changes and transformations. All with a backend to implement, maintain, transform and finally suppress.. Why suppress? In a market where content got its place to lead we understood that spending time in ie. authoring takes more results at home than investing on the backend. And we can't say you how much we are happy to be, now, on the market in time fashion with all our web apps..

Remember, any school you come from is right except some important details that you can find out only by your own empirical approach, sticking on your mission and if you can without backend.

PHP long way to perfection

Reaching perfection is something difficult to obtain but leaving the opportunity to do stuff with detail and attention is probably the worst fault you can do. This is true although you want to be *supportative* with legacy code.

PHP is today the preferred programming language of most people to build stuff on the web but surely to become a mature language still luck of some *attributes*:
- Consistency. If often you can choose how to do stuff not always happens that same context instructions work by the same basis/method starting from the signature.
- Engineering. It is fine to leave to the consumer or web developer the choise how to do stuff but simplify till missing the implementation result should be hard, and sometime it is not.
- Evolution. Thanks gosh PHP continues to be compatible with legacy code but some instructions remain hard to use since centuries.
- And it is buggy like many things in this world.

Sometimes we - developers - enjoy our part, a lot, till missing the way without recognizing the necessity to listen and to reach the goal. It is always time for a change. And mainly when we talk about something yet so big like PHP.