Laneway Houses and Single Family Homes:
Comments submitted to the City of Vancouver as part of a review of permitting delays and barriers. September 2016.
Presentation to a City of Vancouver workshop looking at ways to support/create 'Missing Middle' housing including duplex, triplex and multi-family house types.
O workshop irá explorar como as práticas ágeis podem ajudar a evitar ou lidar com esse tipo de sistema. Será discutido por que a entrega contínua, TDD e refatoração não são suficientes para ajudar a garantir uma arquitetura limpa. Os resultados vão ajudar os participantes entenderem melhor as práticas e padrões que ajudam a limpar o seu código legado (refactor), bem como manter um código limpo exercitando conceitos como Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftsmanship.
Executive Summary(FOR ALTERNATIVE STUDY PROJECTS)(LIMIT TO 1 O.docxrhetttrevannion
Executive Summary
(FOR ALTERNATIVE STUDY PROJECTS)
(LIMIT TO 1 OR 2 PAGES.. NOTE THE REMAINDER OF THE REPORT PROVIDES OPPORTUNITY TO ELABORATE ON EACH OF THESE AND PROVIDE MORE DETAIL, DIAGRAMS, PHOTOS, ETC.)
(MAKE REFERENCE TO OTHER SECTION OF REPORT AND PLANS AND STUDIES IN APPENDICES)
1. INTRODUCTION:
The introduction is a place where you can draw the reader's attention. Try to make it interesting. Think to yourself, what would interest you or others in the industry? The introduction is also where you provide general information on the project from the owner's perspective. Be sure not to provide information on the project from your perspective or why you are hired. Save that information for the Purpose and Objective section. It is also a chance to let them know a little about the project and why it is so important to you.
2. BACKGROUND:
The Background section is where you give a little about the project history and existing conditions. You can also state why the project or site is where it is from a social, economic, and/or pragmatic perspective. You can use this section as a forward to the Purpose and Objective section. The background on a project usually sets up the purpose of the project and why you were hired.
3. PURPOSE AND OBJECTIVE:
This section is where you tell them why you are here - Why were you hired? What are you planning to do, and what are you expecting to find? Be sure to save your actual findings in the Findings section, but you can give a hint or a tease to your findings here.
4. FINDINGS:
Here is the opportunity to provide your brief findings. The operative word here is “brief” - and be sure to keep it interesting. Think to yourself - what would the owner be interested in finding? The owner hired you for several reasons, but what are his or her main reason for hiring you? Get into the owner’s head. Since you may have been hired for several different reasons - or disciplines, you may need subsections in this area to address each of the different disciplines. Be sure to only list your findings and NOT your opinions. Save your opinions for the Recommendations section.
5. RECOMMENDATOINS:
The Recommendations is where you let the owner know what your thoughts are. This is your chance to give them advice on what they should do with what you have found (and listed in the Findings section). Since this is just the Executive Summary, limit your recommendations to major decisions that will need to be made by the owner. The owner hired you for a specific reason and may be at a turning point. The owner needs to know what direction they should take after reading the executive summary. In other words, do NOT expect the owner to read every study or recommendation in the subsequent documents. (Secret tip: It is always a good idea to discuss major recommendations with the owner verbally in advance of your submittal. That way, you can either get buy-in to the recommendation, have a chance to change the recommendation, .
Executive Summary(FOR ALTERNATIVE STUDY PROJECTS)(LIMIT TO 1 O.docxelbanglis
Executive Summary
(FOR ALTERNATIVE STUDY PROJECTS)
(LIMIT TO 1 OR 2 PAGES.. NOTE THE REMAINDER OF THE REPORT PROVIDES OPPORTUNITY TO ELABORATE ON EACH OF THESE AND PROVIDE MORE DETAIL, DIAGRAMS, PHOTOS, ETC.)
(MAKE REFERENCE TO OTHER SECTION OF REPORT AND PLANS AND STUDIES IN APPENDICES)
1. INTRODUCTION:
The introduction is a place where you can draw the reader's attention. Try to make it interesting. Think to yourself, what would interest you or others in the industry? The introduction is also where you provide general information on the project from the owner's perspective. Be sure not to provide information on the project from your perspective or why you are hired. Save that information for the Purpose and Objective section. It is also a chance to let them know a little about the project and why it is so important to you.
2. BACKGROUND:
The Background section is where you give a little about the project history and existing conditions. You can also state why the project or site is where it is from a social, economic, and/or pragmatic perspective. You can use this section as a forward to the Purpose and Objective section. The background on a project usually sets up the purpose of the project and why you were hired.
3. PURPOSE AND OBJECTIVE:
This section is where you tell them why you are here - Why were you hired? What are you planning to do, and what are you expecting to find? Be sure to save your actual findings in the Findings section, but you can give a hint or a tease to your findings here.
4. FINDINGS:
Here is the opportunity to provide your brief findings. The operative word here is “brief” - and be sure to keep it interesting. Think to yourself - what would the owner be interested in finding? The owner hired you for several reasons, but what are his or her main reason for hiring you? Get into the owner’s head. Since you may have been hired for several different reasons - or disciplines, you may need subsections in this area to address each of the different disciplines. Be sure to only list your findings and NOT your opinions. Save your opinions for the Recommendations section.
5. RECOMMENDATOINS:
The Recommendations is where you let the owner know what your thoughts are. This is your chance to give them advice on what they should do with what you have found (and listed in the Findings section). Since this is just the Executive Summary, limit your recommendations to major decisions that will need to be made by the owner. The owner hired you for a specific reason and may be at a turning point. The owner needs to know what direction they should take after reading the executive summary. In other words, do NOT expect the owner to read every study or recommendation in the subsequent documents. (Secret tip: It is always a good idea to discuss major recommendations with the owner verbally in advance of your submittal. That way, you can either get buy-in to the recommendation, have a chance to change the recommendation, ...
I worked with professors at Michigan State University on a hand held device that could take health measurements of a plant. They are in the planning to launch this product in early 2016.
JDD 2016 - Joseph W. Yoder - Deliver Fast "With Confidence"PROIDEA
When developing and delivering large, complex systems it can be all too easy to only focus on features and overlook software qualities specific those related to software architecture. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with issues related to evolving the architectures, specifically when trying keeping the system working while making significant improvements when adding functionality. However, time has shown that various Agile practices are not sufficient to prevent or eliminate Technical Debt which can ultimately affect reliability. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture. If there is not enough attention on the architecture and code base, ultimately technical debt will creep in to the point where it can become hard to delivery quickly and with confidence.
Two important principle that can help teams deliver more quickly and with confidence is to focus on code quality and delivery size. Small frequently delivery with constant attention to a good code base is crucial to being able to sustain faster delivery with confidence. Often teams evolve to continuous delivery with some limited success, however issues arise when there is not good validation through tests and constant attention to the code quality. Practices that can help keep the code clean or from getting muddier include: Testing, Divide & Conquer, Gentrification, Quarantine, Refactoring, and Craftsmanship. This talk will examine techniques such as Continuous Integration, Continuous Inspection, Continuous Delivery as well as other techniques to pay good attention to code quality allowing teams to delivery more quickly and with confidence.
This talk has to distinct parts, the first part is about this new design-lead Era at IBM, which is really about how to scale great design to large organizations.
We’re making a huge company-wide commitment and investment to turn IBM to a design lead organization, with design led products and projects.
In the second part of the talk, I’d talk about how my team, which has embraced lean UX methods, has managed to stay focus by adopting the new IBM design thinking framework, as well as some of the lessons of integrating a strong design competency with a lean team.
Presentation to a City of Vancouver workshop looking at ways to support/create 'Missing Middle' housing including duplex, triplex and multi-family house types.
O workshop irá explorar como as práticas ágeis podem ajudar a evitar ou lidar com esse tipo de sistema. Será discutido por que a entrega contínua, TDD e refatoração não são suficientes para ajudar a garantir uma arquitetura limpa. Os resultados vão ajudar os participantes entenderem melhor as práticas e padrões que ajudam a limpar o seu código legado (refactor), bem como manter um código limpo exercitando conceitos como Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftsmanship.
Executive Summary(FOR ALTERNATIVE STUDY PROJECTS)(LIMIT TO 1 O.docxrhetttrevannion
Executive Summary
(FOR ALTERNATIVE STUDY PROJECTS)
(LIMIT TO 1 OR 2 PAGES.. NOTE THE REMAINDER OF THE REPORT PROVIDES OPPORTUNITY TO ELABORATE ON EACH OF THESE AND PROVIDE MORE DETAIL, DIAGRAMS, PHOTOS, ETC.)
(MAKE REFERENCE TO OTHER SECTION OF REPORT AND PLANS AND STUDIES IN APPENDICES)
1. INTRODUCTION:
The introduction is a place where you can draw the reader's attention. Try to make it interesting. Think to yourself, what would interest you or others in the industry? The introduction is also where you provide general information on the project from the owner's perspective. Be sure not to provide information on the project from your perspective or why you are hired. Save that information for the Purpose and Objective section. It is also a chance to let them know a little about the project and why it is so important to you.
2. BACKGROUND:
The Background section is where you give a little about the project history and existing conditions. You can also state why the project or site is where it is from a social, economic, and/or pragmatic perspective. You can use this section as a forward to the Purpose and Objective section. The background on a project usually sets up the purpose of the project and why you were hired.
3. PURPOSE AND OBJECTIVE:
This section is where you tell them why you are here - Why were you hired? What are you planning to do, and what are you expecting to find? Be sure to save your actual findings in the Findings section, but you can give a hint or a tease to your findings here.
4. FINDINGS:
Here is the opportunity to provide your brief findings. The operative word here is “brief” - and be sure to keep it interesting. Think to yourself - what would the owner be interested in finding? The owner hired you for several reasons, but what are his or her main reason for hiring you? Get into the owner’s head. Since you may have been hired for several different reasons - or disciplines, you may need subsections in this area to address each of the different disciplines. Be sure to only list your findings and NOT your opinions. Save your opinions for the Recommendations section.
5. RECOMMENDATOINS:
The Recommendations is where you let the owner know what your thoughts are. This is your chance to give them advice on what they should do with what you have found (and listed in the Findings section). Since this is just the Executive Summary, limit your recommendations to major decisions that will need to be made by the owner. The owner hired you for a specific reason and may be at a turning point. The owner needs to know what direction they should take after reading the executive summary. In other words, do NOT expect the owner to read every study or recommendation in the subsequent documents. (Secret tip: It is always a good idea to discuss major recommendations with the owner verbally in advance of your submittal. That way, you can either get buy-in to the recommendation, have a chance to change the recommendation, .
Executive Summary(FOR ALTERNATIVE STUDY PROJECTS)(LIMIT TO 1 O.docxelbanglis
Executive Summary
(FOR ALTERNATIVE STUDY PROJECTS)
(LIMIT TO 1 OR 2 PAGES.. NOTE THE REMAINDER OF THE REPORT PROVIDES OPPORTUNITY TO ELABORATE ON EACH OF THESE AND PROVIDE MORE DETAIL, DIAGRAMS, PHOTOS, ETC.)
(MAKE REFERENCE TO OTHER SECTION OF REPORT AND PLANS AND STUDIES IN APPENDICES)
1. INTRODUCTION:
The introduction is a place where you can draw the reader's attention. Try to make it interesting. Think to yourself, what would interest you or others in the industry? The introduction is also where you provide general information on the project from the owner's perspective. Be sure not to provide information on the project from your perspective or why you are hired. Save that information for the Purpose and Objective section. It is also a chance to let them know a little about the project and why it is so important to you.
2. BACKGROUND:
The Background section is where you give a little about the project history and existing conditions. You can also state why the project or site is where it is from a social, economic, and/or pragmatic perspective. You can use this section as a forward to the Purpose and Objective section. The background on a project usually sets up the purpose of the project and why you were hired.
3. PURPOSE AND OBJECTIVE:
This section is where you tell them why you are here - Why were you hired? What are you planning to do, and what are you expecting to find? Be sure to save your actual findings in the Findings section, but you can give a hint or a tease to your findings here.
4. FINDINGS:
Here is the opportunity to provide your brief findings. The operative word here is “brief” - and be sure to keep it interesting. Think to yourself - what would the owner be interested in finding? The owner hired you for several reasons, but what are his or her main reason for hiring you? Get into the owner’s head. Since you may have been hired for several different reasons - or disciplines, you may need subsections in this area to address each of the different disciplines. Be sure to only list your findings and NOT your opinions. Save your opinions for the Recommendations section.
5. RECOMMENDATOINS:
The Recommendations is where you let the owner know what your thoughts are. This is your chance to give them advice on what they should do with what you have found (and listed in the Findings section). Since this is just the Executive Summary, limit your recommendations to major decisions that will need to be made by the owner. The owner hired you for a specific reason and may be at a turning point. The owner needs to know what direction they should take after reading the executive summary. In other words, do NOT expect the owner to read every study or recommendation in the subsequent documents. (Secret tip: It is always a good idea to discuss major recommendations with the owner verbally in advance of your submittal. That way, you can either get buy-in to the recommendation, have a chance to change the recommendation, ...
I worked with professors at Michigan State University on a hand held device that could take health measurements of a plant. They are in the planning to launch this product in early 2016.
JDD 2016 - Joseph W. Yoder - Deliver Fast "With Confidence"PROIDEA
When developing and delivering large, complex systems it can be all too easy to only focus on features and overlook software qualities specific those related to software architecture. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with issues related to evolving the architectures, specifically when trying keeping the system working while making significant improvements when adding functionality. However, time has shown that various Agile practices are not sufficient to prevent or eliminate Technical Debt which can ultimately affect reliability. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture. If there is not enough attention on the architecture and code base, ultimately technical debt will creep in to the point where it can become hard to delivery quickly and with confidence.
Two important principle that can help teams deliver more quickly and with confidence is to focus on code quality and delivery size. Small frequently delivery with constant attention to a good code base is crucial to being able to sustain faster delivery with confidence. Often teams evolve to continuous delivery with some limited success, however issues arise when there is not good validation through tests and constant attention to the code quality. Practices that can help keep the code clean or from getting muddier include: Testing, Divide & Conquer, Gentrification, Quarantine, Refactoring, and Craftsmanship. This talk will examine techniques such as Continuous Integration, Continuous Inspection, Continuous Delivery as well as other techniques to pay good attention to code quality allowing teams to delivery more quickly and with confidence.
This talk has to distinct parts, the first part is about this new design-lead Era at IBM, which is really about how to scale great design to large organizations.
We’re making a huge company-wide commitment and investment to turn IBM to a design lead organization, with design led products and projects.
In the second part of the talk, I’d talk about how my team, which has embraced lean UX methods, has managed to stay focus by adopting the new IBM design thinking framework, as well as some of the lessons of integrating a strong design competency with a lean team.
Leveraging component-based design to save money on your web project, by Oliver Seldman from Advomatic, Leah Kopperman from The Jewish Education Project, and Jessica Teal from Teal Media.
An urban design presentation for staff and members at Wakefield MDC advocating the principles of good design, the economics and social benefits of good design.
ASML is the world's leading provider of lithography systems for the semiconductor industry. Such systems are controlled by more than 20 million lines of code. To improve the efficiency and quality of its software development process, ASML is using, amongst others, model-driven-engineering and associated tools and techniques.
Recently, subsystems are being developed according to an architecture pattern that separates Data, Control and Algorithms (DCA). To support this pattern, the ASML software architecture group is working towards a SW development environment (ASOME). This environment consists of a set of modeling languages, associated editors that allow specification of (sub)systems according to this DCA pattern. Furthermore, it contains model-to-model transformations to (COTS) analysis tools (e.g. model checkers) and model-to-text transformation to generate (parts of) the implementation.
In this presentation, I will briefly introduce ASML and the kind of (software) systems that we develop. Some aspects of the DCA architectural pattern, the languages that we are developing and the associated Sirius based editors, will be presented. For the Data part, a DSL and editor have been developed allowing the definition of various kinds of datatypes from which various kinds of repositories can be generated supporting clone based data or reference based data, modifiable and read-only entities etc. In order support the Control aspect; a language and editor have been defined that allow specification of interfaces and their realization based on state machines. A system editor allows decomposition of a system into subsystems while allowing delegation of incoming requests to internal parts. The editors are mostly Sirius based graphical editors, where the created models are persisted textually using XText.
The presentation will focus on sharing some of our experiences with both the development and deployment of products based on Sirius technology. Building the ASOME environment imposes many challenges and I would like to conclude with some that specifically target the development of the front ends of this environment.
Modelling 3D structures such as ponds, swales, channels and embankments is a relatively new advancement in the industry. Presented at the CIWEM Urban Drainage Group Conference this paper looks specifically at advances that have been made in hydraulic modelling techniques.
2016 NTC Conference - Design on a BudgetAaron Welch
Advomatic and Teal Media presentation at NTC 2016 on the drawbacks of traditional website design processes, and an alternative, more agile approach called Component-Based design.
Micro Manchester Meetup: "The Seven (More) Deadly Sins of Microservices"Daniel Bryant
There is trouble brewing in the land of microservices – today’s shiny technology is tomorrow’s legacy, and there is concern that we will all be dealing with spaghetti services in 2018…
It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project…
Harald Spitaler, Stahlbau Pichler, Bolzano (IT) “The design assist approach f...IDM Südtirol - Alto Adige
The Future Envelope 12
Interreg IT-AU FACEcamp project
------------
Conference on Building Envelopes
20-21 May 2019, NOI Techpark, Bolzano (Italy)
"It’s all about performances".
A portfolio showcasing work that was completed during my product design (BSc) University Degree. The portfolio includes such work as concept development, research and testing, rapid prototyping and design for manufacture.
Topic: Operations Management, Degree: MBA, Semester: II Syllabus: Mysore University. Date : Jan 2015.
Please note: This was prepared as a teaching aid. Not for commercial purposes. Sharing to spread the knowledge of operations management. Note : Copyright belongs to respective owners. List of top references used to prepare these slides given.
If you have any questions, comments, improvement suggestions, Email to: niranjanakoodavalli@gmail.com
Leveraging component-based design to save money on your web project, by Oliver Seldman from Advomatic, Leah Kopperman from The Jewish Education Project, and Jessica Teal from Teal Media.
An urban design presentation for staff and members at Wakefield MDC advocating the principles of good design, the economics and social benefits of good design.
ASML is the world's leading provider of lithography systems for the semiconductor industry. Such systems are controlled by more than 20 million lines of code. To improve the efficiency and quality of its software development process, ASML is using, amongst others, model-driven-engineering and associated tools and techniques.
Recently, subsystems are being developed according to an architecture pattern that separates Data, Control and Algorithms (DCA). To support this pattern, the ASML software architecture group is working towards a SW development environment (ASOME). This environment consists of a set of modeling languages, associated editors that allow specification of (sub)systems according to this DCA pattern. Furthermore, it contains model-to-model transformations to (COTS) analysis tools (e.g. model checkers) and model-to-text transformation to generate (parts of) the implementation.
In this presentation, I will briefly introduce ASML and the kind of (software) systems that we develop. Some aspects of the DCA architectural pattern, the languages that we are developing and the associated Sirius based editors, will be presented. For the Data part, a DSL and editor have been developed allowing the definition of various kinds of datatypes from which various kinds of repositories can be generated supporting clone based data or reference based data, modifiable and read-only entities etc. In order support the Control aspect; a language and editor have been defined that allow specification of interfaces and their realization based on state machines. A system editor allows decomposition of a system into subsystems while allowing delegation of incoming requests to internal parts. The editors are mostly Sirius based graphical editors, where the created models are persisted textually using XText.
The presentation will focus on sharing some of our experiences with both the development and deployment of products based on Sirius technology. Building the ASOME environment imposes many challenges and I would like to conclude with some that specifically target the development of the front ends of this environment.
Modelling 3D structures such as ponds, swales, channels and embankments is a relatively new advancement in the industry. Presented at the CIWEM Urban Drainage Group Conference this paper looks specifically at advances that have been made in hydraulic modelling techniques.
2016 NTC Conference - Design on a BudgetAaron Welch
Advomatic and Teal Media presentation at NTC 2016 on the drawbacks of traditional website design processes, and an alternative, more agile approach called Component-Based design.
Micro Manchester Meetup: "The Seven (More) Deadly Sins of Microservices"Daniel Bryant
There is trouble brewing in the land of microservices – today’s shiny technology is tomorrow’s legacy, and there is concern that we will all be dealing with spaghetti services in 2018…
It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project…
Harald Spitaler, Stahlbau Pichler, Bolzano (IT) “The design assist approach f...IDM Südtirol - Alto Adige
The Future Envelope 12
Interreg IT-AU FACEcamp project
------------
Conference on Building Envelopes
20-21 May 2019, NOI Techpark, Bolzano (Italy)
"It’s all about performances".
A portfolio showcasing work that was completed during my product design (BSc) University Degree. The portfolio includes such work as concept development, research and testing, rapid prototyping and design for manufacture.
Topic: Operations Management, Degree: MBA, Semester: II Syllabus: Mysore University. Date : Jan 2015.
Please note: This was prepared as a teaching aid. Not for commercial purposes. Sharing to spread the knowledge of operations management. Note : Copyright belongs to respective owners. List of top references used to prepare these slides given.
If you have any questions, comments, improvement suggestions, Email to: niranjanakoodavalli@gmail.com
Similar to Lanefab - Comments on Permitting Barriers (20)
Passive House Northwest Conference - March 2016
Bryn Davidson, Lanefab Design/Build
With Passive House you have to get the small details right. At the same time we can't lose sight of the big
picture.
We have to start asking how our passive house projects can actually make the world better; how our projects can be 'Net Positive'.
Case in point: Could your new passive house - on a rural green-field site - incur more negative climate impacts than if you had moved into a draughty old house in a walkable location? Our discussions about passive house need to expand beyond the building envelope to include the impacts of location, and the history of the site.
With examples of policies and projects from Vancouver, BC we'll ask how to set the bar for Net Positive development.
Net Positive Projects - Homes that make the world measurably betterBryn Davidson
Are all 'green' building projects the same?
Can we add floor area while also reducing GHGs?
At Lanefab Design/Build we are wrestling with these questions... so here are our latest thoughts from the 'fabLab.
St. George Blueway - Overview March 2011Bryn Davidson
The St. George Blueway group, in partnership with the False Creek Watershed Society, is working to create a new urban stream along St. George street in Vancouver.
The new water-focused greenway (or 'blueway') will follow the path of the historic stream currently buried in the storm sewers of the Mt. Pleasant neighbourhood.
Presentation by Jared Jageler, David Adler, Noelia Duchovny, and Evan Herrnstadt, analysts in CBO’s Microeconomic Studies and Health Analysis Divisions, at the Association of Environmental and Resource Economists Summer Conference.
Jennifer Schaus and Associates hosts a complimentary webinar series on The FAR in 2024. Join the webinars on Wednesdays and Fridays at noon, eastern.
Recordings are on YouTube and the company website.
https://www.youtube.com/@jenniferschaus/videos
A process server is a authorized person for delivering legal documents, such as summons, complaints, subpoenas, and other court papers, to peoples involved in legal proceedings.
Jennifer Schaus and Associates hosts a complimentary webinar series on The FAR in 2024. Join the webinars on Wednesdays and Fridays at noon, eastern.
Recordings are on YouTube and the company website.
https://www.youtube.com/@jenniferschaus/videos
Jennifer Schaus and Associates hosts a complimentary webinar series on The FAR in 2024. Join the webinars on Wednesdays and Fridays at noon, eastern.
Recordings are on YouTube and the company website.
https://www.youtube.com/@jenniferschaus/videos
Russian anarchist and anti-war movement in the third year of full-scale warAntti Rautiainen
Anarchist group ANA Regensburg hosted my online-presentation on 16th of May 2024, in which I discussed tactics of anti-war activism in Russia, and reasons why the anti-war movement has not been able to make an impact to change the course of events yet. Cases of anarchists repressed for anti-war activities are presented, as well as strategies of support for political prisoners, and modest successes in supporting their struggles.
Thumbnail picture is by MediaZona, you may read their report on anti-war arson attacks in Russia here: https://en.zona.media/article/2022/10/13/burn-map
Links:
Autonomous Action
http://Avtonom.org
Anarchist Black Cross Moscow
http://Avtonom.org/abc
Solidarity Zone
https://t.me/solidarity_zone
Memorial
https://memopzk.org/, https://t.me/pzk_memorial
OVD-Info
https://en.ovdinfo.org/antiwar-ovd-info-guide
RosUznik
https://rosuznik.org/
Uznik Online
http://uznikonline.tilda.ws/
Russian Reader
https://therussianreader.com/
ABC Irkutsk
https://abc38.noblogs.org/
Send mail to prisoners from abroad:
http://Prisonmail.online
YouTube: https://youtu.be/c5nSOdU48O8
Spotify: https://podcasters.spotify.com/pod/show/libertarianlifecoach/episodes/Russian-anarchist-and-anti-war-movement-in-the-third-year-of-full-scale-war-e2k8ai4
This session provides a comprehensive overview of the latest updates to the Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards (commonly known as the Uniform Guidance) outlined in the 2 CFR 200.
With a focus on the 2024 revisions issued by the Office of Management and Budget (OMB), participants will gain insight into the key changes affecting federal grant recipients. The session will delve into critical regulatory updates, providing attendees with the knowledge and tools necessary to navigate and comply with the evolving landscape of federal grant management.
Learning Objectives:
- Understand the rationale behind the 2024 updates to the Uniform Guidance outlined in 2 CFR 200, and their implications for federal grant recipients.
- Identify the key changes and revisions introduced by the Office of Management and Budget (OMB) in the 2024 edition of 2 CFR 200.
- Gain proficiency in applying the updated regulations to ensure compliance with federal grant requirements and avoid potential audit findings.
- Develop strategies for effectively implementing the new guidelines within the grant management processes of their respective organizations, fostering efficiency and accountability in federal grant administration.
Donate to charity during this holiday seasonSERUDS INDIA
For people who have money and are philanthropic, there are infinite opportunities to gift a needy person or child a Merry Christmas. Even if you are living on a shoestring budget, you will be surprised at how much you can do.
Donate Us
https://serudsindia.org/how-to-donate-to-charity-during-this-holiday-season/
#charityforchildren, #donateforchildren, #donateclothesforchildren, #donatebooksforchildren, #donatetoysforchildren, #sponsorforchildren, #sponsorclothesforchildren, #sponsorbooksforchildren, #sponsortoysforchildren, #seruds, #kurnool
Understanding the Challenges of Street ChildrenSERUDS INDIA
By raising awareness, providing support, advocating for change, and offering assistance to children in need, individuals can play a crucial role in improving the lives of street children and helping them realize their full potential
Donate Us
https://serudsindia.org/how-individuals-can-support-street-children-in-india/
#donatefororphan, #donateforhomelesschildren, #childeducation, #ngochildeducation, #donateforeducation, #donationforchildeducation, #sponsorforpoorchild, #sponsororphanage #sponsororphanchild, #donation, #education, #charity, #educationforchild, #seruds, #kurnool, #joyhome
ZGB - The Role of Generative AI in Government transformation.pdfSaeed Al Dhaheri
This keynote was presented during the the 7th edition of the UAE Hackathon 2024. It highlights the role of AI and Generative AI in addressing government transformation to achieve zero government bureaucracy
ZGB - The Role of Generative AI in Government transformation.pdf
Lanefab - Comments on Permitting Barriers
1. Lanefab Design/Build Sept 2016
Illustrative comments on permitting barriers
(and opportunities)
for RS houses & LWH
September 2016
Lanefab Design/Build
2. Lanefab Design/Build Sept 2016
In our view there is a hierarchy of ‘policy importance’.
Less important policies should be removed / expedited
during periods w permit delays (or) low rental vacancy rates.
3. Lanefab Design/Build Sept 2016
Life Safety
Fire separation, exposing faces, stair and guard dimensions, fire sprinklering etc
Energy & Climate
Envelope thermal performance, thick wall exclusions, passive house relaxations etc
Floor Area & Height Compliance
Overlook and Shadowing
Accessibility
Tree Canopy Retention
Architectural Design Guideline Compliance
Front and rear yard compatibility, roof shape, window trim dimension etc
Landscape Design Guideline Compliance
A hierarchy of ‘policy importance’
8. Lanefab Design/Build Sept 2016
Had to go to BOV for relaxations to save/incorporate this magnolia tree
Often there is not enough flex in the bylaw and guidelines… but this is improving…
9. Lanefab Design/Build Sept 2016
More lumber in the barriers than in trees being protected.
Nowhere to work.
146 W.22nd – new RS-1 outright house and lwh
10. Lanefab Design/Build Sept 2016
Late 90s: 4’ tree barrier when main house was built
Adding a garage, and re-doing the backyard
11. Lanefab Design/Build Sept 2016
Late 90s: 4’ tree barrier
Same trees in 2016:
24.5’ requested tree barrier (would have killed the entire project)
Adding a garage, and re-doing the backyard
12. Lanefab Design/Build Sept 2016
Late 90s: 4’ tree barrier
Same trees in 2016:
24.5’ requested tree barrier (would have killed the entire project)
Adding a garage, and re-doing the backyard
This was appealed (successfully), but after much delay.
We need a simpler/clearer policy
13. Lanefab Design/Build Sept 2016
1 arborist says building this lwh at 2’ from property line and tree is OK.
2nd arborist does an air-spade inspection, and says it’s OK
City tree inspector says no… planners ask for a neighbour letter... neighbour refuses
...project is killed after 8 months work and 15k in expenses.
Problem: no clear & early guidance regarding work near trees.
Frequent discrepancy between private and city arborists.
5545 Larch St.
1 storey lwh
14. Lanefab Design/Build Sept 2016
Client wants to preserve existing tree.
City grants extra depth into the yard to move away from the tree (yay!)
City then asks for a neighbour letter due to the granted relaxation…. (grrr)
Solution: don’t ask us to jump through extra hoops if you grant a relaxation to save a tree
6627 Inverness
26’
15. Lanefab Design/Build Sept 2016
38 E.37th RS-1 Passive House
Passive House: Low quality (topped) conifer in the footprint of the garage and basement well.
16. Lanefab Design/Build Sept 2016
38 E.37th RS-1 Passive House
At permit review the city is asking for the tree to be retained…
...a choice that negates the ability to achieve the passive house standard.
Passive House: Low quality (topped) conifer in the footprint of the garage and basement well.
17. Lanefab Design/Build Sept 2016
38 E.37th RS-1 Passive House
At permit review the city is asking for the tree to be retained…
...a choice that negates the ability to achieve the passive house standard.
Ongoing.... 5 weeks of discussion...
We need to balance competing policy agendas (without freezing the triggering project)
Passive House: Low quality (topped) conifer in the footprint of the garage and basement well.
20. Lanefab Design/Build Sept 2016
Design-review interventions to reduce ‘apparent massing’ of upper level.
Example of guidelines leading to time-consuming review…
... with little net gain for the city.
22. Lanefab Design/Build Sept 2016
The design review committee
is a ‘black box’ that can be
subjective and arbitrary.
1168 Park Dr. LWH
23. Lanefab Design/Build Sept 2016
Rejected:
“…creates too much
“cluttered space” at the rear…”
This LWH scheme aimed to
retain existing garage, fence
and gate.
1168 Park Dr. LWH
The design review committee
is a ‘black box’ that can be
subjective and arbitrary.
24. Lanefab Design/Build Sept 2016
Rejected:
“…creates too much
“cluttered space” at the rear…”
5 different concepts with
weeks in-between waiting for
comments from committee
This LWH scheme aimed to
retain existing garage, fence
and gate.
1168 Park Dr. LWH
The design review committee
is a ‘black box’ that can be
subjective and arbitrary.
25. Lanefab Design/Build Sept 2016
3106 Venables
The design review committee
is a ‘black box’ that can be
subjective and arbitrary…
...and has unwritten rules
Staff are debating the imposition of unwritten limits on the width of sunken patios…
26. Staff are debating the imposition of unwritten limits on the width of sunken patios...
…this would not have been allowed.
27. Staff are debating the imposition of unwritten limits on the width of sunken patios...
…this would not have been allowed.
28. Lanefab Design/Build Sept 2016
If design review staff see a need to create new rules…
...save them up, and propose them as part of a public process
30. Lanefab Design/Build Sept 2016
The city’s view of how design guidelines impact projects:
Most projects
(and the city) are
improved through design
review and design
guidelines
Some projects would have
been “ok” anyway, even
without the guidelines
31. Lanefab Design/Build Sept 2016
Many crappy
(but compliant)
projects still get built
Good / different / interesting
/ innovative projects get
dumbed-down and
‘normalized’
Many projects meet the
guidelines initially, but owners
do post-inspection
modifications to get what
they actually wanted
Some projects are
actually improved
through design review
(but at a significant cost
and delay)
Our* view of how design guidelines impact projects:
* designers, builders, & owners of
small-lot residential projects
Some projects would have
been “ok” anyway, even
without the guidelines
32. Lanefab Design/Build Sept 2016
Trees / Landscape
• Allow relaxations without incurring additional hurdles (i.e. neighbour letter)
• Remove the requirement for landscape review
• Plan checkers can do tree review w simple formulas for barriers
• Landscape staff can do a pre-check, and landscape supervisor can support PCs
• Allow tree removal for trees in the building footprint (w/out city inspection)
Design Review
• Individual design reviewers can clear a project without the committee
• The committee exists solely as an appeals process
• Hidden guidelines are shelved until the next policy update process
• Next policy update should reduce /simplify the guidelines
Permit Review
• Allow for a phone call or meeting to review deficiency lists
• Allow older surveys (1 yr.)