The followup (i guess it can be called that ) to Broken Empire . Different main character, different "quest" but the madness is still there. While i didn't enjoyed Red Queen's War as much as Broken Empire (different strokes for different folks i believe ) it is still a good and enjoyable (you can read it independently of the Broken Empire but you'll miss some jokes/callbacks) series.
Bring them on , Mark Lawrence.
The first tip is about upgrading your powershell help files so it will be up to date. For this just run :
Second tip is about searching for useful cmdlets when trying to achieve something with powershell. For instance if you are interesting in looking at the event viewer entries (for instance), you can run :
and get back all the cmdlets that let you interact with the event viewer.
The golem and the jinni
Very nice, very different from the "typical" fantasy novel. The genie in the past bits were the best, i'd gladly read a full novel with those parts.
The Night Angel trilogy
It's enjoyable. A much more "typical" fantasy series with good world building and character development.Most of it presented from a stealth assassin perspective. Towards the end , the narrative kind of stumbles a bit , but overall a enjoyable read.
First 2 are the last books from the Companions Codex trilogy while the last if first book from new Homecoming trilogy.
First 2 books are fine, they reminded me of the old school Drizzt stories, even the cast of characters are very.....familiar. The last one is pretty bad though. The entire books is used as a setup for the cooler things to happen next.
It's a simple equation with 3 variables : time (and implicit money), set of features/bugs ratio and code quality. For best results the trick is not to overemphasize one over the remaining 2 and just keep all 3 balanced. Sounds simple but sometimes it feels like the hardest thing in the world.
Non functional requirements are just as important as functional ones. Yet not much thought is given to them (especially at the beginning when writing the specs for a new "system"). For instance everyone, obviously, wants a secure application (also security is a bool, it's either secure or not, there are no intermediary steps) so a new application will not be released if it's insecure no matter how many functional requirements are implemented.
The idea is to always keep in mind non functional requirements when designing a new "system". Some of the non functional requirements (like capacity/performance or security) can even have a direct impact over the functional requirements.
Finally the 64 bit version of Firefox is out. It works side by side with the 32 bit version (by default 64 bit version is installed in \Program Files instead of Program Files (x86)) but i really recommend everyone to just install the 64 bit version and ditch the 32 bit version (just make sure you back up your profile before doing this).
SELECT * FROM sys.foreign_keys WHERE referenced_object_id = object_id('YourTable')
There's a new Shopkeeper update (v2.6.2) . Grab it here
Change log :
- few small fixes
- added "Edit" button in product details page that redirects to the edit page in administration area. Button is available only if you are logged as administrator.
One of the new C#6 features is string interpolation (which makes the code much nicer than using string.format()) . But by default the new Roslyn compiler is not used when compiling the MVC views. You can change this by installing the nuget package called Microsoft.CodeDom.Providers.DotNetCompilerPlatform
powershell.exe "start microsoft-edge:http://google.com"Obviously feel free to either replace or delete the http://google.com part.
initial = ImmutableList .Empty;
immutableList = initial.Add("stuff");
ListNow you can pass readOnlyCollection and obviously the initial collection will remain unchanged.
initial = Enumerable.Range(1, 10).ToList();
readOnlyCollection = initial.AsReadOnly();
Shopkeeper has a new site now. It's still far from containing all the stuff i want there but it's a start.
Ah, the build + optional deploy script. The "thing" that turns whatever your compiler spits out into a zip/msi/whatever that you can actually install /pass along to customers. For build scripts i've started with batch files, C# , Powershell, moving to msbuild tasks (yeah, that was "fun" ), FAKE, to the node.js "task runner" framework du jour (Grunt, Gulp etc) to finally get back to Powershell.
I still think the best solution for writing a build script is in a shell scripting language (Powershell, bash, whatever) because :
- when it will crash (and it will !!) you're debugging code written by you instead of fuzzing around with a stacktrace spitted up by some shitty Grunt plugin (for instance).
- ubiquity : only powershell/bash is required to run it (compared with node.js + npm + gulp + whatever other plugins you are using).
- simplest way to run 3rd party CLI apps as part of build process ( "& filePath args" and you're done).
- everything is in one place (no package.json, gruntfile(s) and so on). A single file that handles everything.
Names are all wrong in the Warhammer fantasy universe. I mean, who calls a badass vampire "Radu" ? Seriously, it's a vampire not a baker.
Anyway, the premise in "Curse of the necrarch " is very straightforward : big fight between humans and undead. That's basically it. There is some "background" plot to this but it's not really that interesting (or sufficiently developed). Overall i'd say the books is kind of meh.
Working on Shopkeeper localization. Lots of commits with same message.....
This is the first book i've read in the Warhammer fantasy setting. It's actually a collection of 3 stories "tied" together with 2 short ones. It's the story of a ragtag group of human soldiers who do different "jobs" for the Empire in exchange for their freedom. Overall the quality is okeish, nothing bad but nothing great either.
Just reading the classics. Although scifi is not my favorite genre, it makes sense to read what is apparently ranked as the world's best-selling science fiction novel. Overall i enjoyed the first book. I wouldn't go as far
as say it's a "great book" , but it's enjoyable. I enjoyed the characters, world building and the
environment/ecology part of the story (apparently Dune is the first book which deals with the environment/ecology subject). The story both drags in some parts and rushes in the other (especially in the second half) but it's not that bad.
Dune Messiah, on the other hand, it's a completely different kind of book. I understood why the book is written like that (the whole book basically "deals" with the psychological state of the main character after the events of the first book) but , in the end, the book is very different from the first one. It (mostly) lacks "action" and the tone is very different from the first one (not in a good way).
So i've found out that Dropbox and OneDrive actually support junction points . That basically means you can backup your GDrive and OneDrive folder to Dropbox (for instance) .
mklink /j "c:\dropbox\gdrive" "c:\users\blah\google drive"
var upload: HTMLInputElement =
Bullshit. Development of proper, complex apps for multiple devices is fucking grueling and no "toolkit" will save us. "Responsive design" is a idiotic term which is paraded a lot these days. The sad reality is that "responsive" design only "works" on simple , "static" , "read only" sites. It doesn't work on complex apps (with multiple form elements and somehow omplex UIs). Doing a "proper" web app with a certain level of complexity to work on multiple devices and form sizes IS hard work. There are still chunks of a browser behavior very important on mobile that are not standardized ( like zooming for instance). See how easy is to make a single HTML element not zoomable on mobile. Use kendo, jqueryUi, jqueryMobile, whatever ...is still a LOT of work just to get some basic layout behavior work. Something take is very simple to do with the "native" UI toolkits.
From my point of view a part of the problem is HTML and CSS (especially CSS) standards. The specs have become just too convulted and W3C just tries to cover EVERY single scenario now. Especially CSS is a clusterfuck of a complex specification , look at display for instance. And the irony a basic thing like centering a piece of text in a container is still hard too do with CSS. There are 3 million search results on Google on how to do that . This is the most basic operation that a layout engine should do and is still hard to get right.
From my point of view the "answer" would be a new standard with a much narrow . Something simple which describes a layout engine that should just works and which has the "responsive" stuff baked from the start. Maybe built on top of WebGL. Something that can actually take on mobile native toolkit. But yeah...i wouldn't hold my breath for this. After all W3C is still chasing jQuery level developrs with new APIs.
And Google....you're not moving the web forward with a half assed Bootstrap clone.
$dx = 'c:\dropbox'
cd %dxand you'll navigate to c:\dropbox. The advantage of using vars is that you can reuse them if you write some code interactively. The disadvantage is that you'll always have to "cd" manually to actually navigate to that path.
del myfile.txtto delete a single file. It also works with wildcard selector
Remove-Item myfile.txt. But, obviously, you don't want to type "Remove-Item" each time so you can use the alias "rm".
mkdir myFolderto use DOS/Linux command or
New-Item MyFolderto use the builtin cmdlet. For files you usually want to edit it after creation. Personally i just run vim to create and edit the file using a function defined in my profile. Something like
vimedit a.txtwhere vimedit will just run vim with the specified path as a parameter
function psgrep($path, $fileType, $string)
get-childitem $path -include $fileType -rec | select-string $string
psgrep c:\oss\ *.cs "static". This will search for the keyword "static" in filetypes *.cs from path c:\oss
function psgrepFile($path, $fileType)Invoke it like this :
get-childitem $path -include $fileType -rec
psgrepFile c:\oss a*.xml
"The Companions" is basically the first book of a new serie called "The Sundering". But it's also "fits" in the timeline of the Drizzt saga. Personally i didn't really liked the book. I think is basically superfluous. All the events described in this book could have been a chapter in the next "proper" book. It's kind of hard to describe exactly why i didn't like it this without spoiling the storyline so...i won't try.
"Night of the Hunter" is the first book in a new serie called "The Companion Codex". Overall i would say the book is okeish. From my point of view Salvatore is retreading too much but if you don't mind that, the book should be a enjoyable read. As least the good ol' drow scheming is back in action :)
create database foo on (name='foo', filename='c:\DBs\foo.mdf')
Been wanting to read these for a while. Jordan Mechner notes about creating Karateka and Prince of Persian. Lighthearted, interesting read about a kid trying to break into the game industry ~30 years ago. Things were so different back then.
Favourite quote is " I dreamed about being chased by a subroutine".
More Drizzt , yay !! The good news is that the first book, Gauntlgrym, is pretty enjoyable and hearkens a bit to the old books. The bad news is that the next 3 just aren't that great. They aren't bad but they aren't good either. My main criticism is that is just not enough interesting content in there. Too much filler (and, i think, RA Salvatore releasing a new book each year doesn't help with this). Anyway....personally i wouldn't mind waiting 2-3 years for a good book with Drizzt.
I ask this question pretty often to my fellow colleague developers. I'm actually very interesting to see how exactly they perceive the work they do. Most of the time i get back the boring (and untrue) "engineer". Most of the people "doing software" seem to think they are engineers. This can't really be further from the true (if you don't believe me, you should speak with a "regular" engineer from other areas and compare your work with his/her).
Another category of people think of themselves in more abstract terms : poets (because writing code is exactly like writing poetry, right ?) or even philosophers. Obviously, this is bullshit....
Other people think of themselves as craftsmen (personally i think this is a lot closer to the truth). At the end of the day, personally, i think building software is a lot like regular craftsmanship.We use tools just like other craftsmen (instead nails and hammers we use IDEs and debuggers) to "craft" something. The result of our work is , hopefully, something that other people enjoy to use.
What i don't understand is why do people get upset when i told them there isn't much of a difference between what they do and people who build chairs...
Maybe we can write code like this in CSS4. But i won't hold my breath.....
@media screen phone
@media screen tablet