mit Update: Search Continues for Missing Grand Canyon Hiker in Limited Mode By www.nps.gov Published On :: Mon, 19 Jun 2017 04:30:00 EST After three days of extensive searching, the National Park Service (NPS) will reduce the scale of the search for missing hiker, 72 year old Raffat "Ralph" Nasser-Eddin of Los Angeles, CA and Lebanon. https://www.nps.gov/grca/learn/news/missing-hiker-update.htm Full Article
mit South Rim Roads Improvement Project to begin in Early January at Hermit Road Interchange By www.nps.gov Published On :: Sat, 16 Dec 2017 07:50:00 EST Construction will begin as early as January 2, 2018 at the Hermit interchange to resurface and improve the Hermit Road and Village Loop intersection. https://www.nps.gov/grca/learn/news/2018-south-rim-roads-improvement.htm Full Article
mit Grand Canyon National Park to Open 2019 Noncommercial River Trip Permit Lottery By www.nps.gov Published On :: Thu, 01 Feb 2018 09:24:00 EST On Thursday, February 1, 2018 the National Park Service will begin accepting applications for noncommercial river trip permits to raft the Colorado River through Grand Canyon National Park. The permits are for specific launch dates within calendar year 2019. https://www.nps.gov/grca/learn/news/2019-river-lottery-open.htm Full Article
mit Grand Canyon National Park Returns to Level 1 Water Conservation; Limited Water on Trails Due to Seasonal Shut-off By www.nps.gov Published On :: Wed, 31 Oct 2018 07:09:00 EST Following a series of breaks in the Transcanyon Waterline earlier this month, Grand Canyon National Park now has enough water in storage to scale back to Level 1 basic water conservation measures. https://www.nps.gov/grca/learn/news/level-1-water-conservation-seasonal-trail-water.htm Full Article
mit Grand Canyon National Park Noncommercial River Trip Permit Lottery Open for 2020 By www.nps.gov Published On :: Wed, 27 Feb 2019 12:33:00 EST The National Park Service is accepting applications for noncommercial river trip permits to raft the Colorado River through Grand Canyon National Park. The permits are for launch dates within calendar year 2020. https://www.nps.gov/grca/learn/news/2020-noncommercial-river-trip-lottery.htm Full Article
mit Grand Canyon Permit Processing Updates By www.nps.gov Published On :: Mon, 27 Jan 2020 15:47:00 EST Grand Canyon National Park's permit office is temporarily extending the permit processing time periods effective Feb. 14, 2020 until this summer. This change will impact commercial use authorizations (CUA) and special use permit (SUP) applications submitted after Feb. 14. https://www.nps.gov/grca/learn/news/grand-canyon-permit-processing-updates.htm Full Article
mit Grand Canyon National Park Transitions to Limited Services By www.nps.gov Published On :: Thu, 19 Mar 2020 10:22:00 EST Grand Canyon National Park is announcing modifications to operations to implement the latest guidance from the White House, Centers for Disease Control & Prevention (CDC), and local and state authorities. 03/19/2020 https://www.nps.gov/grca/learn/news/grca-np-transitions-to-limited-services-03-19-2020.htm Full Article
mit Sexually transmitted infections surveillance reports By www.health.nsw.gov.au Published On :: Thu, 30 Apr 2020 23:17:15 GMT Full Article
mit NSW lowers age limit for pharmacy flu jabs By www.health.nsw.gov.au Published On :: Mon, 27 Apr 2020 05:42:40 GMT Full Article
mit New Intermittent Fasting Program Shown to Suppress Cancer and Metabolic Disease in Mice and Humans By www.goodnewsnetwork.org Published On :: Sat, 02 May 2020 21:29:20 +0000 This new research has outlined yet another benefit to intermittent fasting—that may arise from the time you eat, rather than what you eat. The post New Intermittent Fasting Program Shown to Suppress Cancer and Metabolic Disease in Mice and Humans appeared first on Good News Network. Full Article Health Science Diet Disease Research Exercise Wellness Fitness NewsCred Medical
mit Polishing the prism: improving wildfire mitigation planning by coupling landscape and social dimensions By www.fs.fed.us Published On :: Wed., 19 Oct 2016 12:00:00 PST Effectively addressing wildfire risk to communities on large multi-owner landscapes requires an understanding of the biophysical factors that influence risk, such as fuel loads, topography, and weather, and social factors such as the capacity and willingness for communities to engage in fire-mitigation activities. Full Article
mit The idiosyncrasies of streams: local variability mitigates vulnerability of trout to changing conditions By www.fs.fed.us Published On :: Wed., 30 Nov 2016 12:00:00 PST Land use and climate change are two key factors with the potential to affect stream conditions and fish habitat. Since the 1950s, Washington and Oregon have required forest practices designed to mitigate the effects of timber harvest on streams and fish. Full Article
mit tech. coord. 2010. Economic modeling of effects of climate change on the forest sector and mitigation options: a compendium of briefing papers By www.fs.fed.us Published On :: Mon, 08 Nov 2010 14:34:00 PST This report is a compilation of six briefing papers based on literature reviews and syntheses, prepared for U.S. Department of Agriculture, Forest Service policy analysts and decisionmakers about specific questions pertaining to climate change. Full Article
mit Rondon admits he would love to return to NUFC By www.chroniclelive.co.uk Published On :: Fri, 8 May 2020 19:48:11 +0000 Salomon Rondon enjoyed a successful season under Rafa Benitez at Newcastle United - and admits he would love to return to Tyneside Full Article Sport
mit FCC Chairman Ajit Pai To Chat With NAB's Gordon Smith For NAB Show Express Welcome Session By www.allaccess.com Published On :: Wed, 06 May 2020 07:49:52 -0700 The in-person NAB SHOW didn't happen due to the pandemic, but the annual chat between FCC Chairman AJIT PAI and NAB Pres./CEO GORDON SMITH will take place anyway as part of the NAB SHOW … more Full Article
mit Brody Smith Joins WKJO (Country Superstars 102.3)/Raleigh, Adds Video Livestream For His Podcast By www.allaccess.com Published On :: Fri, 08 May 2020 08:18:30 -0700 BRODY SMITH, the former iHEARTMEDIA AC KSNE (SUNNY 106.5)/LAS VEGAS. Top 40 WDCG (G105)/RALEIGH, and Top 40 WLDI (WILD 95.5)/W. PALM BEACH personality, has joined TRIANGLE MARKETING … more Full Article
mit Inaugural JBE SummitFest Postponed Until 2021, 2020 Virtual SummitFest Plans Announced By www.allaccess.com Published On :: Wed, 06 May 2020 01:20:01 -0700 Due to the COVID-19 CORONAVIRUS pandemic, JACK BARTON ENTERTAINMENT (JBE) has decided to postpone the first JBE TRIPLE A SUMMITFEST in BOULDER, CO, scheduled for AUGUST 4-7, until AUGUST … more Full Article
mit SummitMedia/Richmond Launches Online Food Drive By www.allaccess.com Published On :: Fri, 01 May 2020 05:54:35 -0700 SUMMITMEDIA's RICHMOND cluster is holding an online food drive TODAY through MAY 31st to support FEED MORE, a food bank serving CENTRAL VIRGINIA. The stations usually hold the "FEED … more Full Article
mit Brian Smith By wordpress.org Published On :: Thu, 28 Mar 2013 14:55:20 +0000 Pulitzer Prize-winning photographer Brian Smith is the luckiest guy on the planet. He’s told Bill Gates exactly what to do for an entire hour, appeared on The X Factor, exhibited at the Library of Congress, dined with the President and... Full Article WordPress.org CMS Photography
mit Canadian Olympic Committee By wordpress.org Published On :: Wed, 27 Nov 2013 15:50:14 +0000 The Canadian Olympic Committee is the official site providing information about coaches and athletes with media and links, and is the private, non-profit organization representing Canadian athletes in the International Olympic Committee (IOC) and the Pan American Games. Full Article Featured WordPress.com VIP Canada CMS International Sports
mit Smithsonian Institution’s National Museum of African Art By wordpress.org Published On :: Fri, 12 Sep 2014 13:12:17 +0000 The Smithsonian Institution’s National Museum of African Art focus is to inspire conversations about the beauty, power, and diversity of African arts and cultures worldwide. Full Article Featured WordPress.org Culture Museum Non-profit Travel
mit MIT Sloan Management Review By wordpress.org Published On :: Wed, 18 Mar 2015 10:29:40 +0000 MIT Sloan Management Review leads the discourse among academic researchers, business executives and other influential thought leaders about advances in management practice that are transforming how people lead and innovate. MIT SMR disseminates new management research and innovative ideas so... Full Article Featured WordPress.org College Education Magazines Newspaper University
mit Guía provisional emitida sobre la atención del accidente cerebrovascular durante la pandemia de COVID-19 By newsroom.heart.org Published On :: Thu, 02 Apr 2020 13:30:00 GMT DALLAS, 2 de abril del 2020 – El cuerpo directivo del Consejo de accidentes cerebrovasculares de la American Heart Association/American Stroke Association publicó la “Guía temporal de emergencia para los Centros de Accidentes Cerebrovasculares de... Full Article
mit Fecha límite de solicitud extendida para becas universitarias y becas escolares de programas escolares de la American Heart Association By newsroom.heart.org Published On :: Tue, 14 Apr 2020 15:00:00 GMT DALLAS, 14 de abril del 2020. La American Heart Association ha extendido la fecha límite para solicitudes de becas individuales y becas escolares ofrecidas a través del Kids Heart Challenge y el American Heart Challenge hasta el 30 de junio. Debido a que... Full Article
mit Effect of a New Rule Limiting Full Contact Practice on the Incidence of Sport-Related Concussion in High School Football Players By feedproxy.google.com Published On :: Fri, 30 Aug 2019 10:43:02 EDT A study to determine if the sport-related concussion (SRC) rate is lower after a rule change that limited the amount and duration of full-contact activities during high school football practice sessions. Full Article
mit Dugout Sports, MLB pitcher Mitch Keller team up to support local firefighters during pandemic By feedproxy.google.com Published On :: Wed, 06 May 2020 12:42:34 PDT CEDAR RAPIDS — Jay Whannel is baseball through and through. He was a star player in high school and college, played briefly in the professional independent leagues. He coached in college and... Full Article Minor League Sports
mit Iowa shifts focus from coronavirus mitigation to management By feedproxy.google.com Published On :: Thu, 07 May 2020 11:17:10 PDT Thanks to enough people following guidelines on social distancing and avoiding large gatherings, Gov. Kim Reynolds said Thursday the state is able to shift its COVID-19 focus from mitigation... Full Article Government
mit Campgrounds reopen in Iowa Friday, see takers despite some health limitations By feedproxy.google.com Published On :: Fri, 08 May 2020 17:34:01 PDT Some Eastern Iowans are ready to go camping. With Gov. Kim Reynolds allowing campgrounds across the state to open Friday, some people wasted little time in heading outdoors. “They’re... Full Article News
mit Limit the characters that display on the_title By feedproxy.google.com Published On :: Wed, 29 Apr 2020 18:08:18 +0000 Ever wanted to display the title of a post somewhere but limit the amount of characters that are shown? For instance, this post has a very long title, and if I were to use <?php echo the_title() ?> it would show as follows: Limit the characters that display on the_title. That may not fit well […] The post Limit the characters that display on the_title appeared first on WPCult. Full Article Tips & Tricks php the_title WordPress
mit SubmitYourContest.com By feedproxy.google.com Published On :: Fri, 01 May 2020 06:08:36 +0000 The post SubmitYourContest.com appeared first on WPCult. Full Article Showcase SubmitYourContest
mit Controlling AirPort Network Access with Time Limits By feedproxy.google.com Published On :: Tue, 09 Apr 2013 13:39:03 +0000 If you own an AirPort base station, you can use the Timed Access feature to control the days and times when users access the Internet. This could come in handy in a variety of situations. For example, if you own a cafe and provide free wi-fi access, you can configure the AirPort to block all access to the Internet when your business is closed. And if you have children, you can set time limits for specific devices in your home. There are two ways to use the timed access feature. You can create a default allow policy to allow all devices to access the Internet at any time, and then specify custom schedules for specific devices. Or you can create a default deny policy to prevent all devices from accessing the Internet according the schedule you specify, and then exempt specific devices by creating custom schedules. Here's how to control AirPort network access with time limits: Open the AirPort Utility application. (It's in Applications → Utilities.) The window shown below appears. Click the AirPort Extreme's icon. The status pop-up window appears. Click Edit. The settings window appears. Select the Network tab. The window shown below appears. Select the Enable Access Control checkbox. Click Timed Access Control. The window shown below appears. Select the Unlimited (default) option. By default, this allows all of the devices connected to your AirPort to access the Internet all day, every day, but you can change this to block Internet access for all devices (except the ones you specify later) during the times you set. If you'd like to limit the days and times that a specific device can access the Internet, click the + button under the Wireless Clients field. The window shown below appears. Enter a name for the device in the Description field. Enter the device's MAC address in the MAC Address field. You can use the following tutorials to find the device's MAC address. How to Find Your Mac's MAC Address How to Find Your iPad's MAC Address How to Find Your iPhone's MAC Address Use the + button under the Wireless Access Times field to create a schedule for this device's Internet access. Once you've added all of your devices and customized the schedules, click Save. Click Update. The AirPort will restart to apply the changes. Congratulations! You have successfully set time limits for the devices connecting to your AirPort network. The schedule you created is effective immediately. Meet Your Macinstructor Matt Cone, the author of Master Your Mac, has been a Mac user for over 20 years. A former ghost writer for some of Apple's most notable instructors, Cone founded Macinstruct in 1999, a site with OS X tutorials that boasts hundreds of thousands of unique visitors per month. You can email him at: matt@macinstruct.com. Full Article
mit Iowa shifts focus from coronavirus mitigation to management By feedproxy.google.com Published On :: Thu, 07 May 2020 11:17:10 PDT Thanks to enough people following guidelines on social distancing and avoiding large gatherings, Gov. Kim Reynolds said Thursday the state is able to shift its COVID-19 focus from mitigation strategies to managing the impact on Iowans.Even as the state Department of Public Health reported 655 new cases and 12 more deaths, Reynolds said Iowa is successfully dealing with the disease, which has claimed 231 lives in less than two months.As she continues to allow more businesses to partially reopen, Reynolds said credit goes to Iowans for responding to targeted mitigation efforts to slow the spread of COVID-19 and prevent health care systems from being overwhelmed.“I’m proud to say that Iowans do what they always do and they responded,” she said during her daily news conference Thursday. “So since we’ve kind of really accomplished what we were trying to do ... now we have shifted our focus from mitigation and resources to managing and containing virus activity as we begin to open Iowa back up.”That means that beginning Friday, dentists may resume providing services and campgrounds, drive-in movie theaters, tanning facilities and medical spas all may reopen statewide, but with restrictions.Her latest proclamation also relaxes mitigation strategies in the 22 counties that remain under more strict orders because the virus is more widespread there. In those 22 counties, beginning Friday, malls and retail stores may reopen provided they operate at no more than 50 percent of capacity and take other steps, and fitness centers may reopen for appointments only.In a statement, Coralville’s Coral Ridge Mall said it would reopen under those conditions starting at 11 a.m. Saturday. Shoppers there should expect to see hand-sanitizing stations, frequent cleanings and social distancing directions among other precautions.“As Coral Ridge Mall prepares for this ‘new normal,’ we are thankful for the opportunity to reopen our doors and look forward to welcoming guests back into the shopping center,” senior general manager Monica Nadeau said in a statement.Representatives of another large mall in the Corridor — Lindale Mall in Cedar Rapids — did not return calls Thursday for comment on its plans.The governor’s new guidelines are in effect until May 15 unless she changes them. Data about COVID-19 will continue to drive her decisions about reopening the state economy “in a responsible manner,” Reynolds said.“Just as we can’t stop the virus completely, we also can’t keep businesses closed and our life restricted indefinitely,” she said.According to the state’s newest version of its COVID-19 dashboard, at coronavirus.iowa.gov, 31 people were admitted to hospitals in the previous 24 hours, bringing the total to 417 with 107 on ventilators and 151 in intensive care.There have been 66,427 people tested, with 16.6 percent of them testing positive for a total of 11,059. Another 4,266 people are recovering.Although the number of Iowans dying and becoming infected with COVID-19 continues to increase, Reynolds, who met Wednesday with President Donald Trump and his coronavirus advisers, said she is proud of the state’s efforts.“We are leading, and we’re leading by example. And we’re going to continue to lead,” she said. “We are in a pandemic. We have a rapidly changing environment. We are reacting and being proactive.”That includes testing at hot spots, such as meatpacking plants, “so of course, our positive cases are going to increase,” she said.Iowa’s COVID-19 response may not be perfect, Reynolds said, “but I think we’re doing everything we can to really take care of Iowans in a responsible way (and) also to get the economy up and going so Iowans can get back to work and we can do everything we can to get our life somewhat back to normal.”Just as it will be up to business owners, churches and others to decide whether they are comfortable partly reopening, Reynolds said it will be up to Iowans to decide whether they want to venture out.“Iowan to need to make those individual choices themselves,” Reynolds said. “They need to apply personal responsibility, take into account where they’re going, what they’re doing.”Reynolds also said Trump asked Iowa Director of Public Health Caitlin Pedati to be a member of his coronavirus task force after Pedati briefed the president on Iowa’s efforts to mitigate COVID-19. However, later Thursday, White House officials told Bloomberg News Pedati is not “officially” a member of the task force, but may be consulted. The governor’s office declined to comment.The Federal Emergency Management Agency has announced $78 million for Iowa in reimbursement for costs associated with COVID-19. The funds will cover 75 percent of the eligible cost of personal protective gear and medical supplies and equipment during May and June.In addition, FEMA has obligated $44 million for similar costs in March and April; $17 million to cover deployment of the National Guard; $4 million to reimburse the state for costs associated with its response; and $4.2 million for the use of up to 20 beds at U.S. Department of Veterans Affairs facilities.Comments: (319) 398-8375; james.lynch@thegazette.com Full Article Government
mit Campgrounds reopen in Iowa Friday, see takers despite some health limitations By feedproxy.google.com Published On :: Fri, 08 May 2020 17:34:01 PDT Some Eastern Iowans are ready to go camping.With Gov. Kim Reynolds allowing campgrounds across the state to open Friday, some people wasted little time in heading outdoors.“They’re already starting to fill up,” said Ryan Schlader of Linn County Conservation. “By about 7 this morning, we had a dozen at Squaw Creek Park. People were coming in bright and early to camp. We’re not surprised.”Schlader said Linn County Conservation tried to have the campgrounds open at the county’s Squaw Creek, Morgan Creek and Pinicon Ridge parks at 5 a.m. Friday. He expected all of them would be busy.“I think people were ready to go,” he said.Lake Macbride State Park in Johnson County didn’t see quite as much of a rush for campsites, park manager Ron Puettmann reported Friday morning, saying he’d had six walk-ins for the park’s 42 campsites.Camping this weekend will be done on a first-come, first-served basis. Sites won’t be available for reservations until next week, though online reservations can be made now, Puettmann said. “I’m quite sure people were waiting anxiously to get on,” he said.While Reynolds’ campground announcement came Wednesday, Schlader and Puettmann said they had no issues having the campgrounds ready for Friday. Schlader said county staff have been in touch with the Iowa Department of Natural Resources and other county conservation boards to discuss protocols for reopening to ensure a safe experience for campers and employers.“We anticipated at some point the order would be lifted,” Schlader said. “We were anticipating maybe May 15. The campgrounds were in good shape and ready to go.” For now, camping comes with some limitations:• Campers can camp only in a self-contained unit with a functioning restroom, such as a recreational vehicle. • Shower houses with restrooms will remain closed for the time being. • Campsites are limited to six people unless they are from the same household.• No visitors are allowed at the campsites.Puettmann said staffers and a DNR officer will be on hand to make sure guidelines are followed, but he didn’t anticipate enforcement would be an issue.“For the most part, we’re going to allow people to police themselves,” he said. It’s hard to gauge demand, Schlader said. The weather isn’t yet deal for camping, and some people might not be ready to camp, given the continuing coronavirus.“There is a lot of uncertainty,” he said. “Do people feel like they need to get out and enjoy a camping experience within their own campsite, or do people still feel under the weather and think it’s not a good idea for my family to go right now? ... We just want this to be an option for people.” Comments: (319) 339-3155; lee.hermiston@thegazette.com Full Article News
mit Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue By feedproxy.google.com Published On :: Thu, 27 Feb 2020 00:00:00 -0500 I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch git checkout feature # ... bunch of feature commits ... git push git checkout qa-environment git merge --no-ff --no-edit feature git push # deploy qa-environment to the QA remote environment # ... more feature commits ... # oh. I'm not committing in the feature branch like I should be and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Maybe you prefer git branch -D qa-environment git checkout qa-environment over git checkout qa-environment git reset --hard origin/qa-environment Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.Shorthands for longevityI like to use all possible natively supported shorthands. There are two broad motivations for that.Fingers have a limited number of movements in them. Save as many as possible left late in life.Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot: Bash # USING - git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # now on feature ???? git cherry-pick origin/qa-environment..qa-environment git push git checkout - # now on qa-environment ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # on feature and ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch We cannot use - when cherry-picking a range > git cherry-pick origin/-..- fatal: bad revision 'origin/-..-' > git cherry-pick origin/qa-environment..- fatal: bad revision 'origin/qa-environment..-' and even if we could we'd still have provide the remote's name (here, origin).That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -: # assuming that branch-a has an upstream origin/branch-a > git checkout branch-a > git checkout branch-b > git checkout - > git branch -D - error: branch '-' not found. > git branch -D branch-a > git checkout - error: pathspec '-' did not match any file(s) known to git So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.@{-<n>} is hard to say but easy to fall in love withWe can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref. > git checkout branch-a > git checkout branch-b > git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch branch-a > git checkout branch-c > git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one branch-a Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of git cherry-pick origin/qa-environment..qa-environment We can do git cherry-pick origin/qa-environment..@{-1} Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1}) Bash # USING - AND @{-1} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick origin/qa-environment..@{-1} # ???? git push git checkout - # ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?@{-1} is the ref itself, not the ref's name, we can't do > git cherry-pick origin/@{-1}..@{-1} origin/@{-1} fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.But good news!Do @{u} @{push} @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run. > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard origin/branch-a HEAD is now at <the SHA origin/branch-a is at> we can > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard @{u} # <-- So Cool! HEAD is now at <the SHA origin/branch-a is at> Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example git checkout branch-a@{u} is the branch branch-a pulls from.In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.) Bash # USING - AND @{-1} AND @{u} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick @{-1}@{u}..@{-1} # ???????? git push git checkout - # ???? git reset --hard @{u} # ???? git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch Make the things you repeat the easiest to doBecause these commands are generalized, we can run some series of them once, maybe git checkout - && git reset --hard @{u} && git checkout - or git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout - and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.And keep goingThe GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:@{-<n>}@{push}@{upstream} Full Article Code Front-end Engineering Back-end Engineering
mit Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue By feedproxy.google.com Published On :: Thu, 27 Feb 2020 00:00:00 -0500 I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch git checkout feature # ... bunch of feature commits ... git push git checkout qa-environment git merge --no-ff --no-edit feature git push # deploy qa-environment to the QA remote environment # ... more feature commits ... # oh. I'm not committing in the feature branch like I should be and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Maybe you prefer git branch -D qa-environment git checkout qa-environment over git checkout qa-environment git reset --hard origin/qa-environment Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.Shorthands for longevityI like to use all possible natively supported shorthands. There are two broad motivations for that.Fingers have a limited number of movements in them. Save as many as possible left late in life.Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot: Bash # USING - git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # now on feature ???? git cherry-pick origin/qa-environment..qa-environment git push git checkout - # now on qa-environment ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # on feature and ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch We cannot use - when cherry-picking a range > git cherry-pick origin/-..- fatal: bad revision 'origin/-..-' > git cherry-pick origin/qa-environment..- fatal: bad revision 'origin/qa-environment..-' and even if we could we'd still have provide the remote's name (here, origin).That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -: # assuming that branch-a has an upstream origin/branch-a > git checkout branch-a > git checkout branch-b > git checkout - > git branch -D - error: branch '-' not found. > git branch -D branch-a > git checkout - error: pathspec '-' did not match any file(s) known to git So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.@{-<n>} is hard to say but easy to fall in love withWe can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref. > git checkout branch-a > git checkout branch-b > git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch branch-a > git checkout branch-c > git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one branch-a Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of git cherry-pick origin/qa-environment..qa-environment We can do git cherry-pick origin/qa-environment..@{-1} Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1}) Bash # USING - AND @{-1} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick origin/qa-environment..@{-1} # ???? git push git checkout - # ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?@{-1} is the ref itself, not the ref's name, we can't do > git cherry-pick origin/@{-1}..@{-1} origin/@{-1} fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.But good news!Do @{u} @{push} @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run. > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard origin/branch-a HEAD is now at <the SHA origin/branch-a is at> we can > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard @{u} # <-- So Cool! HEAD is now at <the SHA origin/branch-a is at> Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example git checkout branch-a@{u} is the branch branch-a pulls from.In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.) Bash # USING - AND @{-1} AND @{u} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick @{-1}@{u}..@{-1} # ???????? git push git checkout - # ???? git reset --hard @{u} # ???? git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch Make the things you repeat the easiest to doBecause these commands are generalized, we can run some series of them once, maybe git checkout - && git reset --hard @{u} && git checkout - or git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout - and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.And keep goingThe GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:@{-<n>}@{push}@{upstream} Full Article Code Front-end Engineering Back-end Engineering
mit How to Set a Default Commit Message By feedproxy.google.com Published On :: Mon, 02 Mar 2020 15:23:46 +0000 Having a default commit message is really useful for a number of reasons: It can formalize your commit messages It serves as a good reminder for the information you should add to your commit message, like issue number If you set it to “Drunk AF, don’t accept this” To set a default commit message on […] The post How to Set a Default Commit Message appeared first on David Walsh Blog. Full Article git Quick Tips Shell
mit Upper Yosemite Falls & Half Dome Moonbow By feedproxy.google.com Published On :: Tue, 16 May 2017 00:01:58 +0000 This past week was the optimal time to photograph moonbows in Yosemite Valley. I revisited photographing the moonbow at Upper Yosemite Falls as I had last year, but this time there was considerable more water and as a result the moonbow (rainbow by moonlight) was more easily seen. It was considerably larger, more vivid in color and wider arching. Conditions were great and at times a little too good as the 3 cameras I set up were completely drenched. If you’d like to read about what it took to get this photo be sure to check out my last blog post, Upper Yosemite Falls Moonbow – Getting The Shot, as it goes into a lot of detail about the hike and the challenges I faced. If you’re curious about gear and settings this was taken with a Canon 5D Mark IV and Canon 11-24mm f/4 lens. Settings were ISO 640, 15 seconds at f/4. Full Article Astro-landscape California Daily Photo Landscape Locations Photography Yosemite Moonbow Nature Night Photography Upper Yosemite Falls
mit Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue By feedproxy.google.com Published On :: Thu, 27 Feb 2020 00:00:00 -0500 I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch git checkout feature # ... bunch of feature commits ... git push git checkout qa-environment git merge --no-ff --no-edit feature git push # deploy qa-environment to the QA remote environment # ... more feature commits ... # oh. I'm not committing in the feature branch like I should be and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Maybe you prefer git branch -D qa-environment git checkout qa-environment over git checkout qa-environment git reset --hard origin/qa-environment Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.Shorthands for longevityI like to use all possible natively supported shorthands. There are two broad motivations for that.Fingers have a limited number of movements in them. Save as many as possible left late in life.Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot: Bash # USING - git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # now on feature ???? git cherry-pick origin/qa-environment..qa-environment git push git checkout - # now on qa-environment ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # on feature and ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch We cannot use - when cherry-picking a range > git cherry-pick origin/-..- fatal: bad revision 'origin/-..-' > git cherry-pick origin/qa-environment..- fatal: bad revision 'origin/qa-environment..-' and even if we could we'd still have provide the remote's name (here, origin).That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -: # assuming that branch-a has an upstream origin/branch-a > git checkout branch-a > git checkout branch-b > git checkout - > git branch -D - error: branch '-' not found. > git branch -D branch-a > git checkout - error: pathspec '-' did not match any file(s) known to git So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.@{-<n>} is hard to say but easy to fall in love withWe can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref. > git checkout branch-a > git checkout branch-b > git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch branch-a > git checkout branch-c > git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one branch-a Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of git cherry-pick origin/qa-environment..qa-environment We can do git cherry-pick origin/qa-environment..@{-1} Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1}) Bash # USING - AND @{-1} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick origin/qa-environment..@{-1} # ???? git push git checkout - # ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?@{-1} is the ref itself, not the ref's name, we can't do > git cherry-pick origin/@{-1}..@{-1} origin/@{-1} fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.But good news!Do @{u} @{push} @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run. > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard origin/branch-a HEAD is now at <the SHA origin/branch-a is at> we can > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard @{u} # <-- So Cool! HEAD is now at <the SHA origin/branch-a is at> Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example git checkout branch-a@{u} is the branch branch-a pulls from.In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.) Bash # USING - AND @{-1} AND @{u} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick @{-1}@{u}..@{-1} # ???????? git push git checkout - # ???? git reset --hard @{u} # ???? git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch Make the things you repeat the easiest to doBecause these commands are generalized, we can run some series of them once, maybe git checkout - && git reset --hard @{u} && git checkout - or git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout - and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.And keep goingThe GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:@{-<n>}@{push}@{upstream} Full Article Code Front-end Engineering Back-end Engineering
mit Ramit Sethi: Money + Other Ways to Live Rich By feedproxy.google.com Published On :: Wed, 31 Jul 2019 13:15:09 +0000 Ditch the idea of yourself as a starving artist. Throw away the notion that you’re doomed to be another poor creative soul. My long time pal Ramit Sethi is back on the show to remind us we need to get back on track to building and living a rich life. And believe me, that doesn’t have to mean cutting back the lattes. Ramit has been on the show a few times, but if you haven’t caught up yet, let me fill you in. Ramit Sethi is the author of the NYT bestseller “I Will Teach You To Be Rich” and writes for over 500,000 monthly readers on his website, iwillteachyoutoberich.com. It’s one of my favorite go-to finance resources covering psychology, personal finance, careers, and entrepreneurship. No one has single-handedly given me better insight into the business side of art, than Ramit. Ramit has updated & expanded 2nd edition of his book and joined me for a LIVE studio conversation on money confessions. In this episode we get into: A rich life isn’t only about save money, it’s about defining & prioritizing the things you love the most. It’s one thing to manage our own personal finances but navigating that with […] The post Ramit Sethi: Money + Other Ways to Live Rich appeared first on Chase Jarvis Photography. Full Article chasejarvisLIVE Podcast author finance money negotiating personal finance ramit sethi
mit Finance Fireside Chat with Ramit Sethi By feedproxy.google.com Published On :: Mon, 20 Apr 2020 13:13:53 +0000 In this episode I’m chatting with my long time friend and financial guru, Ramit Sethi. Ramit has been on the show a number of times, and this time we’re connecting virtually from our living rooms during the quarantine. Of course we get into finances during these uncertain times, but more importantly: adaptation and resilience. Over the years, no one has single-handedly given me better insight about the business side of art than the New York Times bestselling author, Ramit Sethi. Take a listen and let us know what you think. Enjoy! This episode was part of CreativeLive TV, a brand-new, free, 24/7 variety show, live-streamed from the very casual living rooms, studios, and kitchen tables of our worldwide community of legendary creators. You can expect musical performances, Q&As, cooking, spoken word, drawing, and more – featuring many of our favorite personalities – all in a safe, virtual space full of joy, shared experiences, and connection via live, interactive chat. The schedule and upcoming broadcasts can be seen at http://creativelive.com/tv FOLLOW RAMIT: instagram | twitter | website Listen to the Podcast Subscribe Watch the Episode This podcast is brought to you by CreativeLive. CreativeLive is the world’s largest hub […] The post Finance Fireside Chat with Ramit Sethi appeared first on Chase Jarvis Photography. Full Article chasejarvisLIVE Podcast creativity entrepreneurship finance money resilience
mit Make It Til You Make It with Owen Smith By feedproxy.google.com Published On :: Wed, 29 Apr 2020 13:00:36 +0000 If you happened to come across a Youtube video I put out not too long ago featuring Owen Smith, you’ll know the backstory how we connected for this episode of the Chase Jarvis LIVE show. Of course, we hoped to meet in person, but for now we’re coming LIVE to you from our living rooms. Owen Smith is a comedian, actor, writer, and the creator of a new YouTube show: Notebooks. He has performed stand-up on Conan, Colbert and is a regular at the Comedy Store Hollywood and Comedy Cellar in New York. He’s written for shows such as ABC’s Black•ish, Survivor’s Remorse (Starz), The Arsenio Hall Show, The ESPY’s (on ESPN with Drake and ABC with Joel McHale), The Guy’s Choice Awards, Whitney(NBC), Deon Cole’s Black Box (TBS), Are We There Yet (TBS), and Everybody Hates Chris. In this episode, we explore Owen’s Notebook project (so good!) and go deep into growing and developing as an artist, putting work into the world, learning to trust your instincts, finding the right time/place for your ideas, and so much more. Definitely check out his new show Notebooks. So relatable and funny for any creator. Enjoy! FOLLOW OWEN: instagram | twitter | […] The post Make It Til You Make It with Owen Smith appeared first on Chase Jarvis Photography. Full Article chasejarvisLIVE Podcast actor art business comedian creativity producer standup comedy writer
mit Hope in a Sea of Endless Calamity with Mark Manson By feedproxy.google.com Published On :: Wed, 06 May 2020 13:05:54 +0000 Today on the show, I’m chatting with New York Times bestselling author Mark Manson. He is the #1 New York Times Bestselling author of Everything is F*cked and The Subtle Art of Not Giving a F*ck, the mega-bestseller that reached #1 in fourteen different countries. Mark also runs one of the largest personal growth websites in the world, MarkManson.net, a blog with more than two million monthly readers and half a million subscribers, making him one of the largest and most successful independent publishers in the world. In this episode, we take a deep dive into the creative process. How to spend your time when you’re trying get comfortable with being uncomfortable. Mark helps bring into focus the up-side that this moment has created for us while also sharing some of the tactics he while quarantined. Enjoy! FOLLOW MARK: instagram | twitter | website Listen to the Podcast Subscribe This podcast is brought to you by CreativeLive. CreativeLive is the world’s largest hub for online creative education in photo/video, art/design, music/audio, craft/maker, money/life and the ability to make a living in any of those disciplines. They are high quality, highly curated classes taught by the world’s top experts — Pulitzer, Oscar, […] The post Hope in a Sea of Endless Calamity with Mark Manson appeared first on Chase Jarvis Photography. Full Article chasejarvisLIVE Podcast anxiety fear happiness personal development self confidence self help
mit Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue By feedproxy.google.com Published On :: Thu, 27 Feb 2020 00:00:00 -0500 I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch git checkout feature # ... bunch of feature commits ... git push git checkout qa-environment git merge --no-ff --no-edit feature git push # deploy qa-environment to the QA remote environment # ... more feature commits ... # oh. I'm not committing in the feature branch like I should be and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Maybe you prefer git branch -D qa-environment git checkout qa-environment over git checkout qa-environment git reset --hard origin/qa-environment Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.Shorthands for longevityI like to use all possible natively supported shorthands. There are two broad motivations for that.Fingers have a limited number of movements in them. Save as many as possible left late in life.Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot: Bash # USING - git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # now on feature ???? git cherry-pick origin/qa-environment..qa-environment git push git checkout - # now on qa-environment ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # on feature and ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch We cannot use - when cherry-picking a range > git cherry-pick origin/-..- fatal: bad revision 'origin/-..-' > git cherry-pick origin/qa-environment..- fatal: bad revision 'origin/qa-environment..-' and even if we could we'd still have provide the remote's name (here, origin).That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -: # assuming that branch-a has an upstream origin/branch-a > git checkout branch-a > git checkout branch-b > git checkout - > git branch -D - error: branch '-' not found. > git branch -D branch-a > git checkout - error: pathspec '-' did not match any file(s) known to git So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.@{-<n>} is hard to say but easy to fall in love withWe can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref. > git checkout branch-a > git checkout branch-b > git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch branch-a > git checkout branch-c > git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one branch-a Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of git cherry-pick origin/qa-environment..qa-environment We can do git cherry-pick origin/qa-environment..@{-1} Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1}) Bash # USING - AND @{-1} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick origin/qa-environment..@{-1} # ???? git push git checkout - # ???? git reset --hard origin/qa-environment git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?@{-1} is the ref itself, not the ref's name, we can't do > git cherry-pick origin/@{-1}..@{-1} origin/@{-1} fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.But good news!Do @{u} @{push} @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run. > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard origin/branch-a HEAD is now at <the SHA origin/branch-a is at> we can > git checkout branch-a Switched to branch 'branch-a' Your branch is ahead of 'origin/branch-a' by 3 commits. (use "git push" to publish your local commits) > git reset --hard @{u} # <-- So Cool! HEAD is now at <the SHA origin/branch-a is at> Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example git checkout branch-a@{u} is the branch branch-a pulls from.In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.) Bash # USING - AND @{-1} AND @{u} git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit - # ???? git push # hack hack hack # whoops git checkout - # ???? git cherry-pick @{-1}@{u}..@{-1} # ???????? git push git checkout - # ???? git reset --hard @{u} # ???? git merge --no-ff --no-edit - # ???? git checkout - # ???? # ready for more feature commits Bash # ORIGINAL git checkout feature # hack hack hack git push git checkout qa-environment git merge --no-ff --no-edit feature git push # hack hack hack # whoops git checkout feature git cherry-pick origin/qa-environment..qa-environment git push git checkout qa-environment git reset --hard origin/qa-environment git merge --no-ff --no-edit feature git checkout feature # ready for more feature commits Switch Make the things you repeat the easiest to doBecause these commands are generalized, we can run some series of them once, maybe git checkout - && git reset --hard @{u} && git checkout - or git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout - and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.And keep goingThe GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:@{-<n>}@{push}@{upstream} Full Article Code Front-end Engineering Back-end Engineering
mit Limiting your options on purpose By feedproxy.google.com Published On :: Mon, 12 Sep 2016 11:55:19 +0000 Being a photographer with some spending money and a bad habit of lusting after gear, I have amassed a lot of photo gear. Due to that I am often carrying at least two lenses and also prefer zoom lenses versus […] Full Article Photo Tip Thoughts
mit Smashing Podcast Episode 15 With Phil Smith: How Can I Build An App In 10 Days? By feedproxy.google.com Published On :: Tue, 05 May 2020 05:00:00 +0000 In this episode of the Smashing Podcast, we’re talking about building apps on a tight timeline. How can you quickly turn around a project to respond to an emerging situation like COVID-19? Drew McLellan talks to Phil Smith to find out. Show Notes CardMedic React Native React Native for Web Expo Apiary Phil’s company amillionmonkeys Phil’s personal blog and Twitter Weekly Update Getting Started With Nuxt Implementing Dark Mode In React Apps Using styled-components How To Succeed In Wireframe Design Mirage JS Deep Dive: Understanding Mirage JS Models And Associations (Part 1) Readability Algorithms Should Be Tools, Not Targets Transcript Drew McLellan: He is director of the full-stack web development studio amillionmonkeys, where he partners with business owners and creative agencies to build digital products that make an impact. Full Article
mit Resonances as Viscosity Limits for Exponentially Decaying Potentials. (arXiv:2005.01257v2 [math.SP] UPDATED) By arxiv.org Published On :: We show that the complex absorbing potential (CAP) method for computing scattering resonances applies to the case of exponentially decaying potentials. That means that the eigenvalues of $-Delta + V - iepsilon x^2$, $|V(x)|leq e^{-2gamma |x|}$ converge, as $ epsilon o 0+ $, to the poles of the meromorphic continuation of $ ( -Delta + V -lambda^2 )^{-1} $ uniformly on compact subsets of $ extrm{Re},lambda>0$, $ extrm{Im},lambda>-gamma$, $arglambda > pi/8$. Full Article
mit Local mollification of Riemannian metrics using Ricci flow, and Ricci limit spaces. (arXiv:1706.09490v2 [math.DG] UPDATED) By arxiv.org Published On :: We use Ricci flow to obtain a local bi-Holder correspondence between Ricci limit spaces in three dimensions and smooth manifolds. This is more than a complete resolution of the three-dimensional case of the conjecture of Anderson-Cheeger-Colding-Tian, describing how Ricci limit spaces in three dimensions must be homeomorphic to manifolds, and we obtain this in the most general, locally non-collapsed case. The proofs build on results and ideas from recent papers of Hochard and the current authors. Full Article
mit Gaussian invariant measures and stationary solutions of 2D Primitive Equations. (arXiv:2005.03339v1 [math.PR]) By arxiv.org Published On :: We introduce a Gaussian measure formally preserved by the 2-dimensional Primitive Equations driven by additive Gaussian noise. Under such measure the stochastic equations under consideration are singular: we propose a solution theory based on the techniques developed by Gubinelli and Jara in cite{GuJa13} for a hyperviscous version of the equations. Full Article
mit Hydrodynamic limit of Robinson-Schensted-Knuth algorithm. (arXiv:2005.03147v1 [math.CO]) By arxiv.org Published On :: We investigate the evolution in time of the position of a fixed number inthe insertion tableau when the Robinson-Schensted-Knuth algorithm is applied to asequence of random numbers. When the length of the sequence tends to infinity, a typical trajectory after scaling converges uniformly in probability to some deterministiccurve. Full Article
mit Imitation Learning for Human-robot Cooperation Using Bilateral Control. (arXiv:1909.13018v2 [cs.RO] UPDATED) By arxiv.org Published On :: Robots are required to operate autonomously in response to changing situations. Previously, imitation learning using 4ch-bilateral control was demonstrated to be suitable for imitation of object manipulation. However, cooperative work between humans and robots has not yet been verified in these studies. In this study, the task was expanded by cooperative work between a human and a robot. 4ch-bilateral control was used to collect training data for training robot motion. We focused on serving salad as a task in the home. The task was executed with a spoon and a fork fixed to robots. Adjustment of force was indispensable in manipulating indefinitely shaped objects such as salad. Results confirmed the effectiveness of the proposed method as demonstrated by the success of the task. Full Article