Search the Community

Am dat peste un raspuns destul de elaborat si bine construit / argumentat si m-am gandit sa il shareuiesc pentru ca poate schimba perspectiva multor useri de p-aici. ( asta daca stiu engleza, desigur ) Argh. No. We really need to stop with the current internet-penis-size mentality around algorithm skills. Yes, testing for basic algorithmic knowledge is an excellent interview shit-test to weed out people that have absolutely no business writing code, but other than that has very little to do with the job of being a software developer. You can spend all bloody day churning out bug-free code with perfect linear time complexity at laser-finger speed, but you might still be a totally shitty developer. We are not athletes or musicians that perform on stage - we are engineers. Our job is to build things. More specifically, (1) build the right things, that (2) work as expected, are (3) easily maintainable for a year or two, and (4) built within reasonable time-frames. This is sort of how I spend my time at work: 40% Talking about WHAT to build. Communication about requirements is by far the most complex, important, and time-consuming aspect of software development. This includes negotiating them, measuring success of them, preventing feature creep from entering the backlog, prioritizing work, how to evolve the architecture instead of just welding the feature on top of it, convincing your product owner that you need to deal with technical debt, and another billion things. If you don't get this right, it will fail your project no matter how good you are at the other stuff. 40% Diving through other peoples code. It is absolutely crucial to be able to absorb other peoples code correctly and quickly, so that you'll make changes that fit (1) in the architecture and (2) don't break existing functionality. It's even more important that you are able to GENERATE code that is easy to understand and absorb, or you'll be a sort of "time cancer" for the team that constantly produces more and more code that wastes more and more time for people to read and understand. I don't care if a programmer has 200 in IQ - if she neglects writing unit tests (the best kind of code documentation), he's GOING to be a detriment for the team, not an asset. 15% Hunting down existing bugs and performance bottlenecks. This has very little to do with algorithmic skills, because humans cannot "look" at 500 000 lines of code and see what is wrong. You need the skillset to methodically narrow down your suspects until you've found the offending method, which usually takes a lot of methodical patience. Once you actually find WHERE the bug/bottleneck resides, it's almost always easy to fix and doesn't require algorithmic genius. 4% Writing actual, new functionality. 1% (and I'm being generous here) Thinking about the time complexity of things. In conclusion: When interviewing, by all means, do a little bit of algorithms just to make sure that the candidate can code, but primarily look at if the person has actually gotten shit done, in a team, in the past.

Developing MIPS Exploits to Hack Routers 1 1. INTRODUCTION 3 2. PREPARING LAB 3 2.1. Running Debian MIPS on QEMU 3 2.2. Cross Compiling for MIPS (bonus section) 4 3. REVERSE ENGINEERING THE BINARY 5 3.1. Obtaining The Target Binary 5 3.2. Getting The Target Running 6 3.3. Setting Up Remote Debugging 8 3.4. Analysing The Vulnerability 9 4. WRITING THE EXPLOIT 10 4.1. Restrictions and Solutions 10 4.2. Finding a Proper ROP Chain 11 4.2. MIPS Shellcoding 14 4.2.1 Writing Fork Shellcode 14 4.2.1 Writing Unlink Shellcode (bonus section) 16 5. CONCLUSION 18 6. References 19 Read more: https://www.exploit-db.com/docs/36806.pdf

Product Description Liquid Story Binder XE is a uniquely designed word processor for professional and aspiring authors, poets, and novelists. Writing software for those who require the editing ability of a commercial text editor as well as a document tracking system. It is for those who want the freedom to create, outline and revise but are tired of losing track of their work Word Processing for Novelists Liquid Story Binder XE is specifically designed for fiction writing. XE includes all the standard features such as spell-checking, thesaurus, smart quotes, templates, font and paragraph styles — everything you need to write your next great novel. Chapter and Scene Based Writing Liquid Story Binder XE can clean and combine many small documents into a single, font-unified manuscript. Use a Chapter Builder to quickly arrange complex scenes. A Multimedia Organizer Sort pictures into Galleries or Storyboards, quickly access custom MP3 playlists, even record yourself reading your latest chapter using a microphone. Pick and Choose Flexible Features Pick and choose the file types that work best for you. Liquid Story Binder never tells you how to write! Flexible file types allow you to use your imagination. Use a Dossier for characters, places or things, or a Builder to preserve important snippets. Organize Your Novel Create a Binder folder and let Liquid Story Binder sort, search and combine your documents. Create the Perfect Working Environment Choose a color scheme that suits your writing style. Save window positions and open files for quick and easy access using Workspaces. Open dozens of windows simultaneously – or just a simple textbox centered in the screen. Full Screen Editing Even though Liquid Story Binder is packed with features, sometimes less is more. Liquid Story Binder XE offers full screen editing, a feature that removes all distractions including menus and title bars. A Typewriter for your PC The Liquid Story Binder Typewriter is the ultimate tool for distraction-free writing. Like a mechanical typewriter, users are prevented from editing previously written text. There are no specific formatting options, no scrolling, deleting, or revisions. The Typewriter tool doesn’t even allow you to use the backspace key. It forces you to write, to move forward, to add new words. It halts the temptation to linger, revise, and correct. Turn Liquid Story Binder into a typewriter for your PC. Advanced Outlining Tools Timelines, Outlines, Mindmaps, Dossiers, Sequences and Storyboards. Liquid Story Binder XE provides the tools you need to plan your next great novel. Mindmapping Liquid Story Binder XE Mindmaps allow you to visually link ideas together using lines and text. A mindmap is a diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central key word or idea. Unlike many mindmapping applications, Liquid Story Binder XE does not use a rigid or pre-designed structure. Users can place items however they choose. Create item colonies, isolated from one another. Index items by color. Change item connections quickly and easily. Try using Mindmaps to create and organize family trees. Journals Liquid Story Binder XE allows you to create multiple Journals. Start a daily writing journal, or go back into the past to tell the story of a fictional character. Combine your Journal entries into a single manuscript. Protect Your Work For every Chapter, Liquid Story Binder XE creates a single, easy-to-access backup file. This backup file contains an entry for each day’s changes. Liquid Story Binder XE also includes a complete Binder backup using ZIP compression. Product homepage here -> Download <-Deal Expires in: EXPIRED!