archive-ro.com » RO » T » TEKKIE.RO

Total: 200

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Technical stuff
    g local git archive format zip HEAD Desktop work in progress zip Then I uploaded the archive on the testing machine with g local scp v Desktop work in progress zip deployer 123 x x x Next step was to unpack it there deployer remote unzip work in progress zip I then installed its dependencies deployer remote npm install Starting the process was easy as pie deployer remote npm run dev I got myself a solid process consisting of just 4 steps which can easily be the starting point of the production deployment when I get to that point For different use cases where the versioning information is also needed I find git bundle to be more appropriate in Processes 271 Words 1 Comment Best way to learn is to look at the best Most people I ve worked with don t like to learn in an ordered manner from a textbook They enjoy experimentation more than anything because it allows them to see how things are moving when change is applied And because I ve been working with React lately I thought it would be a good idea to see an isomorphic application at its best so I started to dig Facebook s desktop implementation After overcoming the disappointment that they didn t implement it universally I did discover some gems in their frontend code To be continued in Funny 90 Words Comment List all globally installed npm modules Today I needed to have a look at all the npm modules that were installed globally on my machine I found that npm has a list command that does just that But in order to only see the modules and not all their dependencies I needed to specify a depth value of 0 npm list g depth 0 usr local lib ampersand 3 0 5 bower 1 4 1 brunch 1 8 3 grunt cli 0 1 13 gulp 3 9 0 http server 0 8 0 javascripting 2 0 3 mocha 2 3 0 n 2 0 1 node gyp 2 0 2 npm 2 11 3 phantomas 1 11 0 react native cli 0 1 4 react tools 0 13 3 supervisor 0 7 1 The g switch is the same one that I used when globally installing each module If the name of some package doesn t immediately ring a bell replacing list with ll can help npm ll g depth 0 usr local lib ampersand 3 0 5 CLI tool for generating single page apps a la http humanjavascript com git https github com ampersandjs ampersand git https github com ampersandjs ampersand bower 1 4 1 The browser package manager git https github com bower bower git http bower io brunch 1 8 3 A lightweight approach to building HTML5 applications with emphasis on elegance and simplicity git https github com brunch brunch git http brunch io grunt cli 0 1 13 The grunt command line interface git github com gruntjs grunt cli git http gruntjs

    Original URL path: http://www.tekkie.ro/ (2016-05-01)
    Open archived version from archive


  • About | Technical stuff
    strongly believe that being able to wear several technical hats is what makes a great all round developer and a reliable technical manager that can be trusted to deliver on time and at high standards of quality I enjoy mostly life in the backend side of the process where the meat and sauce is because I believe that the more stable scalable and resilient the software is the more value it can deliver to its end users However I value the frontend work just as much as the ease of use is equally important to being able to get the job done Usability is a key part of software development practices that I follow and that translates to simpler better products Since 2011 my consulting and development services are delivered using the Tekkie Consulting company We bring new life to old software making sure all the existing functionality stays in place easing the process of adding new functionality and elliminating bugs After conducting an audit we deliver you a detailed insight of your current situation with clear recommendations on what can be improved and recommendations of steps to be taken After having successfully delivered several large scale products on tight timeframes I can help you with targeted advice and hands on help on product creation development and maintenance without any compromise to the quality For more detailed insight on my professional path please consult Georgiana Gligor s LinkedIn profile Share this Click to share on Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to

    Original URL path: http://www.tekkie.ro/about/ (2016-05-01)
    Open archived version from archive

  • Contact | Technical stuff
    in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Tags Agile Android Apache books browser cloud computing code conventions Computer setup development environment Drupal 7 Facebook Firefox fun time git GitHub Google IDE install JavaScript Linux Mac Methodology mobile News node js online application online tools OSX OS X personal skills PHP PHPUnit presentation quickies Scrum Sebastian Bergmann

    Original URL path: http://www.tekkie.ro/contact/ (2016-05-01)
    Open archived version from archive

  • Online web resources | Technical stuff
    Software development quickies Online SQL instant formatter Tekkie blogs RO Big Lazy SysAdmin RO Blogosfera românească IT RO CNET ro RO Ştefan Poşchină RO Ionut Staicu EN Ref bijstere spor EN Coding Horror Web development Julien Lecomte Tony Marston you gotfoo org Share this Click to share on Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Join the discussion Cancel Reply Join the discussion Comment Name Email Website Tags Agile Android Apache books browser cloud computing code conventions Computer setup development environment Drupal 7 Facebook Firefox fun time git GitHub Google IDE install JavaScript Linux Mac Methodology mobile News node js online application online tools OSX OS X personal skills PHP PHPUnit presentation quickies Scrum Sebastian Bergmann Skype Software development processes symfony2 tekkies testing Ubuntu Web development Wordpress Yahoo Categories Blogging 3 CMS 2 Computer setup 17 Funny 7 Mac OSX 5 Methodology 11 Mobile development

    Original URL path: http://www.tekkie.ro/resources/ (2016-05-01)
    Open archived version from archive

  • Remove local git branches no longer in remote repository | Technical stuff
    stackoverflow com questions 4040717 git remote prune didnt show as many pruned branches as i expected http stackoverflow com questions 20106712 what are the differences between git remote prune git prune git fetch prune http stackoverflow com questions 2688251 what is the difference between git fetch origin and git remote update origin Share this Click to share on Twitter Opens in new window Click to share on Facebook Opens in

    Original URL path: http://www.tekkie.ro/revision-control/remove-local-git-branches-no-longer-in-remote-repository/ (2016-05-01)
    Open archived version from archive

  • Revision control | Technical stuff
    will eventually want to merge it into To prepare the ground for our team we will open a AG 0001 initial setup branch off master This is the place to add initial gitignore rules define the basic coding standards etc git checkout master start from the master branch git checkout b origin AG 0001 initial setup relevant commits in between git push origin AG 0001 initial setup publish our work for the teammates benefit Rule Merge Upwards Always commit your fixes to the oldest supported branch that require them Then periodically merge the integration branches upwards into each other The AG 0001 initial setup is a few commits ahead You can have a quicklook at them by executing git log pretty oneline 9cf571c1c1225a5fecf61c43981048fb16193860 setup gitignore rules 3c1fef41a9ca5d1b24f767404f9bfd52affab90c naming convention for short lived branches 0c1fe345edbebde03f217e7c67d5f67626f2ca7b explain long term branches Assuming this would be all we want to do on the initial setup branch we want to merge our branch upwards What is our destination branch in this case Since there is no release yet we are targetting the next release so the master branch Let s put on our packagist hat for a second How will we know what went into a release and what didn t if we grab all those 3 commits above individually Fortunately there s an easy way of assembling them together as one single entity in the integration branch known as squashing 2 it is an extremely useful method to maintain a clean commit history git merge squash AG 0001 initial setup git commit v git push origin master The result can be viewed online with the mention that I have left the squash message untouched specifically for the reader to get a feel of the defaults At this point let s remove the feature branch as we are done with it git push origin delete AG 0001 initial setup The maintainers of other topic branches are now able and should grab all changes in the integration branches early and often in order to avoid solving complex conflicts later Prepare our first release We have reached an important milestone our initial setup is in fact valid so as a team we decide that our work so far should be refered to as release 0 0 1 Check that master is a superset of maint by executing git log master maint and validating there are no commits found We can now tag the release git tag m initial setup 0 0 1 0 0 1 master git push tags Once the release is done from a coding perspective we can now hand it over to the packagist The next step is to tidy up the maintenance branches to reflect the new state of facts Since maint reflects the previous release it would be a good time to spin off a new maint FORMER RELEASE to be able to supply quick fixes there In our case this is not needed as we don t have a previous release

    Original URL path: http://www.tekkie.ro/category/revision-control/ (2016-05-01)
    Open archived version from archive

  • Reactive manifesto | Technical stuff
    communication Share this Click to share on Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related

    Original URL path: http://www.tekkie.ro/processes/the-reactive-manifesto/ (2016-05-01)
    Open archived version from archive

  • Processes | Technical stuff
    into To prepare the ground for our team we will open a AG 0001 initial setup branch off master This is the place to add initial gitignore rules define the basic coding standards etc git checkout master start from the master branch git checkout b origin AG 0001 initial setup relevant commits in between git push origin AG 0001 initial setup publish our work for the teammates benefit Rule Merge Upwards Always commit your fixes to the oldest supported branch that require them Then periodically merge the integration branches upwards into each other The AG 0001 initial setup is a few commits ahead You can have a quicklook at them by executing git log pretty oneline 9cf571c1c1225a5fecf61c43981048fb16193860 setup gitignore rules 3c1fef41a9ca5d1b24f767404f9bfd52affab90c naming convention for short lived branches 0c1fe345edbebde03f217e7c67d5f67626f2ca7b explain long term branches Assuming this would be all we want to do on the initial setup branch we want to merge our branch upwards What is our destination branch in this case Since there is no release yet we are targetting the next release so the master branch Let s put on our packagist hat for a second How will we know what went into a release and what didn t if we grab all those 3 commits above individually Fortunately there s an easy way of assembling them together as one single entity in the integration branch known as squashing 2 it is an extremely useful method to maintain a clean commit history git merge squash AG 0001 initial setup git commit v git push origin master The result can be viewed online with the mention that I have left the squash message untouched specifically for the reader to get a feel of the defaults At this point let s remove the feature branch as we are done with it git push origin delete AG 0001 initial setup The maintainers of other topic branches are now able and should grab all changes in the integration branches early and often in order to avoid solving complex conflicts later Prepare our first release We have reached an important milestone our initial setup is in fact valid so as a team we decide that our work so far should be refered to as release 0 0 1 Check that master is a superset of maint by executing git log master maint and validating there are no commits found We can now tag the release git tag m initial setup 0 0 1 0 0 1 master git push tags Once the release is done from a coding perspective we can now hand it over to the packagist The next step is to tidy up the maintenance branches to reflect the new state of facts Since maint reflects the previous release it would be a good time to spin off a new maint FORMER RELEASE to be able to supply quick fixes there In our case this is not needed as we don t have a previous release to refer to What is needed

    Original URL path: http://www.tekkie.ro/category/processes/ (2016-05-01)
    Open archived version from archive