Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Job Interview: Codility Practical

2»

Comments

  • Registered Users, Registered Users 2 Posts: 8,593 ✭✭✭funkey_monkey


    I'm just trying to go throught it and learn off all the commands. We have UI's as well, but they are not very stable and are prone to erroneous output.
    As for not needing a book, I'm not sure about that. There is a multitiude of commands, switches, etc that needs to be known and some of it is not very intuitive.

    I'm also considering on picking up on the OCJP accreditation.


  • Registered Users, Registered Users 2 Posts: 6,236 ✭✭✭Idleater


    I'm just trying to go throught it and learn off all the commands.
    To be honest, with Git, you are as well off learning (and sticking to) the basics for the most part. You sound like you are doing a lot of learning in a broad spectrum of things, so don't be concerned with having to know everything at once.

    Understanding the concept of Remote Origin vs Local Head vs staged files, fetch, merge and push operations will get you a long way.

    There are obviously scenario where you will need to use specific variants of the operations, but if you keep the changes simple and branches up to date, you will not need to leverage them for the most part. At work there is a "cheat sheet" set of 4 steps that deal with the basic day to day: create branch, commit changes, submit for review, rework review comments.

    Basic work flow:
    1) get up to date master
    2) branch
    3) do work and commit locally
    4) push branch to remote to collaborate
    (loop 3,4)

    Push for review
    5) get up to date master
    6) merge branch resolving conflicts
    7) push for review

    rework
    8) commit amend



    Git is complex and the best way to learn is for you or better a colleague to end up in a very messy situation and you dig your way out of it. But all of that requires understanding of how git (and to be honest most other vcs software) works.


  • Registered Users, Registered Users 2 Posts: 8,593 ✭✭✭funkey_monkey


    What way do you all use Git - via the command line or via an interface such as Tortoise?

    Yes - I'm just trying to learn the basics (initial post was misleading) and understand what I'm doing with it. Eclipse allows some commands, but we have found it to be a bit flaky.


  • Registered Users, Registered Users 2 Posts: 6,236 ✭✭✭Idleater


    What way do you all use Git - via the command line or via an interface such as Tortoise?

    Command line for me. I had added the git tools to eclipse but likewise never worked right/consistently for adds/commits/fetches. However I do use it for diff/blame (who wrote this; oh me :o)


  • Registered Users, Registered Users 2 Posts: 8,593 ✭✭✭funkey_monkey


    I appreciate Talisman gave me some recommendations on how to upskill in this post but I've decided to created a new thread to get some wider opinion on how I develop my CPD.

    Things are not going well. I might be overly pessimistic but I need to do something to help move on my skills incase the worst happens.


    http://www.boards.ie/vbulletin/showthread.php?t=2057662320


    As an aside, I'm getting more comfortable with Git. By no means an expert but I've finally understood the architecture behind it and am able to help some other colleagues in a simialr position to myself.


Advertisement