Skip to main content

Work laptop

For my projects I require very strong machine. After reviewing the laptops from Dell, Lenovo, Apple, HP, Toshiba etc. I finally made a choice - Asus G75VX (the link is to the G75VW model, no link to VX model on the official Web site):


Specifications:

Asus G75VX-T4153H


Series
ASUS G75VX
Operating System
MS Windows 8 64-bit
CPU
Intel Core Processor i7-3630QM (2.4GHz/3.3, 6Mb)
Chipset
Mobile Intel HM77 Express Chipset
Memory
32GB DDR3 SDRAM (1600 MHz)
Hard Drive
256GB Solid State Drive (SSD) + 1TB 5400RPM
Optical Drive
BluRay Writer
Display
17.3" (1920x1080 Resolution)
Display Type
FHD
LED Backlight
ZBD Guarantee
Graphics
NVIDIA GeForce GTX 670M 3GB DDR5
Wireless
802.11b/g/n
Bluetooth
4.0
Webcam
720p
Expansion Slots
3 in 1 Card Reader (MS/SD/MMC)
I/O Ports
4 USB 3.0, 1x Microphone-in jack;1x Headphone-out jack (S/PDIF);1x RJ45 LAN Jack for LAN insert;1x VGA Port (D-Sub);1x HDMI;1x Display Port
Keyboard
ROG illuminated  Chiclet Keyboard (Numeric keypad)
Pointing Device/s
Touchpad
Battery
8 Cell 5200mAh
Power
180W AC Adapter
Dimensions
41.5 W x 32.0 D x 1.70 - 5.2 H cm
Weight
4.50 kg
Warranty
2 Year Global

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi