This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
$remoteport = bash.exe -c "ifconfig eth0 | grep 'inet '" | |
$found = $remoteport -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}'; | |
if( $found ){ | |
$remoteport = $matches[0]; | |
} else{ | |
echo "The Script Exited, the ip address of WSL 2 cannot be found"; | |
exit; | |
} |
--colour | |
-I app |
ּ_בּ | |
בּ_בּ | |
טּ_טּ | |
כּ‗כּ | |
לּ_לּ | |
מּ_מּ | |
סּ_סּ | |
תּ_תּ | |
٩(×̯×)۶ | |
٩(̾●̮̮̃̾•̃̾)۶ |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
Hi, we're Envato and we're looking for a "senior" Ruby on Rails developer.
We know it's a bit absurd to ask for seniors for a new-ish technology, but we're more looking for the senior mindset, for depth and breadth of experience in delivering good quality code, and helping your teammates achieve the same. We need the kind of people we can point at a big problem with maybe another dev or two by their side and come out with a neat solution on the other side. We'd prefer to hire someone with practical, commercial Ruby on Rails experience, but if you're a Python, Java, .NET, Haskell, LISP, or whatever else developer who picks up new things quickly and can get things DONE we want to speak with you.
First though: a bit about us. We're a youngish company, transitioning out of the hectic startup days and into something a bit bigger and more settled. We operate a series of online stock digital media marketplaces such as Activeden (formerly FlashDen), GraphicRiver, ThemeF
I've been wanting to do a serious project in Go. One thing holding me back has been a my working environment. As a huge PyCharm user, I was hoping the Go IDE plugin for IntelliJ IDEA would fit my needs. However, it never felt quite right. After a previous experiment a few years ago using Vim, I knew how powerful it could be if I put in the time to make it so. Luckily there are plugins for almost anything you need to do with Go or what you would expect form and IDE. While this is no where near comprehensive, it will get you writing code, building and testing with the power you would expect from Vim.
I'm assuming you're coming with a clean slate. For me this was OSX so I used MacVim. There is nothing in my config files that assumes this is the case.
# A simple Makefile alternative to using Grunt for your static asset compilation | |
# | |
## Usage | |
# | |
# $ npm install | |
# | |
# And then you can run various commands: | |
# | |
# $ make # compile files that need compiling | |
# $ make clean all # remove target files and recompile from scratch |
# Required: an admin contact for errors, billing issues, and the like | |
admin_email: your.name@yourcompany.com | |
# Optional: timezone for when to send and how to format emails | |
# defaults to "Australia/Melbourne" | |
timezone: "Australia/Melbourne" | |
# Required: config for shipping news (notify on merged PRs) | |
shipping: | |
# Array of release notifications to send | |
- |
1. Monolithic applications and architectures can vary in their monolithness. This is an under-specified description. | |
2. Microservice applications and architectures can vary in their microness. This is an under-specified description. | |
3. Microservices and monolithic architectures have both benefits and disadvantages. | |
4. Organizations will exploit those benefits while working around any weaknesses. | |
5. Success of the business is a large influence on the exploitation of benefits and implementation and costs of workarounds. | |
6. All benefits and work arounds are context-sensitive. Meaning that they are both technically and socially constructed by the organization that navigates them. | |
7. Path dependency is a thing. History matters and manifests in these architectural decisions and evolution in an organization. | |
8. Patterns exist to inform practice, not dictate it. Zealous adherence to an architectural pattern brings peril when it is to the exclusion of cultural context in actual practice. | |
9. Architectural patterns w |