Nuget

Recently I had to create a nuget and push it

Luckily things worked smoother than I expected

  1. Downloaded nuget.exe

  2. Created “nuget” folder with

  • “build” folder. –> this in turn contained 2 things
    • targets file
    • “intenttriggering” folder containing the model files
  • nuspec file

nuget pack

D:\nuget>C:\Users\agoswami\Downloads\nuget.exe pack NLU.IntentTriggering.Model.nuspec
Attempting to build package from ‘NLU.IntentTriggering.Model.nuspec’.
Successfully created package ‘D:\nuget\NLU.IntentTriggering.Model.1.2.0.nupkg’.

nuget push –> luckily it worked smoothly. dunno how

D:\nuget>C:\Users\agoswami\Downloads\nuget.exe push -Source “TScience.NLU” -ApiKey az NLU.IntentTriggering.Model.1.2.0.nupkg

Code Collapse

I find it quite useful. Want to note it down since i use different IDEs for C# and Python

(try out these combos — i always get what i want by trial and error)

VS2019

  • Ctrl followed by MM (repeat to undo)
  • Ctrl followed by ML (repeat to undo)
  • Ctrl followed by MO (repeat to undo)

PyCharm

  • Ctrl followed by + (- to undo)
  • Ctrl, Shift followed by + (- to undo)
  • Ctrl, Alt followed by + (- to undo)

Ubuntu Terminal Smarts

I think using the Ubuntu Terminal in a smart way is crucial for day-to-day productivity.

I came across this nice link where several tricks are listed down and explained nicely.

https://help.ubuntu.com/community/UsingTheTerminal

Note: The consistent Copy-Paste mechanism  I have found working across Unity terminal, Xfce terminal, unity gvim, xfce gvim etc is  using:

  • Control + Insert : to copy
    • this is also same as ‘copy on select’ i.e. just select the text and it will be copied automatically.
  • Shift + Insert : to paste

Check it out!

Java, Maven, Scala, SBT Concepts

Am toe dipping into maven. Trying to make sense of how maven fits in with  IDE, command line maven, POM files blah blah etc.

tips:

  • intellij will have default support within the IDE for both Maven and SBT.  So as long as we are not using mvn and sbt  from the command line we should be good.

java fundamental concepts:

maven:

base scala in intellij:

scala with SBT:

5 Skills.

One person recently pointed out to me that a strong ML team needs 5 skills.

I was glad he pointed it out so clearly. Sometimes its easy to know things, but hearing it from someone else and crystallizing it helps a lot.

The 5 skills (in no particular order) are:

  1. Research
  2. Engineering
  3. Data Science
  4. Program Management
  5. Systems Architecture.

The other interesting thing he mentioned which I really liked was about prioritization. Nowadays there is so much of cool technology out there that it becomes super important to do prioritization. This would give one a strong sense of direction.

Tool Shortcuts

As I keep using different tools, it has become necessary to note down the different shortcuts across the tools.

Spyder:

  • (control + 1)  : comment/uncomment lines
  • (control + d)  : delete lines
  • is there a way to cut lines in spyder ?  (besides the standard select and cut technique)

Notepad++

  • (control + q)  : comment/uncomment lines for different file formats e.g. .sh / .bat

GVim

  • yy  : cut lines
  • pp : paste lines

VS:

  • (control + x) : cut lines
  • (control + kd) : format correction

IntelliJ IDEA:

  • (alt + F12) : command prompt
  • (control + alt + l) : format correction
  • (control + d) : move back from sbt’s scala console (‘sbt’ -> ‘console’) back to the sbt console.
  • (control + ‘/’) : comment / uncomment

 

 

References:

 

 

Git : Undo commits, Viewing Unpushed Git Commits

Tips:

[1] First note that there is a difference between ‘revert’ and ‘reset’

 

[2]  Undoing a ‘git add’ before doing a ‘git commit’

Note:  For this scenario, most of the above links are recommending doing a ‘git reset’. There is a difference between a ‘soft’ reset and a ‘hard’ reset.

 

[3] Recently I had to undo a commit I had made into my local git repo. I was under the impression that reverting commits in Git is a big hassle. To my surprise, it didn’t prove to be too much of a pain. These are things I had to do basically:

  • couple of git reset --soft HEAD~ commands (because there was stuff I had pulled into my repo after commiting)
  • couple of   git checkout —  <file> commands to undo my inadvertent changes.

That was it!  I got my repo back to sanity.

 

[4]  Another import task is to view unpushed git commits. this is an important thing to do, especially before making commits into a remote branch.

 

References: