If you are looking for something to use this good theory on take a gander at Drools http://www.drools.org/ (Apache v2 license)
20 karma · joined December 9, 2015
But if you really want a trackpad, yep, nothing beats an Apple Touchpad. (or at least what I have used / seen)
Monogatari (Anime Series) - It is a jumbled mess that is a jumpy as it is deep. If you don't want to see any fan service at all in your anime I would skip over this. If you don't mind that (or enjoy it) this is a great anime. It doesn't knock my favorite anime (Cowboy Bebop) off of my Number one slot, but this one is a great that I would wager will stand for the future. (Bakemonogatari is the first season).
Don't Panic - There's a reason it is written in big bold red letters on the universe's best selling book.
Speak your problems logically and show that you've given some thought to them when you talk with your boss.
My biggest inspiration (other than taking a perfect shot at a whitetail deer and him just dropping dead) was a good PDF about shotGroups over on the CRAN[1]. It is a little dry and statistically heavy (meaning you need to have some statistical background to make sense of it), but well enough detailed for the info that triggered me to pursue this pet project.
I would love to write it at a level where if a person with no statistical background would be able to read through it and be able to understand it "enough". (Which requires a lot of rewriting on my part to make sure I'm also not boring a person with statistics background to death too explaining what Standard Deviation is :P)
[1] https://cran.r-project.org/web/packages/shotGroups/vignettes...
True:
> no discussion of how one might interpret this model, what its assumptions are, and how to assess validity or fit?
Quoting OP from the comments in his blog:
> Hey Victor, thanks for reading! You’re absolutely right, I should have taken some time to talk about the assumptions of linear regression. I tried to mention them in passing, but I’ll try to be more explicit next time. I should have brought up the pearson correlation coefficient. I tried to write this from a more machine learning point of view, not as much statistics.
Either way it was a decently written post and would read more in the future (though I would like to see more statistics side of things rather than just me thinking Alex here is waving his hands saying 'you see nothing!' when we look at the mathematical assumptions / 'pure' statistics).
In other thoughts:
I'm currently in the process of writing a blog series on the analytics of Firearm projectiles (What ammo is most accurate from a Ruger American 308 Win.). Seeing other statistical posts like this help me figure out how to make mine better. So thanks Alex!
I also keep up with friends/acquaintances (typically people on the 'business' side of things). Though most of my software/programming buds and gals we connect elsewhere (typically through Steam).
But if what you are after is insight into how a computer works I found that I had my 'ah-ha' moment while learning C, Assembly (intel), and writing a compiler. I did have to have a slight basis in computer architecture, but that compiler project I worked on made everything click.
(side note on writing a compiler. Read, Decode, Execute. There are no short cuts around those series of steps).
If you are looking for a book I would recommend the 'Dragon Book'
http://www.amazon.com/Compilers-Principles-Techniques-Tools-...
I found a paper copy of the international version for cheap (like $10 US if I remember) that was amazing.
I have debian on my NAS and 'stable' backup box. I keep this thing rock solid.
If I actually want to do anything crazy, I'll either whip up a VM or I have a clunker of a laptop I keep around for experimenting and other things (along with other single board computers).
My two cents in keeping something stable is don't do anything to it. Keep it as vanilla as possible unless you are 100% sure what you are doing.
Good post and read.
I feel like this is more obvious in software. Errors are handled and reported in the logs, but it still works. Sure they, the errors, need to be fixed. But problems that cause things to crash (contextual pun) need to be fixed first.
Though I did like that post :D
I took a COBOL course just two years ago in a Texas Public University. It was considered the 'I didn't get any offers anywhere else' or 'I am too lazy to apply' if you were picked up by IBM as a COBOL engineer. I was trying to pull up the online syllabus. Seems like they have finally gotten rid of that course (or maybe the professor who taught it finally passed away).
As annoying as COBOL was, it was unique and interesting in the way it handled IO processing. From what I understood from talking with those who had gone the COBOl engineer route from my school, was that it was never quite learning COBOL, but rather all the jank years of programmers added into the codebase. COBOL is annoying, but when you have the equivalent of jank similar to badly designed #define 's all over the place that makes you want to thrash out at everything and anything when you realize what is happening ... that is, from what I have been told, a major reason COBOL sucks.
It wasn't my cup of tea, thus I didn't pursue it, but to fellow classmates, they quite enjoyed it as one would when you program in C. It had a certain elegance to it.
I found this statement rather interesting. I had an internship at Garmin where they provided housing to all the interns via dorms at a nearby university. It was rather refreshing to be near students whom where, for the lack of better words, smart. They had received an internship. There was some bar that people had to pass higher than just SAT/ACT and what your grades were in High School. People had drones, RC cars, Raspberry Pis (and others), every weekend was something different and new. (Not to mention how engineers can go from drinking, to science, and back in seconds).
It was a better time than I ever had in University Housing at my actual college (but then again my college wasn't exactly a Tech/Engineering college (we just had a decent program that wasn't $250K)). Even when I made my stunt to stay in the Honors Dorm at my University, there's quite a divide of personality when you get students from all majors. It was rather segregated internal communities of STEM, Arts, and Not STEM/Arts. It was never quite as amazing to live in a group like that was provided at that Internship.
That way you aren't stuck with specialty tools if you don't like it. Also stay away from nicer glass. Don't get kokomo glass if you don't need/want it. I always just see what's in the scrap bin and then design based from what's in there.
Gardening is also something I enjoy. Learning about plants and keeping them healthy year round. It is very satisfying to have a harvest of your own plant (I grow a decent sized Tabasco pepper plant.) Though this turns into a more solo task unless you do it in a community garden or something like that.
VERY much so. So, imagine yourself as some old bank executive. Sure you work at a more progressive (tech and policy wise) bank than others, but still at the end of the day we're a bank. Why would we give free things away? That was the main reaction before our current CIO, Rob Alexandar, got into the mix of things. He has slowly been pushing to become more and more forward thinking about tech from the top down. Which is a hard thing in such a regulated environment like a bank. There are so many internal power struggles on old systems that all new tech hires (new meaning last 5 years and younger) with getting rid of older things. We have begun to rewrite major systems. Keeping good documentation. Transitioning everything to git rather than SVN. Updating our AppSec ability to audit things quickly such that we can actually get something to production in a week if we really want to.
Also for me, every interview I had after my Google one felt like a cake walk.
Whatever you do with it, congrats for being reached out to. You don't know what you did but you were doing it right ;)
He was the 'Hard' Professor of our CS program. The one where if you could walk out of a test with a 50/100 you felt like you just won the lottery. He was ruthless, iron clad, and never made a mistake with his grading. He would never assign a textbook in which he wouldn't use every chapter to lecture from. He would run through a red pen for each class writing notes back to us and giving us different ways of studying and writing down exercises from the book or his mind to help us understand. We would learn the material. Getting out of his class with a 'B' or even rarer an 'A' was considered a very high honor (and jokingly, the stuff of legend) at our University.
But when he recently announce his retirement, students from years gone by came back, almost like a pilgrimage, to reach back out to him in some way. His ruthless tests, his wise teaching, his fatherly advice for all things in our initial careers in whichever direction we went with them, that is a reason I was glad I went to college and had the honor and privilege to learn from him. Jokes of how many people had to extend their stays at university because he 'failed' them, but then again each person whom hated him at that point, still made the trek back and regarded him one of their lives best mentors.
Are there crappy people in college (students, instructors, professors, admins, etc.) ... heck yeah. But then again there are those who instill values and education in their peers. You just need to find them.
https://github.com/capitalone/Hygieia
So I work for Capital One (obligatory What's in your Wallet). This is our Open Source DevOps Dashboard (Apache v2). We do make outside contributars agree to a "Capital One Individual and Corporate Contributor License Agreement" (ctrl-f for 'Link to Agreement' on the main git page I provided above).
Essentially, from a buddy of mine who works on it, we basically just need to make sure people don't somehow add non-compatiable liscensed code to it, and we can keep using it with your contribution.
As for the commits from outside and taking it so that we can use it, I believe we not only have the team incharge of the project review the code, but also our Application Security guys look at the code a lot. (They always scrutinize any and all non internal code for any sort of malicious intent (software or legal)). Once the green light is from them then we are good to go, to my understanding. I don't directly work on the project. (Shameless plug for what I do work on https://ane.capitalone.com/landing . Huzzah for Direct Auto Loans!)
I don't know much else, but if you reach out to any of the more active people who contribute they'll reach back out, or atleast they did for me when I reached out via my personal git account.
We have two other open source projects, but I am not as familiar with them as Hygieia.
I spent a long while, and still do, thinking about what am I heading towards. I know a lot of people don't know this and there is no way I will ever know all the details to make a decision, but I prefer the 'fail to plan, plan to fail' montra. Thus I plan, but am willing to scrap my planes in the wink of an eye, contingent on new infromation.
This is what I did and maybe you'll find something helpful in this method. Find what makes you tick. Make a list of things you enjoy doing. Try to be specific as you can. (You like novelty. Okay then maybe something like 'I like to learn a new trade skill (wood carving, stained glass, etc.) every 6 months.') Try to begin to boil it down to a long list. Keep adding things to the list, and take a break from the list every now and again (just to bring a fresh pair of eyes to it). If an idea seems broad, try to break it down (when I did/do this, I try to be able to tell someone the idea and they would be able to go out and do it exactly how it is in my head).
Then next to the list make columns like 'Financially sound ideas' (buying 32 Raspberry PIs to make a large cluster computer is not as financailly sound as Learning how apache2 works), 'Speed of doing' (you can learn how to write C at a basic level in an afternoon, but learning how to weld may take you longer), 'Practical for you to do' (if you weigh 400lbs and wanting to go backpacking through the Rockies is not as practical as learning how to write better on a whiteboard), 'It would bring me immediate gratitude', 'it would bring me long term gratitude', etc.
After you make a large list rank each column with 1-5 or some other ranking system (I liked the 1-5 because I could say I really hate, sort of hate, neutral, like, love an idea). Then you can hopefully start to see things that rank high in each category you made. (e.x. I really want to take a trip around South America (drive for two weeks or so through the Andes). It isn't practicle, it isn't quick to do, it isn't finacially sound, but it would be one hell of a memory. It is something I want to strive towards and go one day.)
2a) Did the company recently have any bad press? (Smaller companies were harder to judge on this, but larger ones are easy. i.e. JP Morgan Chase was not on my list, However Capital One was.)
2b) (This was only used if I was unsure after 2a) If I knew someone in the company over my professional network, or a frined of a friend, etc. I would reach out and ask them about the company. Most people responded to me which was nice. Come to find out we would talk about our mutual relation and then I could ask them about what they do. I also got some good general advice as well.
3) Does the company 'smell bad'. This was something I didn't really use until I was applying/in the process of getting hired. I would keep my nose out for bad signs. (looking at you Cerner (Great Engineers I chatted with, but their recruiting was a nightmare to deal with, but that may of just been me)).
If you can't tell, I did my best to logically choose and look at data in a very organized fashion. This was due to the amount of data that I knew I was going to manually be mulling over. I needed a way to figure out to to translate my research/feelings of one company to the research/feelings of another.
(Also, you have no reason to believe me, but I did get to last round interviews with Google. I never even applied with them. They reached out to me via LinkedIn. At first I was like 'This must be spam trying to phish me or something', nope real deal. I was keeping a Blog on Blogger about Software Engineering, School, and other semi-professional things. I blame that for them reaching out to me.)
If you choose the shotgun approach, as I did, Keep a spreadsheet, or something, to help organize all the information.
Always Customize your resume by using the words that they put on their job hire post. (This will get you past electronic screenings and non-technical HR people who just look for keywords). This is really annoying (writing your resume each time) but I felt it helped me.
I always researched the company the night before resumes and try to find a technical blog that a company may produce, or some niche thing that the company does. (Capital One and it's AutoNavigator is what I focused on when I was interviewing).
Lastly, I did embellish the truth a little in any of my stories. Not to the point of a lie (... sort of ...) but I made my past technical experience an enjoyable story to listen to. There was a quote I read in 'Iterating Grace', paraphrasing it: Great Stories are better than Great Facts. Don't lie in the facts, but like statistics, you can bend the truth and still let it be truth.
Another piece of advice is make sure you are confident when you walk in. Even for technical roles, confidence is key. Being able to talk and have the interviewer like the interviewee is one of the many keys I found to being successful.
If you don't mind lying, most companies will never check your GPA past the transcript you hand over (if you do that at all). So you want to embellish that 3.2 GPA to be a 3.5+ go ahead. Most companies never check. (Come to find out I didn't have the correct GPA on my resume when I changed semesters even though I had an updated Transcript I was sending out. No one ever bothered me about it). I did not ask the HR at my company this question as well and they did not confirm this fact.
I hope that helps you some :D
Either way Having more arrays of Satalites for GPS will be better for all devices (Planes, Auto, handheld, etc.).
(OPs last paragraph)
I should of also added that Java is a good language to start out with due to schools teaching with that a lot, or the large portion of workforce that uses Java. So teaching functional programming (albeit Java is not strictly that) is doable using Java. But also has benefits of the AP test if OP and their kiddo are thinking college.
(Also, if you are in the U.S. then as much flack as Java gets as a language, it is the language used for the College Board AP exam for Computer Science (https://apstudent.collegeboard.org/apcourse/ap-computer-scie...)
Almost like naming convention is looking at something through a telescope (very narrow point of view, but very concise) and comments (especially those at top of functions/Sprocs/algorithms that describe what is happening) are like looking with your bare eyes. You can get a jist of things, but you sometimes can't be sure that's accurate 100%.
(A backpacking saying is "never trust any sign you come across" Someone could have tampered with it since it was put up. Use it as a guideline, but not as a rule. I take a similar approach to comments in critical pieces of code. (Touching Credit Decision-ing for Auto Loans ... yep, gonna slow down and take it slow to make sure I don't screw anything up))
1)
umm I mean you do have an 8x8 grid (8 bits each row) and you could have pieces make up bits being on or off and make a 8 letter phrase (each row being it's own letter).
(Ascii Wikipedia for your reference - https://en.wikipedia.org/wiki/ASCII#ASCII_printable_code_cha...)
2)
Maybe you could also do something like the Where Am I Game?
example:
I stay one night in Denver; four nights in San Francisco; And one night in Washington DC;
Where am I?
1 Denver = D 4 SanFrancisco = F 1 WashingtonDC = W
(DFW) -> Dallas
So you could do something like playing a chess game and for every attempted move (like player 1 moves a Rook but keeps his hand on it and taps the board thinking about the move and then places it down means the letter 'o').
3)
There was also a movie with Bruce Willis (or The Rock Johnson. I always get them confused). Where the main guy tries to escape from a space prison. There was one scene where they communicated over a chess game by only talking when there hand was on the queen. Any word spoken while on the queen was then concatenated to a sentance to convey what they were really talking about.