Archive for the ‘Software Development’ Category
Posted by jpluimers on 2018/03/30
Cool interactive colour mixing:
The www.spectrumcolors.de site has way more interesting pages around colour spaces, colour press techniques (like colour separation, rasterising, etc). Worth visiting!
–jeroen
via:
Posted in Algorithms, Development, Power User, Software Development | Leave a Comment »
Posted by jpluimers on 2018/03/29
[WayBack]FizzBuzz: One Simple Interview Question… Jeroen Wiert Pluimers – Google+:
THE BASICS S1 • E2
FizzBuzz: One Simple Interview Question
Tom Scott
Published on Jul 31, 2017
There are a lot of opinions on how to hire coders, and most of them are terrible. The opinions, that is, not the coders. But a basic filter test to make sure someone can do what they say they can: that seems reasonable, and FizzBuzz is one of the more common tests. Even now, interviewers use it. Let’s talk about why it’s tricky, and how to solve it.
Imran’s blog post: [WayBack] Using FizzBuzz to Find Developers who Grok Coding | Imran On Tech
Other approaches for pretty much every language: [WayBack] FizzBuzz – Rosetta Code
…
In retrospect, I wasn’t really surprised Kristian Köhntopp commented these two:
–jeroen
– https://plus.google.com/+KristianKöhntopp/posts/jYKBAD4MHMj
Read the rest of this entry »
Posted in Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/03/29
Interesting to try:
The new generation Pascal programming language that combines simplicity of classic Pascal, a great number of modern extensions and broad capabilities of Microsoft .NET Framework
I didn’t know about it either.
–jeroen
Read the rest of this entry »
Posted in .NET, Development, Pascal, Software Development | Leave a Comment »
Posted by jpluimers on 2018/03/27
From the “I hate my users” department:
- This dialog pops up every 10 seconds
- The Office 2011 for Mac update requires non-Office apps to quit as well
–jeroen
Posted in Apple, Development, iMac, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, MacMini, Office, Office 2011 for Mac, Power User, Software Development, Usability, User Experience (ux) | Leave a Comment »
Posted by jpluimers on 2018/03/26
I forgot to blog about this before, but 2 months ago PowerShell core came available: [WayBack] PowerShell Core 6.0: Generally Available (GA) and Supported! | PowerShell Team Blog.
[WayBack] Installing PowerShell Core on macOS and Linux | Microsoft Docs is easy (one way is through homebrew:
$ brew tap caskroom/cask
$ brew cask install powershell
If you already installed a beta, then the steps are these:
$ brew update
$ brew cask reinstall powershell
Note that after installation, it is known as pwsh (at least one of the betas named it powershell) to set PowerShell Core apart from PowerShell*:
$ pwsh --version
PowerShell v6.0.2
Via: [WayBack] PowerShell Core 6.0 is a new edition of PowerShell that is cross-platform (Windows, macOS, and Linux), open-source, and built for heterogeneous environm… – Lars Fosdal – Google+
*pwsh versus powershell
There has been quite a discussion on the PowerShell Core repository on the rename, but I think it is for a good reason.
Too bad that during part of the beta, the old name powershell was used, but beta-time means things break every now and then.
PowerShell Core is sufficiently different from prior PowerShell versions to warrant a name change. This also makes it a lot easier to use them side-by-side.
Many other names (like posh, pcsh or psh) were considered, usually because of naming conflicts with existing tools (like posh) or easy confusion with existing shells (like pcsh and csh). A benefit on Linux/macOS is that it now ends with sh like virtually all other shells.
More background information is at:
–jeroen
Posted in Apple, CommandLine, Development, Home brew / homebrew, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, MacMini, Power User, PowerShell, PowerShell, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2018/03/26
From [WayBack] Docker – Docker Cloud Migration Notification and FAQs:
The services on Docker Cloud that provide application, node, and swarm cluster management will be shutting down on May 21.
…
If you do not migrate by May 21, your applications running on the Docker node cluster management service will cease to operate.
Swarms will continue to function; however, if you do not retrieve your SSH keys for the Swarms being managed by our swarm cluster management service, you will be unable to access your swarms using your Docker ID. For instructions on how to retrieve and access your Swarms with SSH keys, please refer to the Docker docs.
So soon, no more [WayBack] Docker Cloud – Build, Ship and Run any App, Anywhere.
Remember: still the cloud is other peoples computers, so be sure you can move when needed.
–jeroen
Posted in Cloud, Cloud Development, Containers, Development, Docker, Infrastructure, Power User | Leave a Comment »
Posted by jpluimers on 2018/03/21
About a year ago, [WayBack] Rumors of Cmd’s death have been greatly exaggerated – Windows Command Line Tools For Developers got published as a response to confusing posts like these:
But I still think it’s a wise idea to switch away from the Cmd and to PowerShell as with PowerShell you get way more consistent language features, far better documentation, truckloads of new features (of which I like the object pipeline and .NET interoperability most) and far fewer quirks.
It’s time as well, as by now, Windows 7 has been EOL for a while, and Windows 8.x is in extended support: [WayBack] Windows lifecycle fact sheet – Windows Help:
| Client operating systems |
Latest update or service pack |
End of mainstream support |
End of extended support |
| Windows XP |
Service Pack 3 |
April 14, 2009 |
April 8, 2014 |
| Windows Vista |
Service Pack 2 |
April 10, 2012 |
April 11, 2017 |
| Windows 7* |
Service Pack 1 |
January 13, 2015 |
January 14, 2020 |
| Windows 8 |
Windows 8.1 |
January 9, 2018 |
January 10, 2023 |
| Windows 10, released in July 2015** |
N/A |
October 13, 2020 |
October 14, 2025 |
Which means the PowerShell version baseline on supported Windows versions is at least 4.0: [Archive.is] windows 10 powershell version – Google Search and [WayBack] PowerShell versions and their Windows version – 4sysops
PowerShell and Windows versions ^
| PowerShell Version |
Release Date |
Default Windows Versions |
| PowerShell 2.0 |
October 2009 |
Windows 7 Windows Server 2008 R2 (**) |
| PowerShell 3.0 |
September 2012 |
Windows 8 Windows Server 2012 |
| PowerShell 4.0 |
October 2013 |
Windows 8.1 Windows Server 2012 R2 |
| PowerShell 5.0 |
April 2014 (***) |
Windows 10 |
So try PowerShell now. You won’t regret it.
–jeroen
via: [WayBack] Very interesting clear-up post and comments on CMD, command.com, PowerShell in past and future DOS/Windows versions and Unix shells altogether. – Ilya S – Google+
Posted in Batch-Files, CommandLine, Development, Power User, PowerShell, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
Posted by jpluimers on 2018/03/20
One of those “duh” moments: go --version says there is no go -version, but there is go version as shown below.
It is even at [WayBack] Print Go version right in the middle of this 30 page [WayBack] go – The Go Programming Language.
On the hunt for that, I found this very interesting link for when you have binaries built with go and need the version: [WayBack] How to find out which Go version built your binary | Dave Cheney.
$ go --version
flag provided but not defined: -version
Go is a tool for managing Go source code.
Usage:
go command [arguments]
The commands are:
build compile packages and dependencies
clean remove object files and cached files
doc show documentation for package or symbol
env print Go environment information
bug start a bug report
fix update packages to use new APIs
fmt gofmt (reformat) package sources
generate generate Go files by processing source
get download and install packages and dependencies
install compile and install packages and dependencies
list list packages
run compile and run Go program
test test packages
tool run specified go tool
version print Go version
vet report likely mistakes in packages
Use "go help [command]" for more information about a command.
Additional help topics:
c calling between Go and C
buildmode build modes
cache build and test caching
filetype file types
gopath GOPATH environment variable
environment environment variables
importpath import path syntax
packages package lists
testflag testing flags
testfunc testing functions
Use "go help [topic]" for more information about that topic.
–jeroen
Posted in Development, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 