Group items tagged

In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that: - Use declarative formats for setup automation, to minimize time and cost for new developers joining the project; - Have a clean contract with the underlying operating system, offering maximum portability between execution environments; - Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; - Minimize divergence between development and production, enabling continuous deployment for maximum agility; - And can scale up without significant changes to tooling, architecture, or development practices. The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).

Testing distributed systems under hard failures like network partitions and instance termination is critical, but it's also important we test them under less catastrophic conditions because this is what they most often experience. Comcast is a tool designed to simulate common network problems like latency, bandwidth restrictions, and dropped/reordered/corrupted packets. It works by wrapping up some system tools in a portable(ish) way. On BSD-derived systems such as OSX, we use tools like ipfw and pfctl to inject failure. On Linux, we use iptables and tc. Comcast is merely a thin wrapper around these controls.

 global Automated Fingerprint Identification System market will grow at a CAGR of 19.71 percent over the period 2012-2016.

A few years ago, I took on a freelance project to implement an Internet Explorer component in C++. I was billing a healthy hourly rate on other projects at the time, but this particular client insisted on a fixed price. In a bout of temporary insanity, I made an exception.... Every developer knows that accurate software estimation is not possible even when perfect information is available about project requirements (i.e. practically never).....

podobne nazory na estimate trvania taskov som cez vikend cital aj v tomto clanku https://techcrunch.com/2016/12/11/death-to-jira/ , odhady veru nie su easy

Z toho clanku "death to JIRA" vypichujem: For some reason many companies today seem to be terrified of the prospect of writing more than a couple of paragraphs of clear and simple prose. But a well-written 8-page document can define the nuances of a complicated system far better than a whole cumbersome flotilla of interlinked JIRA tickets. ... Feature planning is about communication. JIRA is fundamentally a terrible way to communicate the requirements of a complex system. Words in a row, if written well, will always be better. A v dost vela veciach suhlasim.

PostgreSQL is an open source multi-purpose relational database system which is widely used throughout the world. It is one huge system with the integrated subsystems, each of which has a particular complex feature and works with each other cooperatively. Although understanding of the internal mechanism is crucial for both administration and integration using PostgreSQL, its hugeness and complexity prevent it.

I've written server-side applications for a decade now, and monitoring the components of your application is critical but painful. What monitors the CPU and RAM usage of your custom daemons? What monitors Redis, MySQL, memcached and the other parts of your system to ensure they are all behaving normally? What if I told you you could do all that and set it up in less than 5 minutes?

Fingera pre indickych uradnikov

North encourages an agile, content-first, approach to product development and a mobile-first, in-browser, system based approach to design and development.

zabavne citanie ako motorola dodala kriminalny afis a nedokazala splnit poziadavky na rychlost, presnost a este to musia dost casto restartovat

new system that not only captures rolled fingerprints and tenprints but also allows the user to sign the glass to register a signature.

Linux servers displayed a notable tendency to misbehave during the leap second event at the end of the day on June 30. The problem often presented itself as abrupt and sustained load spikes on the affected machines....a look at what happened shines an interesting light on the trickiness of dealing with time in software systems.

Look at recent Microsoft releases: we don't fix old features, but accrete new ones. New features help much more at review time than improvements to old ones. (That's literally the explanation for PowerShell. Many of us wanted to improve cmd.exe, but couldn't.)

Making everything easy to change makes the entire system very complex. Technical debt is a metaphor developed by Ward Cunningham, who uses the term to describe the design tradeoffs we make in order to meet schedules and customer expectations.

nejako mi to pripomenulo dnesne zufale pokusy stiahnut nejake data zo serveru v malawi: The ten minutes you spent planning will save 30 minutes later in the day when you don't have to spend the time shuffling through the papers on your desk, looking for that one thing you misplaced. Think like a chef: Put everything in its place today, and watch your workflow speed up to five-star quality.