Skip to main content

Home/ InnoDev/ Group items tagged lead

Rss Feed Group items tagged

Juraj Visnovsky

Adopt New Tech Before Everyone Else - 2 views

  •  
    One glaring constant in your career is that the technology you'll use for your craft will regularly change. When this happens you have a choice: hold on to what you know or become an early adopter, exploring the next thing. It's the early adopters who take the early lead towards mastering the newest tools will have a greater chance of wining the race for new client opportunities.
Juraj Visnovsky

Image Tragick - 0 views

  •  
    There are multiple vulnerabilities in ImageMagick, a package commonly used by web services to process images. One of the vulnerabilities can lead to remote code execution (RCE) if you process user submitted images. The exploit for this vulnerability is being used in the wild.
Peter Vojtek

Elektrobicykel s autorizaciou odtlackom prstom - 3 views

  •  
    You can choose that a certain finger starts the bike in a certain mode. Your thumb can lead you the Street Mode, while your middle-finger will activate the speed-mode. The owner can limit rights to other users - you can lend your bike to your friend and limit his riding-time and speed.
Peter Vojtek

The Software Team Leader Manifesto - 2 views

  •  
    narazil som na toto hodinove video, a napriek tomu ze neznasam videa, toto povazujem za velmi prinosne. pre mna to je zhrnutie pocitov a nazorov ktore som intuitivne "tusil", ale v tom videu ich ten chlapik povie nahlas a je to pekne explicitne vyslovene a presvedcive.
Juraj Visnovsky

Idioms that lead to faster running Ruby code - 0 views

  •  
    Pomocka pri pisani rychlejsieho Ruby kodu. V ramci moznosti... :o)
Juraj Visnovsky

has_many considered harmful - 2 views

  •  
    has_many is an anti-pattern which leads straight to monolithic applications. However, a simple inversion can free us from its grasp. What is the first model you added to your application? Probably User, right? So, once you wrote user.rb and its corresponding tests, and committed it - why did you ever open that file up again to tell it about something that it did not need to know existed? Rails keeps you from reopening user.rb if you add a column to the User table, and this is good, right? So why, when you added a Posts table far away, did you open up User again to make it aware of Posts? Did the definition of being a user change? Did you did not realize you were violating the Open-Closed Principle, one of the 5 principles of SOLID design? Somewhere inside I bet you knew it felt dirty to keep opening up User and making it aware of things that it had been blissfully unaware of.
1 - 6 of 6
Showing 20 items per page