Group items tagged

vysvetlenie preco nie je velmi vhodne, aby office-management a programatori boli v jednej miestnosti a zvonenie telefonov a postarka vyrusovali tych, ktorych naplnou prace je najma programovat: top performers overwhelmingly worked for companies that gave their workers the most privacy, personal space, control over their physical environments, and freedom from interruption. Sixty-two percent of the best performers said that their workspace was acceptably private, compared to only 19 percent of the worst performers

zaujimava comicsans prezentacia o OpenSSL a potencialnom nastupcovi LibreSSL.

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.

The official Ruby interpreter is written in C. That means that everything you can do in Ruby, you can also do using function calls to Ruby's C API.

The longer an engineer remains at a company, the harder it is to find a few hours of isolation, free from interruption, to get work done.

Hackathon SNG je prvým z podujatí, kde sa stretnú programátori, grafickí dizajnéri, zvukoví majstri a ďalší kreatívci, aby počas dvoch dní navrhli a vytvorili projekt s využitím našich dát.

So what have we learnt today? I think the main thing to take away from this is you shouldn't use public services such as Pastebin to post internal source code. Some creepy guy like me is going to collect it all and write about it. Another thing is to make sure debug information is never pushed to production. I didn't put much effort in to this but there will be more of Facebook's source code floating around out there.

quality happens only if somebody has the responsibility for it, and that "somebody" can be no more than one single person. anyone who has ever wondered whether using m4 macros to configure autoconf to write a shell script to look for 26 Fortran compilers in order to build a Web browser was a bit of a detour, Brooks offers well-reasoned hope that there can be a better way.

A curated list of awesome Ruby frameworks, libraries and resources. Inspired by awesome-php & awesome-python.

mozno trosku bulvarny titulok tykajuci sa beznej http komunikacie, ale je zaujimave to vidiet, ako lahko sa da v tomto svete modulov prist k nestastiu :) myslim,ze sa to rovnako tyka ruby gemov, chef receptov a vsetkeho dalsieho, co obycajne automatizovane tahame cez http..

In this article, author talks about how to improve the accuracy of software development effort estimations. He suggests to use relevant historical data improve estimation accuracy and to avoid early estimates based on incomplete information. He also discusses how to measure and predict productivity in software projects.

There's no such thing as an anonymous programmer: your coding style can unmask you, according to research led by Drexel University Comp. Sci. PhD student Aylin Caliskan-Islam. In work that has serious implications for anyone believing their open source project contributions are anonymous, the researchers find that as many as 95 per cent of contributors to a decent-sized code base can be identified.

excentricky clovek tam zabavnym sposobom vysvetluje preco si mysli ze agilny pristup a TDD su zlo a namiesto toho treba uprednostnit "the hacker way". zaujala ma jeho poznamka na zaver - ze sami programatori musia byt ochotni zaplatit vela za softver ktory pouzivaju, lebo inak tym hovoria, ze ani ich vlastna praca nema hodnotu.

Vystúpi tam množstvo veľmi zaujímavých speakerov. Napr. tvorcovia UML, Ruby on Rails, Google Glass, GNU Bash shell, wiki, TDD, agile a mnoho ďalších.

Aj vas irituje nemoznost menit commit messages? Zaujimalo ma vzdy preco, ci to ma dobre odovodnenie a dnes som to nahodou nasiel: The message from Linus Torvalds may answer your question: Modify/edit old commit messages Short answer: you can not (if pushed). extract (Linus refers to BitKeeper as BK): Side note, just out of historical interest: in BK you could. And if you're used to it (like I was) it was really quite practical. Co ja viem, podla mna nie az tak rozumne, ved moznost commit-ovat davame tym ktorym verime, ja nevidim take velke riziko v tom, ked commiters mozu menit messages. Stava sa mi, ze si pomylil cislo JIRA issue a uz je neskoro, nic sa s tym neda spravit. Vtedy ma mrzi, ze som clovek :)

mercurial na to ma feature ktora je natolko specialna ze ani nie je v beznom release :), ak som to pochopil spravne je to nieco ako meta-verzionovanie: http://mercurial.selenic.com/wiki/EvolveExtension

Refactor until you feel you are one step behind the solution you want. Avoid your comfort zone. And while you might see extractions that would probably get you to a better design, don't apply them until you see the need two or three different times. Remember that duplication is cheaper than the wrong abstraction. The best refactors will then naturally arise from the repeated inconveniences, instead of from unbacked ideas of what could potentially be better.