Looking for:
GitHub – MorganGeek/bookmarks: +5K awesome resources for geeks and software crafters.
No more status report e-mails. Have to be a killer app, or they need one. Always have an extension language and a plug-in system mods. Points for successful prioritization. As your company grows you have to get used to the fact that you cannot be involved in all the aspects of the company. Add items to your wishlist, and Deku Deals sends you an email as soon as they go on sale.
– Usa staffing login onboarding 365chess – usa staffing login onboarding 365chess
Picture some serious non-fiction tomes. Take a look at the Super-Quick Demo to see how it works in under 60 seconds. The VPN provider can see all your traffic, and do with it what they want – including logging. Read the contribution guidelines. Command Line Heroes – podcast about the people who transform technology from the command line up. People notice. Points for efficiency and productivity.
Usa staffing login onboarding 365chess – usa staffing login onboarding 365chess.
No more status report e-mails. Just stop doing that stuff, and get rid of anyone who can’t cope. Nothing terrible will happen. You need to change the culture the hard way, or replace people as necessary until the culture works. If you fail – you learn, if you succeed — even better. And never forget the importance of communication. Everyone would have saved so much time, if only we communicated first and wrote code only after. Improvement is something we should do all the time, not once every two weeks in a retrospective.
When a problem emerges, don’t wait. Fix it. Do everything you can to instill a culture of continuous improvement throughout the organization. An improvements board is one way to do that in the small.
Don’t lose crap, ever. Passwords, dates, files, emails, notes, links, whatever. Be easy to reach and quick to respond but protect your focused deep work time. If you said you’ll do it, then freaking do it, no matter how tiny it is.
People notice. No one will take you seriously. To a very large extent, your productivity is a result of what you choose to work on. Keep things perceived as easy out of that list. When you can’t, postponing an “easy” thing can make it both “harder” and smaller. So I believe, having authored a lot of code that went down the toilet, that you don’t get productive by working as much as by not working — not on stuff that is likely to get thrown away.
You know that thing where you keep asking the new person to speak up when they need help, and they never do? You keep begging them to ask more questions, and they say they will, then nothing? There are at least reasons as to why you may need to contact the owner of a vehicle. Thanks to WappyWap mobile application, downloadable on all platforms, as well as a web version, it will now be possible to contact the owner of any car, van, truck or motorcycle through its license plate. A lot of people especially entrepreneurs are so obsessed with how fast they will become successful that they will sacrifice their mental health in order to constantly push themselves.
Look for jobs that excite you, for jobs you think you can do with just a little ramp-up time. And then apply for those jobs, knowing that most of them will ignore you—but it only takes one yes to get an exciting new job, and an exciting new opportunity to learn new skills. Whenever you feel yourself with too much work to do, go back and apply these principles: underpromise, limit your own time, prioritize ruthlessly.
No, instead, it talks about cooperation. Because a VPN in this sense is just a glorified proxy. The VPN provider can see all your traffic, and do with it what they want – including logging. There is no simple solution to the problem of privacy, because privacy itself is a solution to societal challenges that are in constant flux.
If the apparatus of total surveillance that we have described here were deliberate, centralized, and explicit, a Big Brother machine toggling between cameras, it would demand revolt, and we could conceive of a life outside the totalitarian microscope. Multitasking, in short, is not only not thinking, it impairs your ability to think. Thinking means concentrating on one thing long enough to develop an idea about it.
Developing your own ideas. In short, thinking for yourself. You simply cannot do that in bursts of 20 seconds at a time, constantly interrupted by Facebook messages or Twitter tweets, or fiddling with your iPod, or watching something on YouTube.
Points for successful prioritization. Points for efficiency and productivity. Points for doing work that matters. No points for busy. People have a natural tendency to avoid decisions, preferring to stay in a fantasy land where the chance of failure is zero.
Making plans helps free up mental space for whatever we are doing right now, allowing us to be more efficient in the long term.
Skip to content. Star Permalink master. Branches Tags. Could not load branches. Could not load tags. This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. Raw Blame. Edit this file. Open with Desktop View raw View blame. I choose GitHub to list my findings and bookmarks in a central location for productivity, to avoid losing my findings, and also to share them with the world. All about performance Adam Pittenger – Love what you build.
Build what you love. R0ml – Why are objects so hard to debug? John D. Kenneth N. Lodding, Nasa – Hitchhiker’s Guide to Biomorphic Software The natural world may be the inspiration we need for solving our computer problems. Prep for the system design interview. Gojko Adzic – Splitting user stories — the hamburger method Bill Wake – Evolution, Cupcakes, and Skeletons: Changing Design Fagner Brack – Why Small Modules Matter Big projects are what, if not the composition of small pieces Joe Forshaw – Message-Oriented Programming Simon Brown – Today’s software developers are the ivory tower architects of tomorrow The C4 model – The C4 model for software architecture : Context, Containers, Components and Code Ben Northrop – The Reality of Reuse we’re hard-wired to want to make decisions quickly and we take too many shortcuts Joshua Kerievsky – Sufficient Design we need high design quality for stuff that is critical to our products and less design quality for stuff that isn’t critical.
When Cleaning Is Not Enough Clean frequently and remodel occasionally to produce an excellent design. Centralized Wins. Decentralized Loses. Dustin Barnes – Increasing Software Transparency with Lightweight Architectural Decision Records Vijini Mallawaarachchi – 10 Common Software Architectural Patterns in a nutshell Kai Niklas – 38 Actions and Insights to Become a Better Software Architect Architectural Katas – small-group exercises for practicing being software architect The C4 model – consists of a hierarchical set of software architecture diagrams for context, containers, components, and code.
Alberto Brandolini – Introducing Event Storming EventStorming is a workshop format for quickly exploring complex business domains. Outsource Undifferentiated Heavy Lifting 3. Create enduring competitive advantage Sandi Metz – The Wrong Abstraction duplication is far cheaper than the wrong abstraction prefer duplication over the wrong abstraction Gordon Brander – Second System Syndrome a simple system is doomed to be replaced by an excessively abstract, over-engeered, or bloated successor.
The Architecture of Open Source Applications – Useful resources of information, because most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another’s mistakes rather than building on one another’s successes. Software that is limited, but simple to use, may be more appealing to the user and market than the reverse. Sane software manifesto – While very opinionated, it’s an interesting list of practices for software developers, about safe code, collaboration, reproducible builds, modularity, architecture, testability, etc.
Collaboration that creates incoherence is easy. You all just do whatever you want. Equally, collaboration on things that are not complex is easy. You can all see whether the log has been chopped or not, there is limited room for debate. This makes it much more likely the outcome will be coherent. But the price we pay is having to handle the complexity of the entire challenge all at once. Have a command shell. Always have an extension language and a plug-in system mods. Are introspective.
Have to be a killer app, or they need one. You need to change the culture the hard way, or replace people as necessary until the culture works. If you fail – you learn, if you succeed — even better. And never forget the importance of communication. Everyone would have saved so much time, if only we communicated first and wrote code only after. Improvement is something we should do all the time, not once every two weeks in a retrospective.
When a problem emerges, don’t wait. Fix it. Do everything you can to instill a culture of continuous improvement throughout the organization. An improvements board is one way to do that in the small. Don’t lose crap, ever. Passwords, dates, files, emails, notes, links, whatever. Be easy to reach and quick to respond but protect your focused deep work time. If you said you’ll do it, then freaking do it, no matter how tiny it is.
People notice. No one will take you seriously. To a very large extent, your productivity is a result of what you choose to work on. Keep things perceived as easy out of that list. When you can’t, postponing an “easy” thing can make it both “harder” and smaller. So I believe, having authored a lot of code that went down the toilet, that you don’t get productive by working as much as by not working — not on stuff that is likely to get thrown away.
You know that thing where you keep asking the new person to speak up when they need help, and they never do? You keep begging them to ask more questions, and they say they will, then nothing? There are at least reasons as to why you may need to contact the owner of a vehicle. Thanks to WappyWap mobile application, downloadable on all platforms, as well as a web version, it will now be possible to contact the owner of any car, van, truck or motorcycle through its license plate.
A lot of people especially entrepreneurs are so obsessed with how fast they will become successful that they will sacrifice their mental health in order to constantly push themselves.
Look for jobs that excite you, for jobs you think you can do with just a little ramp-up time. And then apply for those jobs, knowing that most of them will ignore you—but it only takes one yes to get an exciting new job, and an exciting new opportunity to learn new skills. Whenever you feel yourself with too much work to do, go back and apply these principles: underpromise, limit your own time, prioritize ruthlessly.
No, instead, it talks about cooperation. Skip to content. Star This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. Branches Tags. Could not load branches. Could not load tags. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio Code Your codespace will open once ready.
Latest commit. Git stats 3, commits. Failed to load latest commit information. View code. I choose GitHub to list my findings and bookmarks in a central location for productivity, to avoid losing my findings, and also to share them with the world. All about performance Adam Pittenger – Love what you build. Build what you love. R0ml – Why are objects so hard to debug? John D. Kenneth N. Lodding, Nasa – Hitchhiker’s Guide to Biomorphic Software The natural world may be the inspiration we need for solving our computer problems.
Prep for the system design interview. Gojko Adzic – Splitting user stories — the hamburger method Bill Wake – Evolution, Cupcakes, and Skeletons: Changing Design Fagner Brack – Why Small Modules Matter Big projects are what, if not the composition of small pieces Joe Forshaw – Message-Oriented Programming Simon Brown – Today’s software developers are the ivory tower architects of tomorrow The C4 model – The C4 model for software architecture : Context, Containers, Components and Code Ben Northrop – The Reality of Reuse we’re hard-wired to want to make decisions quickly and we take too many shortcuts Joshua Kerievsky – Sufficient Design we need high design quality for stuff that is critical to our products and less design quality for stuff that isn’t critical.
When Cleaning Is Not Enough Clean frequently and remodel occasionally to produce an excellent design. Centralized Wins. Decentralized Loses. Dustin Barnes – Increasing Software Transparency with Lightweight Architectural Decision Records Vijini Mallawaarachchi – 10 Common Software Architectural Patterns in a nutshell Kai Niklas – 38 Actions and Insights to Become a Better Software Architect Architectural Katas – small-group exercises for practicing being software architect The C4 model – consists of a hierarchical set of software architecture diagrams for context, containers, components, and code.
Alberto Brandolini – Introducing Event Storming EventStorming is a workshop format for quickly exploring complex business domains. Outsource Undifferentiated Heavy Lifting 3. Create enduring competitive advantage Sandi Metz – The Wrong Abstraction duplication is far cheaper than the wrong abstraction prefer duplication over the wrong abstraction Gordon Brander – Second System Syndrome a simple system is doomed to be replaced by an excessively abstract, over-engeered, or bloated successor.
The Architecture of Open Source Applications – Useful resources of information, because most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history.
As a result, they repeat one another’s mistakes rather than building on one another’s successes. Software that is limited, but simple to use, may be more appealing to the user and market than the reverse. Sane software manifesto – While very opinionated, it’s an interesting list of practices for software developers, about safe code, collaboration, reproducible builds, modularity, architecture, testability, etc. Collaboration that creates incoherence is easy.
You all just do whatever you want. Equally, collaboration on things that are not complex is easy. You can all see whether the log has been chopped or not, there is limited room for debate. This makes it much more likely the outcome will be coherent. But the price we pay is having to handle the complexity of the entire challenge all at once. Have a command shell. Always have an extension language and a plug-in system mods.
Are introspective. Have to be a killer app, or they need one. Unix Sheikh – Is the madness ever going to end? Ben Hoyt – The small web is beautiful Fewer moving parts.
Small software is faster. Reduced power consumption. The light, frugal aesthetic. Thingiverse – sharing of user-created digital design files to be used for 3D printers, laser cutters, milling machines and many other technologies.
Share in open source or sell your 3D print files. Massive JavaScript libraries, countless client-side queries and overly complex frontend frameworks are par for the course these days. This allows one to have the shared misery of knowing you are not the only one tracking down a bad pointer at the th hour.
The annual event occurs during a week in early March. You can use whatever programming language or tools that you wish. Seth Godin – Folk typography Why is type getting so bad? Goomics – Comics about life at Google INeedCoffee – Life is Coffee Comics Thingiverse – sharing of user-created digital design files to be used for 3D printers, laser cutters, milling machines and many other technologies. Take a look at the Super-Quick Demo to see how it works in under 60 seconds.
Comentários