[RO] Normele de venit pe 2012
S-au publicat normele de venit pe 2012. In momentul asta mai sunt cateva judete pentru care nu s-au publicat inca, dar probabil ca lista va fi completata zilele astea si cu restul.
Dupa cum probabil ati auzit pana acum, marea schimbare in ce priveste normele de venit pe anul acesta e ca s-au scos aproape toate normele pentru CAEN-urile din IT, mai putin 6202 (activitati de consultanta in tehnologia informatiei) si 6203 (activitati de gestiune si exploatare a mijloacelor de calcul). Asta inseamna ca cei care au orice alt CAEN in afara de cele doua au de acum doua optiuni:
- Trecerea la sistemul real de impozitare. In acest caz va trebui sa mergeti sa depuneti declaratia de venituri anticipate pe anul acesta. De asemenea, inseamna tinut contabilitate in partida simpla, completat registrul jurnal de incasari si plati, etc.
- Schimbarea CAEN-ului actual in unul din cele doua de mai sus. Aici ar fi de notat faptul ca de acum orice nou contract sa fie facut pe noua activitate, ceea ce ar putea pune probleme unora. Spre exemplu, ma gandesc ca un contract de consultanta este posibil sa nu convina oricarui client, pentru ca practic nu ar mai exista obligativitatea livrarii de cod sursa sau alte materiale.
Schimbarea de CAEN se face la ONRC. Cel mai bine sunati la sediul ONRC din judetul vostru pentru a intreba exact ce acte va trebuie pentru schimbarea CAEN-ului, cat dureaza, etc.
PS: daca cumva stirea ca s-au scos normele de venit in IT te scandalizeaza, am scris si pentru tine ceva.
Export new and changed files only using TortoiseSVN
I was forced to do some work under Windows these days, and when it came time to deploy the files I changed to the FTP server, I had to figure out how to use TortoiseSVN in order to only export the files that have been created or updated since the last deployment. As it turns out, it’s pretty easy:
- First, bring up the TortoiseSVN menu by right clicking on your working copy.
- From the menu, choose “Show Log”.
- Holding down the CTRL key, select the two revisions you want to compare (like this).
- Right click on one of the two revisions and select theĀ Compare revisions option.
- In the file list that appears, select all the entries (CTRL+A), right click on them and select the Export selection to… option. The files will be exported with the right directory structure, so all you have to do is upload them to the server.
Unfortunately, this method only works for new files or files that have been changed. The files that have been removed will have to be manually deleted from the server too.
There are, of course, tons of better tools to deploy files to FTP servers that can also handle removed files (Springloops is my current favorite), but this is quick and easy way to do it when you don’t have a better solution on hand.
Dynamically resizing the Shadowbox.js modal window
Shadowbox.js is an excellent modal window component capable of handling everything from iFrames to Flash videos to image galleries. However, and odd as it seems, the out-of-the-box solution doesn’t have a resize() method with which to resize the modal window via JavaScript. The reason you might want to manually resize the modal window is in case the content inside changes, for example in the case of IFrames. Fortunately, implementing such a method is quite easy.
First, download Shadowbox. As of this version, the downloaded files are automatically minified, so in order to be able to properly add the needed code you will have to prettify the code, using a tool such as http://jsbeautifier.org/.
After you have prettified the code, scroll down right after the onWindowResize method, which should look something like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 | k.onWindowResize = function () { if (!P) { return } I(); var K = g.player, S = R(K.height, K.width); t(S.width, S.left); E(S.innerHeight, S.top); if (K.onWindowResize) { K.onWindowResize() } }; |
The reason I am including the onWindowResize method is because, the code being packed, the variable names might change in subsequent versions of Shadowbox, so you will have to take a look at an existing function. Now, right below the onWindowResize method, add the following code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | k.dynamicResize = function (w, h) { if (!P) { return } I(); g.player.width = w; g.player.height = h; var K = g.player, S = R(K.height, K.width); t(S.width, S.left); E(S.innerHeight, S.top); if (K.onWindowResize) { K.onWindowResize() } }; |
Notice that there are only three lines that differ between the two methods. After adding this method (and perhaps minifying the code again), you can easily resize the modal like this:
1 | Shadowbox.skin.dynamicResize(600, 400); |
Or, if you want to do it from inside the iframe loaded within the modal:
1 | window.parent.Shadowbox.skin.dynamicResize(600, 400); |
Note that this method does not resize the window beyond the viewport dimensions. It will still be scaled down if it exceeds the viewport’s width or height.
The Pomodoro Technique – 6 months later
6 months ago I decided to try out the Pomodoro Technique, so it’s about time to document my findings. First of all, I cannot image going back to the way I used to work before. It seems too chaotic and disorganized now that I got used to the mechanical precision of the technique.
Some things I learned:
- As I first suspected, the technique helped me accomplish a larger and more efficient quantity of work than before, with a lot less interruption, and a lot less room for procrastination. Not that you cannot procrastinate, it’s just that it’s more obvious to yourself when you do so. If you try reaching for 12-13 pomodoros on an average day, the days when you only manage to churn out 6 or 8 will stand out like a sore thumb.
- I now think of tasks in terms of the number of pomodoros it takes to complete them, so it gave me an excellent unit of measurement for use in estimating.
- Most of us don’t work in an isolated environment, and it’s sometimes hard not to be interrupted, and I think this problem only grows as the size of your organization increases.
Some tricks I used to adapt the technique to my own needs:
- Starting a new pomodoro is sometimes hard. I now have the habit of leaving a small amount of work not done at the end of a pomodoro, and when the break is over this forces me to jump right in and finish what I started. It’s a lot easier to procrastinate when the code is stable and everything works.
- I try and time my pomodoros with my lunch break. Therefore, I don’t take a larger break until after the 5th or 6th pomodoro, which usually ends just as we are all about to go out for lunch. Otherwise I would take my lunch break after just 2 pomodoros.
- I started using the technique by scribbling the number of pomodoros that passed on a little piece of paper. I have, since then, advanced to using a daily to-do list, and marking each pomodoro on the row of it’s corresponding task. This serves a double purpose as, besides tracking the daily pomodoro count, it helps with the future estimation of similar tasks.
Some of the adjustments I made (particularly the first one) directly contradict the book. I don’t think that’s too bad, because the entire technique’s role is to help me become more productive, and if I found a way to improve on this (for my particular case, of course), I think it’s OK. So go ahead and roll your own, as long as the changes you make boost your productivity. However, I strongly recommend sticking to the instructions in the book for the first few months, and then decide if it works for you out of the box or if it needs tweaks.
One does not simply Walk Into Mordor
I was meaning to start writing about books for some time now, but I also didn’t want to pollute this website with non-technical information so, for those of you that are interested, I will be massacring the English language on my other blog too, Walk Into Mordor.
Happy reading!


Sunt Victor Stanciu, web developer, si scriu despre dezvoltare, standarde, tehnici si tehnologii. (