reignite / burnout.io Goto Github PK

Eventually the resources section will be pretty full, so some method of organization or searching is in order.

Adding keywords to resource items and perhaps a JS search function on the page might work.

I would love to see us having the capability to allow folks seeking help to take the MBI-HSS. I don't really have an idea of where to begin, but to have something that concretely says, "Yes, you're burnt out and you need some help" may be of use. The survey's are only $15, but if this were to happen, I wouldn't want folks to have to pay. Having a sponsor who paid would be helpful, I think.

Would be a great idea for burnt out devs to be able to talk to one another. Could also work as a resource and build original searchable content for search engines.

I run a neat forum software called NodeBB. Can possibly give you guys a good deal to start off with if you don't want to host it yourselves.

Hi,
I hope that you are well ?
By experience, it's very difficult to find useful informations to help to understand and overcome a burnout.
Moreover, as developer, I use many time awesome pages.
That's why I have created a awesome web page https://github.com/burnyDay/awesome-burnout-overcome.
I think it's also important to compile informations in different languages to be opened to global community because it's a global plague and local assocations could be helpful.

I wish to create a gohugo github pages based on it.
If you want to participate, feel free to create PR.
Bye and take care.

From @iennae in #45 :

One of these days we should put together something for the different categories of problems that arise and strategies for handling them

We can start using this space to start breaking out the categories for problems/strategies.

A period of time has elapsed since the build was last run, and now it fails (ah, the wonder of technology).

See: https://travis-ci.org/reignite/burnout.io/jobs/165876343

Exception occurred:
  File "/home/travis/virtualenv/python2.7.12/lib/python2.7/site-packages/docutils/writers/_html_base.py", line 671, in depart_document
    assert not self.context, 'len(context) = %s' % len(self.context)
AssertionError: len(context) = 2

http://blog.dbsmasher.com/2015/07/29/on-burnout/

http://funkatron.com/osmi.html / http://funkatron.com/about.html

/cc @funkatron - would be cool if burnout.io and osmi could unify their fantastic work and evangelism somehow - I like how burnout.io is a community open-source thing, whereas osmi seems to be an individual controlled thing - thoughts? Specifically, the burnout.io resources and pull requests section could quickly lend to duplicated content. Perhaps an open-source data file approach like https://github.com/jaspervdj/static-site-generator-comparison could work? Which then both sites then utilise.

http://www.mind.org.uk/

I ran across http://sysadvent.blogspot.com/2015/12/day-8-be-better-engineer-dont-do.html and think it'd be pertinent to the resources. Thoughts?

https://medium.com/@jpaulreed/dodging-burnout-4-hours-at-a-time-965f1921e6a2

The origins of this project is burnout in IT, and there is sadly a significant possibility that management plays an antagonistic role for a significant portion of those visiting the site. The term "actionable" has origins in law and management, so that's not a great foundation for the name of a primary section of the site.

Additionally, @iennae made some additions to the Actionables in #14 that stand on their own quite effectively. They're lost, however, at the bottom of the rest of the items in that section.

Given these two situations, I'm now in favor of condensing the "Actionables" content prior to #14, migrating it to the front page (more content, fewer clicks), additionally migrating the content in #14 to its own section (perhaps titled "More Ideas"?), and removing the "Actionables" section altogether.

The new layout could look something like this:

Burnout.io
├── Resources
├── More Ideas
└── Contribute

I think this will also give us an opportunity to revise and unify the content prior to #14, as it is a little disjoint. The inherent difficulty with collaborative writing is that, while the the content is extremely valuable, it's a bit difficult to read with the different writing styles and organization.

It would be great to hear some opinions before deciding whether to embark on this change. 😄

OS has several files in their project listed here:

https://github.com/opsschool/curriculum/tree/master/meta

It feels like a good step in the right direction to mention those who have contributed to the project, establish style guidelines, and add something like a code of conduct doc.

• http://nodeup.com/eighty / nodeup/contribute#49 - added in #21 (more resources in the website page)
• http://baugues.com/depression - added in #20
• cascadiajs/2015.cascadiajs.com#228
• berlinphp/berlinphp.github.com#78
• dopodcast/dopodcast.github.io#12 (plenty more resources in the comments)
  • Developers & Depression: http://blog.baugues.com/speaking
  • Open Sourcing Mental Illness: http://funkatron.com/osmi.html
  • Frustration Driven Development: http://www.youtube.com/watch?v=1BYZCC5khjE
  • Stanford's Sapolsky On Depression in U.S. (Full Lecture) http://www.youtube.com/watch?v=NOAgplgTxfc
• jsfest/2014-oakland-cfp#31
• https://github.com/dmanners/avoiding-burnout
• https://medium.com/@balupton/surviving-free-culture-f99b39ceb059 - added in #19

The domain is renewing in May of this year at a cost of around $45. I do not plan to renew the domain next year.

According to our analytics, we get maybe 100 views a month, many of which seem to be inauthentic traffic.

Unless I receive alternate proposals, I intend to do the following before the domain renews in 2023:

• Modify the github configuration to end the use of burnout.io and begin using a default github.io domain
• Cease the renewal of the burnout.io domain

I'm starting to run across some dead links. Need to do a bit of cleaning up.

Would you be interested in modifying the language so that it's not only targeted at devs? We might be able to widen it to include everyone in the IT industry, or even anyone in any role in any industry. This stuff effects many people! It would be neat of this was able to function as a general resource.

So far the content is just a bunch of my ramblings, summaries, and misunderstandings of the discussion during the burnout open space at devopsdays pgh. It would be great if we could get some other people to review the content for accuracy and submit new ideas.

http://burnoutio.readthedocs.org/en/latest/contribute.html currently reflects build badges for the burnoutio-test site.

Hi Folks,

I hope everyone has been doing well. I just wanted to check in--it's been a few months and it's been pretty quiet.

Similar to #36 , just need to get the badges updated on the readme.

I received this suggestion by email (not sure if they wish to be named). It's a good Ignite talk by Pam Selle: https://www.youtube.com/watch?v=YBoS-svKdgs

http://gitter.im

The list of articles doesn't really do any of them justice. As the list grows, it may be more helpful to show links based on content (quotes). I think that will help funnel users to articles that are more relevant to them.

Gitter's been quite quiet. I'm curious if using Slack might be a better medium for communication.

https://victorops.com/blog/burnout-in-tech/

The Pico CMS default layout apparently just gives a really tiny version of the site on mobile devices. Since mobile is 75% of the traffic (273/367 visitors per Google Analytics on the single day the site has been up), it would probably be wise to make the layout more friendly for that demographic. I'm considering using something like Zurb Foundation as a framework.

IT could be considered an exclusive term (even differentiating from design, dev, ops, etc.) and other work forces may be experiencing the same problems.

As a result, I've begun genericizing the terminology to be more industry-inclusive. I'd also like to make sure specific IT-related keywords are included for search and other purposes.

Hey all. I'm about to launch a podcast with a friend of mine and a series we would like to run is an interview series. The podcast is for discovering the humans behind the work, learning from their stories and life lessons, so that the listeners can travel a more grounded path. If anyone has any ideas or suggestions, or feels their stories would be useful for a wider audience, post a comment or email us at [email protected]

I am technical person myself - https://balupton.com - and my co-host is a non-technical journalist - http://brokenrecord.co - so should provide for a good range of questions and audience. Personally I'm tired of just listening to tech podcasts about people's work rather than the people behind the work, so this is our initiative to try and change that! This is our first podcast show of our own making, although we've participated in many, so hopefully the bumpy ride while it becomes platinum will be okay!

This site would work great as a static site. Using a static site generator (Like Jekyll), it would be possible to have github actually auto-build your site and host it for you.

Jekyll will auto-compile your markdown, and other such goodies. Definitely worth consideration.

Hey folks,

Some recent change has completely broken burnout.io

can we backtrack this change please?

https://medium.com/@nobert/a-year-of-fire-and-fog-2c68f90c74e4

Hi Ben,

I've been looking over the resources page, and it seems we could beef it up--maybe make it more of a collection of resources, since right now, the feel of the page is that it's more a collection of quotes regarding burnout. I'm not sure if this is the intent, or if you're open to changing it, but I'd love to help in any way I can.

Aaron

https://medium.com/digital-nomad-stories/the-cult-of-work-you-never-meant-to-join-cd965fb9ea1a

"Sanity" is the flipside to "insanity", and thus ableist. I suggest you replace all instances of it with something more descriptive. "Mental health" seems like it might work.

Old phrasing:

If the choice is between your sanity and your work, one of those is going to win (and it needs to be your sanity)!

New phrasing:

If the choice is between your mental health and your work, one of those is going to win (and it needs to be your mental health)!

Writing in RST seems like it might be somewhat of a barrier of entry to contributing. I suggest we move the docs to use markdown instead. To do this, we'll need to:

• Convert the docs
• Update the README
• Ensure that there's nothing on RTD that requires a config change.