Do not get too busy in doing hard work, have some scope to look around for the way to incorporate smart work ;-)
Tag creation in GIT using source tree in simple steps :
1. select a commit to be tagged
2. right click and pick tag option
3. Provide tag name (lable)
4. Click add tag and push it to remote
In case if you want to do the same using command prompt / shell the fire below commands
git clone <repo-address>
git tag -l
git checkout <tag-name>
git branch -D master
git checkout -b master
Dear Software Engineers,
Your job is not to write code.
I know. You think you were hired to write code. In fact, your entire interview process centered around how well you could write code. And I’m sure you do it really well.
But it’s not your job.
Your job is to improve our product for our users. If you want to get technical about it, your job is to improve our product for our users in a way that improves the key metrics of the company. But honestly, you don’t always have a lot of control over that second bit. You do, however, have an enormous amount of control over the first bit!
Of course, if you want to do your job well, it does mean that you may have to change some of your current behaviors.
For one thing, you need to make sure that the code you write (writing code is still one of the main things you will do when doing your job, by the way) runs the way it should, even on users’ machines.
Did you know that our users probably don’t have brand new MacBook Airs with giant Thunderbolt monitors set at the highest resolution possible and running the latest version of Chrome? I checked. A lot of them have Internet Explorer on 4 year old laptops, so sometimes things you build don’t work right on their machines. They’re still our users, and it’s still your job to improve the product for them, so please make sure that the code you wrote works in a reasonable number of environments.
In fact, you’re going to need to make sure that the code you wrote runs in production, in general. I don’t really care if your code runs locally. If your code just runs locally, then my only option is to sell your computer so that our users can use our software, and that really doesn’t scale.
So, to avoid that, you need to check your changes in production. Every time. Remember, your job is not just to ship something. It’s to ship something that improves our product for our customers. You can’t know it will do that unless you check that it runs in the way it’s supposed to.
Of course, in order to check your changes in production, you’re going to need to make sure that your code actually gets merged and pushed into production. I mean, you can’t really check your changes in production if you just let them sit unpushed for hours or days. Push your code. Get it into production. Then run it and check it.
This is obviously harder to do if you’re in an environment where you can’t do continuous deployment, but the theory still holds. When your code gets into production, whenever that is, you’re still responsible for it. Make sure that it’s doing what it ought to be doing – which is make the product better for users.
Another thing to remember is that sometimes users do surprising things, which means that it’s not enough just to test that your code works under perfect conditions. You need to make sure that it does something reasonable even in error cases and zero data states and when the user does something you might not expect, like use the back button or make two accounts by mistake.
This is hard. It means you’ll have to spend time thinking about the different things our users might do. But it’s an important part of your job, because it will vastly improve the product for our users if they aren’t constantly finding bugs or edge cases or dead ends.
There’s one more important part to your job. You need to make sure that we can measure whether we’re all doing our jobs well. That means adding metrics and analytics so that we can test the effects of our changes. If you expect the code you are writing to improve user engagement (by improving the user experience in some key way), then you need to have a way to learn whether or not you succeeded. How else will you know if your job is done? Because, as I’ve mentioned, your job isn’t done until you’ve improved the product for our users.
I know what you’re thinking. This will all take so long! I’ll be so much less effective!
This isn’t true. You’ll be far more effective because you will actually be doing your job. If you get hassled for writing less code, that’s a failure of management, and I apologize for it. We need to spend less time demanding that you write features and more time asking you to improve our product for our users. If we’re not doing that, I strongly suggest you ask us to. If we still refuse, you should leave and find an environment that lets you do your job. Which, not to beat a dead horse, is to make the product better for our users.
Please don’t feel like I’m picking on you. You’re not the only one who should be doing this job. It is all of our jobs to make the product better for our users. It is my job as a PM and UX Designer and Manager to understand our users well enough that I can help you know how to improve the product for them. It is the CEO’s job to find a strategy that allows us to make money by improving the product for our users.
No matter what our job titles, our jobs are all the same — to make the product better for our users. Every day. So let’s do that.
Your Product Manager
Dear Engineers, your job is not to write code! – Tweet This
*This post originally appeared on Medium*
Petty cash is a small amount of discretionary funds in the form of cash used for expenditures where it is not sensible to make any disbursement by cheque, because of the inconvenience and costs of writing, signing, and then cashing the cheque.
The most common way of accounting for petty cash expenditures is to use the imprest system. The initial fund would be created by issuing a cheque for the desired amount. An amount of $100 would typically be sufficient for most small business needs as the expenses to be covered are for small amounts. The bookkeeping entry for this initial fund would be to debit Petty Cash and credit bank account.
As expenditures are made, the custodian of the fund will reimburse employees and receive a petty cash voucher with a receipt/invoice attached in return. At any given time, the total of cash on hand plus reimbursed vouchers must equal the original fund.
When the fund gets low, e.g. $20 remaining, the custodian (a bookkeeper or a member of the administration staff) requests a top up and submits the vouchers for reimbursement. Assuming the vouchers add up to $80, an $80 top up cheque is issued and an $80 debit towards office expenses is recorded. Once the cheque is cashed, the custodian again has cash at the original amount of $100.
An XML Validator
To help you check the syntax of your XML files, we have created an XML validator to syntax-check your XML.
Valid XML Documents
A valid XML document is not the same as a well formed XML document.
The first rule, for a valid XML document, is that it must be well formed (see previous paragraph).
The second rule is that a valid XML document must conform to a document type.
Rules that defines legal elements and attributes for XML documents are often called document definitions, or document schemas.
When to Use a Document Definition?
A document definition is the easiest way to provide a reference to the legal elements and attributes of a document.
A document definition also provides a common reference that many users (developers) can share.
A document definition provides a standardization that makes life easier.
When NOT to Use a Document Definition?
XML does not require a document definition.
When you are experimenting with XML, or when you are working with small XML files, creating document definitions may be a waste of time.
If you develop applications, wait until the specification is stable before you add a document definition. Otherwise, your software might stop working because of validation errors.
There are different types of document definitions that can be used with XML:
- The original Document Type Definition (DTD)
- The newer, and XML based, XML Schema