michaeljswart.com Report : Visit Site

Technical data of the michaeljswart.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host michaeljswart.com. Currently, hosted in United States and its service provider is Mosso Hosting .

cheatography.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

michael j. swart rss feed email me about me july 9, 2018 the bare minimum you need to know to work with git filed under: technical articles — michael j. swart @ 9:00 am i don’t like using git for source control. it’s the worst source control system (except for all the others). my biggest beef is that many of the commands are unintuitive. look how tricky some of these common use cases can be: top voted stackoverflow questions tagged git . the top 3 questions have over ten thousand votes! this shows a mismatch between how people want to use git and how git is designed to be used. i want to show the set of commands that i use most. these commands cover 95% of my use of git. initial setup one-time tasks include downloading git and signing up for github or bitbucket . my team uses github, but yours might use gitlab, bitbucket or something else. here’s my typical workflow. say i want to work on some files in a project on a remote server: clone a repository my first step is to find the repository for the project. assuming i’m not starting a project from scratch, i find and copy the location of the repository from a site like github or bitbucket. so the clone command looks like this: git clone https://github.com/someproject/somerepo.git git clone https://github.com/someproject/somerepo.git this downloads all the files so i have my own copy to work with. create a branch next i create a branch. branches are “alternate timelines” for a repository. the real timeline or branch is called master. one branch can be checked out at a time, so after i create a branch, i check out that branch. in the diagram, i’ve indicated the checkout branch in bold. i like to immediately push that branch back to the remote server. i can always refer to the remote server as “origin”. all this is done with these commands: git branch mybranch git checkout mybranch git push -u origin mybranch git branch mybranch git checkout mybranch git push -u origin mybranch change stuff now it’s time to make changes. this has nothing to do with git but it’s part of my workflow. in my example here i’m adding a file b.txt . stage changes these changes aren’t part of the branch yet though! if i want them to be part of the branch. i have to commit my changes. that’s done in two parts. the first part is to specify the changes i want to commit. that’s called staging and it’s done with git add . i almost always want to commit everything, so the command becomes: git add * git add * commit changes the second part is to actually commit the files to the branch with a commit message: git commit -m "my commit message" git commit -m "my commit message" push changes i’m happy with the changes i made to my branch so i want to share them with the rest of the world starting with the remote server. git push origin mybranch git push origin mybranch create a pull request and merge to master in fact i’m so happy with these changes, i want to include them in master, the real timeline. but not so fast! this is where collaboration and teamwork become important. i create a pull request and then if i get the approval of my teammates, i can merge. it sounds like a chore, but luckily i don’t have to memorize any git commands for this step because of sites like github or bitbucket. they have a really nice web site and ui where teams can discuss changes before approving them. once the changes are approved and merged, master now has the changes. once it’s merged. just to complete the circle, i can pull the results of the merge back to my own computer with a pull git pull git checkout master git pull git checkout master other use cases where am i? to find out where i am in my workflow, i like to use: git status git status this one command can tell me what branch i’m on. whether there are changes that can be pushed or pulled. what files have changed and what changes are staged. merge conflicts with small frequent changes, merge conflicts become rare. but they still happen. merge conflicts are a pain in the neck and to this day i usually end up googling “resolving git merge conflicts”. can’t this be easier? there are so many programs and utilities available whose only purpose is to make this stuff easier. but they don’t. they make some steps easy, and some steps impossible. whenever i really screw things up, i delete everything and start from scratch at the cloning step. i find i have to do that more often when i use a tool that was supposed to make my life easier. one exception the only exception to this rule is visual studio code . it’s a real treat to use. i love it. maybe you like the command line. maybe you have a favorite “git-helper” application. no matter how you use git, in every case, you still have to understand the workflow you’re using and that’s what i’ve tried to describe here. where to next if you want to really get good at this stuff. i recently learned of a great online resource (thanks cressa!) at https://learngitbranching.js.org/ . it’s a great interactive site that teaches more about branching. you will very quickly learn more than the bare minimum required. i recommend it. -- comments (3) july 3, 2018 shifting gears in 2018 filed under: sqlserverpedia syndication — michael j. swart @ 9:00 am i wanted you to know about some changes coming to this blog. i’m shifting the focus from sql server to other technologies. specifically, i’m going to explore and begin writing more about modern software development including things that have been labeled devops or site reliability engineering. i’ve been looking for a new challenge for a while and i have an opportunity to do that by following the direction set by my company a few years ago. my company is embracing the public cloud for its price, its flexibility and its promise of scalability. which public cloud? as awesome as azure is, we’re going all-in aws. for me, this means new lessons to learn and new things to write about. my audience my target audience for the new topics include people searching google who want to find the answers to the same questions i learned recently. the developer who is super-familiar with the microsoft stack (aka yours truly) but who wants to branch out into a new stack. i hope that still includes you. blogging as a student i have no problems blogging as a learner. just look at kenneth fisher ( @sqlstudent144 ) and pinal dave ( @sqlauthority ). they both began their blogs from the point of view of a learner. that word “student” is even there in kenneth’s handle. and pinal’s site is about his “journey to authority”, another colorful expression for learning. and they’ve done it. they’ve both successfully gained a reputation as an authority in their field. my topics i’ve often straddled the line between a developer and a dba. i know a little bit about what it takes to keep sql server happy and healthy. i look forward to expanding my “site reliability engineering” skills into new areas. so for the next few weeks, i’ll start by blogging about the tools i use and what it takes to get started on a simple project. it’s about the arrows software architecture is often over-simplified as drawing boxes and arrows describing things (the boxes) and how they’re organized or how they communicate with each other (the arrows). one thing i’ve noticed is that programs used to be the hard part. the classes, the objects, the algorithms. now it seems to me, that the arrows are the hard part. deployment, security, automation and all that network stuff can’t be deferred to another team. the arrows are the hard part i may specialize in something in the future, but for now i have no shortage of topics. i’ve been tracking my google search history: here’s what that looks like for the past two weeks: youtube getting started terraform aws circleci tf examples getting started terraform tf examples getting started terraform deploy to aws specify descending in primary key codepipeline aws code deploy dynamodb ttl attribute lambda to dynamodb tutorial javascript add 4 months add

URL analysis for michaeljswart.com

http://michaeljswart.com/?page_id=494
http://michaeljswart.com/2018/01/100-percent-online-deployments-keep-changes-oltp-friendly/
http://michaeljswart.com/2014/09/take-care-when-scripting-batches/
http://michaeljswart.com/category/miscelleaneous-sql/
http://michaeljswart.com/2018/03/t-sql-options-for-comparing-distinctness/#comments
http://michaeljswart.com/2018/01/100-online-deployments/
http://michaeljswart.com/2018/07/shifting-gears-in-2018/
http://michaeljswart.com/category/technical-articles/
http://michaeljswart.com/feed/
http://michaeljswart.com/2018/01/sha1-collisions-in-sql-server/
http://michaeljswart.com/2018/03/failed-to-initialize-deadlock-control-key-cannot-be-null-when-viewing-deadlock-graphs/#comments
http://michaeljswart.com/2018/01/100-percent-online-deployments-blue-green-details/
http://michaeljswart.com/2018/03/failed-to-initialize-deadlock-control-key-cannot-be-null-when-viewing-deadlock-graphs/
http://michaeljswart.com/category/tongue-in-cheek/
http://michaeljswart.com/2018/07/the-bare-minimum-you-need-to-know-to-work-with-git/
theregister.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: MICHAELJSWART.COM
Registry Domain ID: 1575344561_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2017-10-12T12:28:12Z
Creation Date: 2009-11-11T14:40:32Z
Registry Expiry Date: 2019-11-11T14:40:32Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: DNS1.STABLETRANSIT.COM
Name Server: DNS2.STABLETRANSIT.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-09-19T14:03:52Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR GoDaddy.com, LLC

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =michaeljswart.com

  PORT 43

  TYPE domain

DOMAIN

  NAME michaeljswart.com

  CHANGED 2017-10-12

  CREATED 2009-11-11

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientRenewProhibited https://icann.org/epp#clientRenewProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  DNS1.STABLETRANSIT.COM 69.20.95.4

  DNS2.STABLETRANSIT.COM 65.61.188.4

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .