Tampa - around 6 months now

We have been here for around 6 months now.  This time has been filled with some enjoyment but also plenty of difficulties, frustrations and just "stuff".

I wish there were more enjoyable moments right now but I must accept the good with the bad.  

Since we got here we have gone through cataract surgery (both eyes) for my wife, finally gotten the braces for my daughter which we had put off for over a year because we had waffled on moving south for so long.  I think the orthodontics people are still shaking their heads at how often we are in  with her to get wires fixed - she may cause them to revise their "off limits food" list.  

I've still not felt like I could take time to find a Sleep Apnea doctor and dentist.  I had started to try and look into apnea doctors and someone did recommend one.  I have not followed up though.  For a while, I was not able to get to a doctors list on the insurance web site - they still had me associated with my previous employer and couldn't figure out how to fix it.  I think they may have fixed it now (after months) but I haven't tried logging in.  It was extremely frustrating not being able to get to our current medical items.  For a dentist, I just need to figure out where I want to go - near home or work.. I need time to review the places that are nearby.

We still have our leaking travel trailer which we are going to try and sell for whatever we can get but need time to work that out.  We think there is a place that will buy it - have to let that one go a big loss I guess.  We don't have time/cash to fix that right now.

I had to replace the rear brakes on my motorcycle which I had unknowingly ground down to the metal (how I didn't notice sooner I don't know - guess I don't press them hard enough normally).  

A Toyota dealer says our front brakes are ready for replacement (although a different dealer later didn't comment).  I've got the rotors and pads just in case I find we need them right now. We still have a rattle around the sunroof in the Toyota - just no time to get it looked at yet.  Wife keeps laughing and telling me it is a nut that a squirrel stored - and is still glaring at me whenever I take the car.

On a plus note, we now have a house - and a nice one at that.  On the downside, there is more work to do to it than was revealed by the home inspection and that is frustrating.  We also are sort of stuck between between homes - family at the apartment and me at the house for most of the week (having together 2-3 days of work week) and then everyone at the house on weekends.  We took the travel trailer mattresses to the house so we had something to sleep on.  It is painful at times for me - I'm starting to try and get some back exercises going again - it is starting to help but slow.  

Regarding the house, we had to replace the main breaker the first week - we only had power to half the house (1 leg of the 240v wasn't working) and it left the big appliances either non-functional or partially functional.  I learned one day that cold showers are still not enjoyable.  I am thankful we have full electricity again.

The wife of the previous owners had some medical issues and we are slowly figuring out why some things were done the way they were.  We are slowly sorting out some of those things and updating the easy stuff.  I was sad to hear that once the prior owners moved out the wife went straight into a nursing home. I do try and pray for the family.

The washer and dryer didn't convey with the house so we went  out and got some new ones - includes some features we didn't have before like the "steam" functions. The problem showed up though during the first use of the dryer though.  It was putting out codes regarding "airflow" being a problem.  I, being somewhat handy, figured it must just be a clogged vent.  It was funny that I was outside at around midnight one night with a flashlight trying to find the outside vent - without luck.  The next day, my wife and family pointed out that it was a plastic pipe that comes out of the ground about 12-18 " from the outside exterior wall (!??!??).  Anyways, to make a long story shorter, it wasn't clogged -  the new "smart" dryers monitor airflow and will warn you or even stop if it thinks there is an "excessive" restriction.  In our case, the way it is plumbed under the concrete slab and out with around 4 90 degree turns ends up at around 20 feet of length without the dryer to wall connection which is longer than desired because we wanted the doors to open in a way that made loading easy. So we are at the moment stuck running the dryer into a "in the house" water based lint trap and leaving some doors open around the wash room to let the heat and moisture out (hope we don't draw lizards in - I know who will have to chase them). The long term solution will probably be a vent extender and possible a reroute of the vent through the attic and out a wall - not really in the budget right now.

We have some leaky drains in the master bath to fix up.  Those are on my list of things to do sooner and later so we don't get a bigger mess.

There are a number of light dimmers and electric outlets that need replacing - nothing too bad but time consuming and complicated because the house is wired "interestingly".  It was mildly noticeable when reviewing the breaker box - a number of items marked "lights" but no room indicated and things like that.  There were not nearly as many breakers in use as to what I would expect either. What we know now is that there are some items on the same circuit as a major appliance - like maybe some wall outlets and the stove.  The shed was wired off of a heat pump circuit and even that wiring I am not sure I understood one aspect of what they did.  This is going to take time to sort out.

Then there is the shed.  We knew there was some rot but not the extent - when we had looked before it was full of stuff so there wasn't much access.  On move in, we found holes in the floor and the ceiling was  a total loss.  My parents are awesome and want to help by replacing the shed.  We started tearing it down and found that they had tacked up new wood over exterior rot (some years ago probably - not for the sale).  There were plenty of ants and palmetto bugs using it as a home.  This is going to take some time to sort out too.

I've not ventured into the attic yet.  Hoping that doesn't show more issues.

We still have a number of items to bring down from VA.  I hoping we can make a trip soon - that will provide one real bed for the house at least along with a bunch of storage stuff and additional workbench for the garage.  Not sure I need the additional workbench but I may have some specific uses.

On top of all this, my kids are/were struggling to get caught up in their school work since they started late with some Florida virtual school classes.  They fell farther behind in those and I don't know whether it is a bit of a self-direction issue or just issues related to never doing work mostly online. I have not been overly encouraging to them and I hope they forgive me for that.  I should say that I am proud of my son for doing  *extremely* well on his SATs.  I am also very proud of my daughter for how well she is doing with violin lessons (and guitar as well).  They are both so very capable of doing just about anything but they need my encouragement more than harshness sometimes.  I am hard on them - I think they should always do things to the best of their abilities.

At this very moment, we still have not sold our house in VA as well.  It wasn't really a problem for a few months - it was a "safety net" if we just couldn't deal with it down here.  I think we are enjoying it to some degree and it is now time to get the house off our books.  That has been a huge anchor around our necks for a while.  I think we have an offer now and plan to sign a contract shortly - hoping this works out finally.  Still not getting what I had hoped for but it is a little higher than a previous offer someone made. I do want to give a praise that it looks like it is going to sell though!

I must admit that I have been handling the stress of the issues pretty poorly lately/still.  I'm very embarrassed and angry with myself at the moment.  I am thankful for Jesus forgiveness though. I continue to pray for strength and perseverance.  I continue to hope that once we get totally out of the apartment and into the house along with finishing up this years schooling - we can work on "renewing the family and individually" for a lack of better words.  Separation of family is never a good thing - I am understanding that clearly now.  That applies to both our family "unit" and church family as well.  There is strength in togetherness both those areas.   

Fortunately, the new church we visited twice now seems like a good fit.  I am hopeful that we can quickly make some additional friends (still massively miss friends from VA and wish they were closer).  I really need more support right now - still feeling personally responsible for many issues. I really need to spend time in bible reading and quiet time.  So many things keep wedging their way into that time.

Scott

Cry out to Jesus

Cry out to Jesus when you are tired. Why cry out to Jesus? Because he loves you.

Cry out to him when you wake up gasping for breath and heart pounding. Because he loves me. 

Cry out when you feel like everything you do is a mistake.  Because he cares.

Cry out when you are sad and disappointed with others.   Because he wants your burden

Cry out when you are disappointed in yourself.   Because he wants my burdens. 

Cry out when you are alone and scared. Cry out when you are in pain. Because he listens.

This is not crying out into emptiness; this is shouting to myself and others to know and remember that Jesus is the answer and he does respond to our cries.  All that is needed is to hold him dearer than all else.

I lay my head down again tonight with final pleas that he help me to love him the way I should and to show my family how to love him more.

Scott

Angular 2 and ecosystem: dislikes?

Ok, so Angular 2 generates a good amount of attention with lots of great things touted about it.  That is fine but what matters to me is whether it is like the medications advertised on TV - "Cures you <insert condition here>" but in tiny print has "side effects of nausea, vomiting and sometimes death".  Angular is still pretty new to me - typically I work mostly on back-end Java development. I'm not doing new Angular coding right this second but for a couple months I have been doing automated builds for Angular 2 projects and just started to work on converting some Angular 2 projects from Gulp based to mainly just NPM with Webpack2 which is resulting in some coding along the way.

Ok, so let me start off by saying that I don't think Angular 2 will have 'death' as a side effect.  Maybe headaches though.

My list of issues - some not directly Angular issues but related in various ways through tooling or general ecosystem.

• Documentation is poor.  I find myself asking questions like 'what about this or that' and official docs for what seems like most stuff in the NPN repository don't have the answers.  I waste too much time looking for answers at Stackoverflow or elsewhere for usage/API questions rather than working on the actual functionality. This isn't an Angular (2) specific issue but they didn't improve things.
• Searching for Angular 2 documentation, etc results in many links to Angular 1 stuff or to items which a beginner can't easily identify as Angular 1 or 2.  Just "Angular" everywhere. I wish that those blogging or writing examples, documentation, etc would consistently include a version in the content or at least a date when something was written so there is a better chance of figuring it out.  I'll admit that I don't always think about this aspect either until I'm on the receiving end of new technology but when breaking changes are very common this is more important.
• Seed projects drive me a bit crazy when they use beta software.  As of the date I am writing this (3/5/17), what appears to be a common seed project here is using webpack 2.1.0-beta.27. I have never worked where we would rely on beta software - especially well after non-beta software was available. I spent some time already looking into the non-beta webpack 2 and I see how the particular seed we used pushed the developers into using the beta initially.  I just wish that they would put time into converting to non-beta software even if it will take some effort.  It seems odd and unwise to expect further beta updates after a stable release so good luck with bug fixes or security issues. And just so no one thinks I am talking about just Webpack2, in this instance rxjs 5.0.0-beta.12 is also in this seed.
• NPM is so slow I feel like my hair will be totally grey before most 'npm install' processes finish. I did see there is at least one attempt at an alternative (Yarn) but I had problems with an app with just a moderate number of dependencies and it was still pretty slow for me. By version # terms, Yarn is still really young and I hope it makes major improvements. 
• NPM version? I've yet to see any nice documentation stating when/where particular NPM versions should be used. I've read some information listing some of the differences but nothing really saying 'hey, version 4 is where you should be now because..' or making it clear what the impact is of using various versions in different contexts.  Is it s difference of works versus not or simply efficiency differences? Does it depend on other considerations?
• Many 3rd party libraries are not using semantic versioning yet.  If people are creating apps/libs and passing them on to you for further work before deploying to production many times the build is dysfunctional by time I even try the build process. To many packages making breaking changes with no way of knowing by the version number. An example issue with ng2-bootstrap can be viewed here.  I think the main contributor to the issue is the extensive/default use of "^' and '~' to modify the process of selecting compatible dependency versions.  The default should be to NOT use them(^ or ~) in my opinion. It is a huge time waster trying to get a build working which was just handed to you that won't build because 'some' component got upgraded to an incompatible version which must be tracked down. [edit 2017/04/20] You have probably heard of Perl being referred to as a "write once" language - I sometimes think about Angular as a "build once" technology since each and every build of the same code has the potential to fail.
• Private NPM registry?  I found the 'blessed way' of handling this to be underwhelming. If you search for other free/open source options you will likely end up at Sinopia which is a dead project last I checked this issue. Note that nothing at the Sinopia link indicates it isn't maintained.  I would recommend Verdaccio at this moment. I find it crazy that you must expend a good amount of time just to figure out a reasonable open source private registry solution.  There are several non-open source solutions available.
• I've run into a number of odd and possibly random issues during 'npm install'. At this point, I'm trying to keep up with npm updates hoping to reduce the number of days where repeatable builds seem impossible.  Tools or infrastructure - who knows?
• Module systems - CommonJS vs AMD vs ES6 vs .... And people complain about the complexity of languages such as C++..  
• Typescript and integrating 3rd party JS based modules - I'm still working through a situation where a 3rd party module has only a single anonymous function exported and there is no definition file. This is another productivity killer. This may be more of an experience issue (lack of on my part related to Typescript) than a true technical issue but googling for "best solutions" is slow in this case.
• Throw in some technology such as an API generator targeting Angular 2 and other technology such as an API proxy and you get some unwanted complexity.  What was initially a quick (and good) way to stand up simple applications turns into something much higher in complexity.  How how I can't say. 
• Arg.  Renames of packages and/or packages of similar names make thinks difficult to sort out when looking for useful components and/or tying to use them.  Too much change and little maturity.

[Edit 2017/04/20 - feeling the need to add some positives to my analysis] 

+ It sounds like Angular 4 is a step toward better versioning (semantically speaking). I don't know that it is a total fix in itself since there are still many libraries/frameworks that need to fall in line regarding versioning.  

+ The dependency injection in Angular has been somewhat useful.  

+ The overall "feeling" of development isn't too bad - given enough time and maturity it may be "very good or great".

So should you dump your applications / user interfaces that are rooted in JEE type technology? I don't think so. At least not yet. It is probably worth keeping an eye on technology such as this.  I would certainly evaluate the risk for the type of use you expect along with the productivity differences between this and whatever you were doing.

Thanks for reading!
May Jesus bless your day!

Scott