O problema reside entre a cadeira e o teclado ...

GIT - the stupid content tracker

2014-11-24T15:36:00.000+01:00

"Initial revision of "git", the information manager from hell ~ Apr 2005"

GIT - the stupid content tracker

"git" can mean anything, depending on your mood.

- random three-letter combination that is pronounceable, and not
actually used by any common UNIX command. The fact that it is a
mispronounciation of "get" may or may not be relevant.
- stupid. contemptible and despicable. simple. Take your pick from the
dictionary of slang.
- "global information tracker": you're in a good mood, and it actually
works for you. Angels sing, and a light suddenly fills the room.
- "goddamn idiotic truckload of sh*t": when it breaks

This is a stupid (but extremely fast) directory content manager. It
doesn't do a whole lot, but what it _does_ do is track directory
contents efficiently.

There are two object abstractions: the "object database", and the
"current directory cache".

The Object Database (SHA1_FILE_DIRECTORY)

The object database is literally just a content-addressable collection
of objects. All objects are named by their content, which is
approximated by the SHA1 hash of the object itself. Objects may refer
to other objects (by referencing their SHA1 hash), and so you can build
up a hierarchy of objects.

There are several kinds of objects in the content-addressable collection
database. They are all in deflated with zlib, and start off with a tag
of their type, and size information about the data. The SHA1 hash is
always the hash of the _compressed_ object, not the original one.

In particular, the consistency of an object can always be tested
independently of the contents or the type of the object: all objects can
be validated by verifying that (a) their hashes match the content of the
file and (b) the object successfully inflates to a stream of bytes that
forms a sequence of <ascii tag without space> + <space> + <ascii decimal
size> + <byte\0> + <binary object data>.

BLOB: A "blob" object is nothing but a binary blob of data, and doesn't
refer to anything else. There is no signature or any other verification
of the data, so while the object is consistent (it _is_ indexed by its
sha1 hash, so the data itself is certainly correct), it has absolutely
no other attributes. No name associations, no permissions. It is
purely a blob of data (ie normally "file contents").

TREE: The next hierarchical object type is the "tree" object. A tree
object is a list of permission/name/blob data, sorted by name. In other
words the tree object is uniquely determined by the set contents, and so
two separate but identical trees will always share the exact same
object.

Again, a "tree" object is just a pure data abstraction: it has no
history, no signatures, no verification of validity, except that the
contents are again protected by the hash itself. So you can trust the
contents of a tree, the same way you can trust the contents of a blob,
but you don't know where those contents _came_ from.

Side note on trees: since a "tree" object is a sorted list of
"filename+content", you can create a diff between two trees without
actually having to unpack two trees. Just ignore all common parts, and
your diff will look right. In other words, you can effectively (and
efficiently) tell the difference between any two random trees by O(n)
where "n" is the size of the difference, rather than the size of the
tree.

Side note 2 on trees: since the name of a "blob" depends entirely and
exclusively on its contents (ie there are no names or permissions
involved), you can see trivial renames or permission changes by noticing
that the blob stayed the same. However, renames with data changes need
a smarter "diff" implementation.

CHANGESET: The "changeset" object is an object that introduces the
notion of history into the picture. In contrast to the other objects,
it doesn't just describe the physical state of a tree, it describes how
we got there, and why.

A "changeset" is defined by the tree-object that it results in, the
parent changesets (zero, one or more) that led up to that point, and a
comment on what happened. Again, a changeset is not trusted per se:
the contents are well-defined and "safe" due to the cryptographically
strong signatures at all levels, but there is no reason to believe that
the tree is "good" or that the merge information makes sense. The
parents do not have to actually have any relationship with the result,
for example.

Note on changesets: unlike real SCM's, changesets do not contain rename
information or file mode chane information. All of that is implicit in
the trees involved (the result tree, and the result trees of the
parents), and describing that makes no sense in this idiotic file
manager.

TRUST: The notion of "trust" is really outside the scope of "git", but
it's worth noting a few things. First off, since everything is hashed
with SHA1, you _can_ trust that an object is intact and has not been
messed with by external sources. So the name of an object uniquely
identifies a known state - just not a state that you may want to trust.

Furthermore, since the SHA1 signature of a changeset refers to the
SHA1 signatures of the tree it is associated with and the signatures
of the parent, a single named changeset specifies uniquely a whole
set of history, with full contents. You can't later fake any step of
the way once you have the name of a changeset.

So to introduce some real trust in the system, the only thing you need
to do is to digitally sign just _one_ special note, which includes the
name of a top-level changeset. Your digital signature shows others that
you trust that changeset, and the immutability of the history of
changesets tells others that they can trust the whole history.

In other words, you can easily validate a whole archive by just sending
out a single email that tells the people the name (SHA1 hash) of the top
changeset, and digitally sign that email using something like GPG/PGP.

In particular, you can also have a separate archive of "trust points" or
tags, which document your (and other peoples) trust. You may, of
course, archive these "certificates of trust" using "git" itself, but
it's not something "git" does for you.

Another way of saying the same thing: "git" itself only handles content
integrity, the trust has to come from outside.

Current Directory Cache (".dircache/index")

The "current directory cache" is a simple binary file, which contains an
efficient representation of a virtual directory content at some random
time. It does so by a simple array that associates a set of names,
dates, permissions and content (aka "blob") objects together. The cache
is always kept ordered by name, and names are unique at any point in
time, but the cache has no long-term meaning, and can be partially
updated at any time.

In particular, the "current directory cache" certainly does not need to
be consistent with the current directory contents, but it has two very
important attributes:

(a) it can re-generate the full state it caches (not just the directory
structure: through the "blob" object it can regenerate the data too)

As a special case, there is a clear and unambiguous one-way mapping
from a current directory cache to a "tree object", which can be
efficiently created from just the current directory cache without
actually looking at any other data. So a directory cache at any
one time uniquely specifies one and only one "tree" object (but
has additional data to make it easy to match up that tree object
with what has happened in the directory)

and

(b) it has efficient methods for finding inconsistencies between that
cached state ("tree object waiting to be instantiated") and the
current state.

Those are the two ONLY things that the directory cache does. It's a
cache, and the normal operation is to re-generate it completely from a
known tree object, or update/compare it with a live tree that is being
developed. If you blow the directory cache away entirely, you haven't
lost any information as long as you have the name of the tree that it
described.

(But directory caches can also have real information in them: in
particular, they can have the representation of an intermediate tree
that has not yet been instantiated. So they do have meaning and usage
outside of caching - in one sense you can think of the current directory
cache as being the "work in progress" towards a tree commit).

source

Android platform version

2014-08-11T18:03:00.000+01:00

Platform Version	API Level	VERSION_CODE	Notes
Android 4.4	19	`KITKAT`	Platform Highlights
Android 4.3	18	`JELLY_BEAN_MR2`	Platform Highlights
Android 4.2, 4.2.2	17	`JELLY_BEAN_MR1`	Platform Highlights
Android 4.1, 4.1.1	16	`JELLY_BEAN`	Platform Highlights
Android 4.0.3, 4.0.4	15	`ICE_CREAM_SANDWICH_MR1`	Platform Highlights
Android 4.0, 4.0.1, 4.0.2	14	`ICE_CREAM_SANDWICH`	Platform Highlights
Android 3.2	13	`HONEYCOMB_MR2`
Android 3.1.x	12	`HONEYCOMB_MR1`	Platform Highlights
Android 3.0.x	11	`HONEYCOMB`	Platform Highlights
Android 2.3.4 Android 2.3.3	10	`GINGERBREAD_MR1`	Platform Highlights
Android 2.3.2 Android 2.3.1 Android 2.3	9	`GINGERBREAD`	Platform Highlights
Android 2.2.x	8	`FROYO`	Platform Highlights
Android 2.1.x	7	`ECLAIR_MR1`	Platform Highlights
Android 2.0.1	6	`ECLAIR_0_1`
Android 2.0	5	`ECLAIR`
Android 1.6	4	`DONUT`	Platform Highlights
Android 1.5	3	`CUPCAKE`	Platform Highlights
Android 1.1	2	`BASE_1_1`
Android 1.0	1	`BASE`

source

Android Logging

2014-03-18T10:34:00.000+01:00

Android Log.v(), Log.d(), Log.i(), Log.w(), Log.e():

When to use each one?

Log.e: This is for when bad stuff happens. Use this tag in places like inside a catch statment. Youknow and error has occurred and therefore you're logging an error

Log.w: Use this when you suspect something shady is going on. You may not be completely in full on error mode, but maybe you recovered from some unexpected behavior. Basically, use this to log stuff you didn't expect to happen but isn't necessarily an error. Kind of like a "hey, this happened, and it's weird, we should look into it."

Log.i: Use this to post useful information to the log. For example: that you have successfully connected to a server. Basically use it to report successes.

Log.d: Use this for debugging purposes. If you want to print out a bunch of messages so you can log the exact flow of your program, use this. If you want to keep a log of variable values, use this.

Log.v: Use this when you want to go absolutely nuts with your logging. If for some reason you've decided to log every little thing in a particular part of your app, use the Log.v tag.

And as a bonus :

Log.wtf: Use this when stuff goes absolutely, horribly, holy-crap wrong. You know those catch blocks where you're catching errors that you never should get...yea, if you wanna log them use Log.wtf

wtf -> What a Terrible Failure

href:

Map . Data Structure

2014-03-17T10:55:00.001+01:00

There are 4 commonly used implementations of Map in Java SE:

HashMap, TreeMap, Hashtable and LinkedHashMap. If we use one sentence to describe each implementation, it would be the following:

HashMap is implemented as a hash table, and there is no ordering on keys or values.
TreeMap is implemented based on red-black tree structure, and it is ordered by the key.
LinkedHashMap preserves the insertion order
Hashtable is synchronized, in contrast to HashMap.

This gives us the reason that HashMap should be used if it is thread-safe, since Hashtable has overhead for synchronization.

href:

PS: What is the difference between implementing Comparable and Comparator?

Comparable

A comparable object is capable of comparing itself with another object. The class itself must implements the java.lang.Comparable interface in order to be able to compare its instances.

Comparator

A comparator object is capable of comparing two different objects. The class is not comparing its instances, but some other class's instances. This comparator class must implement the java.util.Comparator interface.

href:

DLL em uso ?

2014-02-19T11:38:00.001+01:00

Para descoberta dos processos que referenciam/usam/bloqueiam a DLL:

Command line : tasklist /m thelocked.dll

Porreiro pah !

2013-10-30T10:31:00.001+01:00

Acabei de receber um email das Finanças.

Apeteceu-me responder : "Porreiro pah !"

Exmo.(a) Senhor(a)

ZéCarlos
NIF: 000000000

A Autoridade Tributária e Aduaneira (AT) encontra-se já a desenvolver os mecanismos de atribuição do crédito de IRS que lhe cabe, em resultado de ter vindo a exigir a inserção do seu Número de Identificação Fiscal (NIF) nas faturas correspondentes a transações que lhe foram efetuadas.
Como sabe, esse crédito corresponde a 15% do IVA suportado (com um limite máximo de € 250) nas prestações de serviços efetuadas pelas empresas enquadradas nos sectores de atividade de alojamento e restauração, cabeleireiros e reparação de automóveis e motociclos.
Cumpre-me agradecer-lhe o papel que, por via da prática destes simples atos de exigência de fatura nas transações em que intervém, tem desempenhado no esforço de combate à economia paralela e à evasão fiscal em Portugal. A AT cumprirá também o seu papel no processo, zelando para que os seus impostos não sejam desviados para fins ilícitos.
Exigir fatura é um direito cívico, que garante que os impostos que pagamos são entregues ao Estado e é também um dever, porque a tarefa de diminuir os graves custos financeiros e sociais que suportamos em razão da existência da economia paralela, nos cabe a todos, enquanto cidadãos.
Cerca de 2 milhões de portugueses solicitaram a inserção do seu NIF nas faturas referentes às atividades que concedem benefício fiscal e inseriram faturas no Portal das Finanças, contribuindo assim para um sistema fiscal mais justo.

Com os melhores cumprimentos,O Diretor-Geral
José António de Azevedo Pereira

FYI : CRM within Gmail

2013-03-06T10:11:00.000+01:00

http://www.streak.com/

Streak is a Google Chrome Extension that adds extra tools to Gmail letting you manage relationships directly within your inbox.

Managing relationships is done by grouping email conversations into Boxes and placing those Boxes into Pipelines.

Streak's primary use is for Sales and Customer Support but is flexible enough to be useful for everything from a personal To-Do list to Project Management.

- A Box is where you put all the emails, files, contacts and information related to something you want to track. If you're using Streak for sales then you'd use a Box to store all the conversations and information related to a particular deal. If you're doing hiring then you'd have one Box for each candidate.

- A Pipeline is used to manage some workflow or process that has multiple activities at any given time. The defining characteristics of a Pipeline are the Stages of the Pipeline and the Columns that apply to each Box.

o An example that illustrates best would be a pipeline that keeps track of people that owe me money. For stages I'd have "Owes", "Partially paid", "Fully paid", "Forgiven". And then for columns I'd have one column to know when I gave the person the money, another column to track how much they owe me, and another column to track how much they've paid me back. I can also do this with the people I owe money to.

Streak is currently in beta and is free to use. We will offer a paid version in the future but we always plan on having a free version to use.

"KEY to success"

2012-11-20T16:09:00.000+01:00

Android Dev : Reverse Engineer (decompile) an APK to Java code

2012-11-14T15:20:00.000+01:00

Unzip APK as zip file
Dex2jar on classes.dex
Open jar in JD-GUI

Android Dev : ProGuard

2012-11-14T14:40:00.000+01:00

http://developer.android.com/tools/help/proguard.html

The ProGuard tool shrinks, optimizes, and obfuscates your code by removing unused code and renaming classes, fields, and methods with semantically obscure names.

The result is a smaller sized .apk file that is more difficult to reverse engineer.

Plataformas sociais

2012-10-30T14:52:00.000+01:00

Twitter = perspectives.

Twitter is great for getting immediate perspectives on news and events. In other words, if you want to learn that there was an earthquake in Chile before CNN, and you like getting updates from people at ground zero, then Twitter is for you. In short, Twitter is for real-time perspectives.

Facebook = people.

Facebook is the way to learn what's going on in the lives of people that you already know (friends, relatives and colleagues). It's great for learning that their cats rolled over, they went to a great party or they had sex, children or grandchildren. In short, Facebook is for people.

Google Plus = passions.

Google Plus enables you to pursue your passions with people who you don't know. Your 50 close friends and family on Facebook may not share your passion for photography, but on Google+ you can have a blast with photographers that you didn't know. In short, Google+ is for passions.

from http://www.openforum.com/articles/should-you-join-google-plus

CrossOver for free on Wednesday, October 31

2012-10-30T09:31:00.000+01:00

I am happy to announce that we will be providing a copy of CrossOver for free to all comers this Halloween, Wednesday, October 31, from 00:00 until 23:59 pm, Central Daylight Time.

To sign up for your free copy or free 12 month extension, simply visit this web page:
http://flock.codeweavers.com any time on October 31, 2012, from 00:00 until 23:59 CDT.

What is the Mars Curiosity Rover's software built in?

2012-08-07T13:36:00.001+01:00

The code is based on that of MER (Spirit and Opportunity), which were based off of their first lander, MPF (Sojourner). It's 3.5 million lines of C (much of it autogenerated), running on a RA50 processor manufactured by BAE and the VxWorks Operating system. Over a million lines were hand coded.

The code is implemented as 150 separate modules, each performing a different function. Highly coupled modules are organized into Components that abstract the modules they contain, and "specify either a specific function, activity, or behavior." These components are futher organized into layers, and there are "no more than 10 top-level components."

It does appear that the testing scripts were written in Python.

source

Para os interessados numa leitura mais completa, sugiro "JPL_Coding_Standard_C" (~22 páginas).

"Scope : The coding rules defined here primarily target the development of mission critical flight software written in the C programming language. This means that the rules are focused on embedded software applications, which generally operate under stricter resource constraints than, e.g., ground software."

Wallet TMN

2012-05-21T11:51:00.002+01:00

Relativamente a Mobilidade, a TMN está sempre uns passos à frente.

Agora já com pagamentos por NFC, SMS, USSD e QR Code.

Mais aqui

HP since 1956

2012-05-21T08:25:00.004+01:00

Samsung SIII ROM Leaks

2012-05-20T21:31:00.000+01:00

, bem como todas as apps internas.

Para os curiosos pelo S-Voice, podem fazer o download e exprimentar (nota: os servidores da Samsung filtram por equipamento, "portantos" tem que usar Samsung também)

link

Folder	Size	Description
/app	435.5mB	Application folder, biggest of them all. The biggest percentage is [2] indeed TouchWiz Apps , with top 30 out of 187 APKs taking up 283MB.
/lib	206.4mB	Proprietary drivers, codecs, thing you won't want to remove.
/hdic	147.6mB	Localisation for about 24 languages, you could shrink this dramatically.
/framework	57.7mB	Android framework, nothing you could shrink here.
/tts	58.8mB	Text-to-speech libraries, again, shrinkable.
/media	27.0mB	Ringtones, alarms, animations
/vendor	25.8mB	More drivers
/etc	12.0mB
/usr	10.0mB
/bin	6.8mB
/fonts	9.0mB
/preloaddata	7.3mB
/vsc	3.6mB
/voicebargeindata	2.3mB
/wakeupdata	1.5mB
/cameradata	720kB
/xbin	64kB

Total 1031mB, and another 200mB for the CSC, Modem and Kernel.

"Um Corpo Estranho"

2012-05-16T22:31:00.000+01:00

, em repeat !

Para acompanhar:

Google Drive lives (kinda ...)

2012-04-24T21:25:00.000+01:00

Google ToS: "When you upload or otherwise submit content to our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content."

SkyDrive ToS: "Except for material that we license to you, we don't claim ownership of the content you provide on the service. Your content remains your content. We also don't control, verify, or endorse the content that you and others make available on the service."

Dropbox ToS: "By using our Services you provide us with information, files, and folders that you submit to Dropbox (together, "your stuff"). You retain full ownership to your stuff. We don't claim any ownership to any of it. These Terms do not grant us any rights to your stuff or intellectual property except for the limited rights that are needed to run the Services, as explained below."

via Reddit.

Howto - Links simbólicos em Windows

2012-04-10T15:37:00.000+01:00

Para uma criação de links simbólicos em Windows, permitindo deste modo, igualar os links a directórios como em "Unix/Linux" podemos usar o comando MKLINK.

Sintaxe:

Segue-se exemplo:

Com a execução de:

Com o comando "mklink /D workspace C:\Users\dfc\Desktop\Dropbox\workspace", criamos um link simbólico em D:\tmp\workspace para uma directoria existente noutra partição. Isto funciona como um "shortcut" mas imita na totalidade a directoria.
Com o comando "rmdir workspace", assumindo o posicionamento na drive/directoria, removemos o link, já que uma remoção normal (via command line ou Windows Explorer) iria remover os conteúdos.

Nota 1: Este truque poderá ser usado em casos que a partição C está com falta de espaço, sendo que via command line de administração (com boot para Safe Mode with Command Prompt) para movermos a pasta "Program Files" de partição, e depois criar o link simbólico "Program Files" na partição original.

Nota 2: "Symbolic links are different from hard links. Hard links do not normally point to directories, and they cannot link paths on different volumes or file systems. Symbolic links may point to any file or directory irrespective of the volumes on which the source and destination reside. Whereas hard links always refer to an existing file, symbolic links may contain an arbitrary path that doesn't point to anything."

Stop SQL Server Management Studio from scripting SPs using sp_executesql

2011-10-19T15:02:00.001+01:00

Turn off the "Include IF NOT EXISTS" option.

It's at Tools..Options, then click "Scripting" on the explorer pane of the dialog that pops-up. the "IF NOT EXISTS" option is in the second group from the top (Object Scripting options).

      EXEC dbo.sp_executesql @statement = N'-- =============================================
      -- Author:          Me
    -- =============================================
    CREATE PROCEDURE [dbo].[MyProc]
        -- Add the parameters for the stored procedure here
        @StartDate datetime
    AS
      BEGIN

BlackBerry blackout, free apps

2011-10-17T12:13:00.000+01:00

Research In Motion (RIM) announced today that a selection of premium apps worth a total value of more than US $100 will be offered free of charge to subscribers as an expression of appreciation for their patience during the recent service disruptions. The apps will be made available to customers over the coming weeks on BlackBerry App World and will continue to be available until December 31 2011.

The selections over this period will include the following :
SIMS 3 – Electronic ArtsBejeweled – Electronic Arts
N.O.V.A. – Gameloft
Texas Hold'em Poker 2 – Gameloft

Bubble Bash 2 – Gameloft
Photo Editor Ultimate – Ice Cold Apps
DriveSafe.ly Pro – iSpeech.org
iSpeech Translator Pro – iSpeech.org
Drive Safe.ly Enterprise – iSpeech.org
Nobex Radio™ Premium – Nobex

Shazam Encore – Shazam
Vlingo Plus: Virtual Assistant – Vlingo

link

/start funny rant

/stop funny rant

iOs 5.0

2011-10-13T21:39:00.003+01:00

"one giant leap for iOs .... One small step for Android"

Google+

2011-10-13T10:03:00.000+01:00

Recomendo a leitura https://plus.google.com/112678702228711889851/posts/eVeouesvaVX sobre o "produto" Google+, escrito por Steve Yegge (um elemento Google), no que supostamente era para ser um post interno, e não público.

tl;dr;

"That one last thing that Google doesn't do well is Platforms. We don't understand platforms. We don't "get" platforms. Some of you do, but you are the minority. This has become painfully clear to me over the past six years. I was kind of hoping that competitive pressure from Microsoft and Amazon and more recently Facebook would make us wake up collectively and start doing universal services. Not in some sort of ad-hoc, half-assed way, but in more or less the same way Amazon did it: all at once, for real, no cheating, and treating it as our top priority from now on."

"Google+ is a prime example of our complete failure to understand platforms from the very highest levels of executive leadership (hi Larry, Sergey, Eric, Vic, howdy howdy) down to the very lowest leaf workers (hey yo). We all don't get it."

"The Google+ platform is a pathetic afterthought. We had no API at all at launch, and last I checked, we had one measly API call."

"Google+ is a knee-jerk reaction, a study in short-term thinking, predicated on the incorrect notion that Facebook is successful because they built a great product. But that's not why they are successful. Facebook is successful because they built an entire constellation of products by allowing other people to do the work. So Facebook is different for everyone. Some people spend all their time on Mafia Wars. Some spend all their time on Farmville. There are hundreds or maybe thousands of different high-quality time sinks available, so there's something there for everyone."

"The problem is that we are trying to predict what people want and deliver it for them...

You can't do that. Not really. Not reliably. There have been precious few people in the world, over the entire history of computing, who have been able to do it reliably. Steve Jobs was one of them. We don't have a Steve Jobs here. I'm sorry, but we don't."

"And also don't get me wrong about Google+. They're far from the only offenders. This is a cultural thing. What we have going on internally is basically a war, with the underdog minority Platformers fighting a more or less losing battle against the Mighty Funded Confident Producters."

"It's everyone. The problem is that we're a Product Company through and through. We built a successful product with broad appeal -- our search, that is -- and that wild success has biased us."

"I'm not saying it's too late for us, but the longer we wait, the closer we get to being Too Late."

TIL - Dark Side of the Rainbow

2011-08-08T13:27:00.004+01:00

Dark Side of the Rainbow (also known as Dark Side of Oz or The Wizard of Floyd) refers to the pairing of the 1973 Pink Floyd music album The Dark Side of the Moon with the visual portion of the 1939 film The Wizard of Oz. This produces moments where the film and the album appear to correspond with each other.

...

Band members and others involved in the making of the album state that any relationship between the two works of art is merely a coincidence.

Link para video

Link para wikipedia

2011-07-22T09:20:00.004+01:00

Já existe um novo market para o Android.

Destaca-se a navegação horizontal, e layout completamente novo.

Para os ansiosos, visto por agora apenas estar dísponivel para DEVs, é só fazer o download do apk aqui.

enjoy !