47 stories
·
1 follower

Dockless Roombas

1 Comment and 8 Shares
The company started out exploiting a loophole in the law banning scooters. The city was mad at first, but then they noticed how much they were saving on street cleaning.
Read the whole story
Share this story
Delete
1 public comment
alt_text_bot
49 days ago
reply
The company started out exploiting a loophole in the law banning scooters. The city was mad at first, but then they noticed how much they were saving on street cleaning.
33 days ago
https://keramatzade.com/Earn-wealth-with-amazing-business-ideals https://keramatzade.com/Law-of-Attraction-of-Wealth https://keramatzade.com/Ways-to-make-money https://modirebimeh.ir/online-calculation-of-iranian-life-insurance/ https://modirebimeh.ir/engineers-professional-liability-insurance/ https://modirebimeh.ir/third-party-insurance-calculation/ https://modirebimeh.ir/iran-liability-insurance-have-you-not-yet-insured-your-business-with-iran-liability-insurance/ https://modirebimeh.ir/iran-life-insurance-ganji-for-the-future-of-children-and-families/ https://modirebimeh.ir/iran-car-body-insurance-the-best-and-most-prestigious-in-the-iranian-insurance-industry/ https://modirebimeh.ir/the-most-reliable-and-unrivaled-third-party-car-insurance-in-iran/ https://keramatzade.com/14-ways-to-increase-revenue https://keramatzade.com/8-ways-to-increase-revenue https://keramatzade.com/25-jobs-with-which-you-can-earn-up-to-a-million-dollars https://keramatzade.com/success-secret-1 https://keramatzade.com/Make-Money-Online-Effective-step-by-step-money-making-techniques https://keramatzade.com/Make-money-at-home https://keramatzade.com/Ways-to-make-money-without-capital https://keramatzade.com/Creative-Money-Making-Ideas https://keramatzade.com/The-law-of-attracting-money https://keramatzade.com/Ways-to-Make-Money-at-Home https://keramatzade.com/Immediate-absorption-of-wealth-in-10-minutes-and-attractive-ways-to-get-rich https://keramatzade.com/The-secret-of-attracting-money-in-Iran-to-achieve-creative-money-maker-ideas https://keramatzade.com/Ways-to-get-rich-in-Iran-with-the-most-wonderful-business-ideas https://keramatzade.com/Astonishing-economic-intelligence-test-to-increase-financial-intelligence

Get your work recognized: write a brag document

1 Comment and 4 Shares

There’s this idea that, if you do great work at your job, people will (or should!) automatically recognize that work and reward you for it with promotions / increased pay. In practice, it’s often more complicated than that – some kinds of important work are more visible/memorable than others. It’s frustrating to have done something really important and later realize that you didn’t get rewarded for it just because the people making the decision didn’t understand or remember what you did. So I want to talk about a tactic that I and lots of people I work with have used!

This blog post isn’t just about being promoted or getting raises though. The ideas here have actually been more useful to me to help me reflect on themes in my work, what’s important to me, what I’m learning, and what I’d like to be doing differently. But they’ve definitely helped with promotions!

You can also skip to the brag document template at the end.

you don’t remember everything you did

One thing I’m always struck by when it comes to performance review time is a feeling of “wait, what did I do in the last 6 months?“. This is a kind of demoralizing feeling and it’s usually not based in reality, more in “I forgot what cool stuff I actually did”.

I invariably end up having to spend a bunch of time looking through my pull requests, tickets, launch emails, design documents, and more. I always end up finding small (and sometimes not-so-small) things that I completely forgot I did, like:

  • mentored an intern 5 months ago
  • did a small-but-important security project
  • spent a few weeks helping get an important migration over the line
  • helped X put together this design doc
  • etcetera!

your manager doesn’t remember everything you did

And if you don’t remember everything important you did, your manager (no matter how great they are!) probably doesn’t either. And they need to explain to other people why you should be promoted or given an evaluation like “exceeds expectations” (“X’s work is so awesome!!!!” doesn’t fly).

So if your manager is going to effectively advocate for you, they need help.

here’s the tactic: write a document listing your accomplishments

The tactic is pretty simple! Instead of trying to remember everything you did with your brain, maintain a “brag document” that lists everything so you can refer to it when you get to performance review season! This is a pretty common tactic – when I started doing this I mentioned it to more experienced people and they were like “oh yeah, I’ve been doing that for a long time, it really helps”.

Where I work we call this a “brag document” but I’ve heard other names for the same concept like “hype document” or “list of stuff I did” :).

There’s a basic template for a brag document at the end of this post.

share your brag document with your manager

When I first wrote a brag document I was kind of nervous about sharing it with my manager. It felt weird to be like “hey, uh, look at all the awesome stuff I did this year, I wrote a long document listing everything”. But my manager was really thankful for it – I think his perspective was “this makes my job way easier, now I can look at the document when writing your perf review instead of trying to remember what happened”.

Giving them a document that explains your accomplishments will really help your manager advocate for you in discussions about your performance and come to any meetings they need to have prepared.

Brag documents also really help with manager transitions – if you get a new manager 3 months before an important performance review that you want to do well on, giving them a brag document outlining your most important work & its impact will help them understand what you’ve been doing even though they may not have been aware of any of your work before.

share it with your peer reviewers

Similarly, if your company does peer feedback as part of the promotion/perf process – share your brag document with your peer reviewers!! Every time someone shares their doc with me I find it SO HELPFUL with writing their review for much the same reasons it’s helpful to share it with your manager – it reminds me of all the amazing things they did, and when they list their goals in their brag document it also helps me see what areas they might be most interested in feedback on.

On some teams at work it’s a team norm to share a brag document with peer reviewers to make it easier for them.

explain the big picture

In addition to just listing accomplishments, in your brag document you can write the narrative explaining the big picture of your work. Have you been really focused on security? On building your product skills & having really good relationships with your users? On building a strong culture of code review on the team?

In my brag document, I like to do this by making a section for areas that I’ve been focused on (like “security”) and listing all the work I’ve done in that area there. This is especially good if you’re working on something fuzzy like “building a stronger culture of code review” where all the individual actions you do towards that might be relatively small and there isn’t a big shiny ship.

use your brag document to notice patterns

In the past I’ve found the brag document useful not just to hype my accomplishments, but also to reflect on the work I’ve done. Some questions it’s helped me with:

  • What work do I feel most proud of?
  • Are there themes in these projects I should be thinking about? What’s the big picture of what I’m working on? (am I working a lot on security? localization?).
  • What do I wish I was doing more / less of?
  • Which of my projects had the effect I wanted, and which didn’t? Why might that have been?
  • What could have gone better with project X? What might I want to do differently next time?

you can write it all at once or update it every 2 weeks

Many people have told me that it works best for them if they take a few minutes to update their brag document every 2 weeks ago. For me it actually works better to do a single marathon session every 6 months or every year where I look through everything I did and reflect on it all at once. Try out different approaches and see what works for you!

don’t forget to include the fuzzy work

A lot of us work on fuzzy projects that can feel hard to quantify, like:

  • improving code quality on the team / making code reviews a little more in depth
  • making on call easier
  • building a more fair interview process / performance review system
  • refactoring / driving down technical debt

A lot of people will leave this kind of work out because they don’t know how to explain why it’s important. But I think this kind of work is especially important to put into your brag document because it’s the most likely to fall under the radar! One way to approach this is to, for each goal:

  1. explain your goal for the work (why do you think it’s important to refactor X piece of code?)
  2. list some things you’ve done towards that goal
  3. list any effects you’ve seen of the work, even if they’re a little indirect

If you tell your coworkers this kind of work is important to you and tell them what you’ve been doing, maybe they can also give you ideas about how to do it more effectively or make the effects of that work more obvious!

encourage each other to celebrate accomplishments

One nice side effect of having a shared idea that it’s normal/good to maintain a brag document at work is that I sometimes see people encouraging each other to record & celebrate their accomplishments (“hey, you should put that in your brag doc, that was really good!”). It can be hard to see the value of your work sometimes, especially when you’re working on something hard, and an outside perspective from a friend or colleague can really help you see why what you’re doing is important.

Brag documents are good when you use them on your own to advocate for yourself, but I think they’re better as a collaborative effort to recognize where people are excelling.

Next, I want to talk about a couple of structures that we’ve used to help people recognize their accomplishments.

the brag workshop: help people list their accomplishments

The way this “brag document” practice started in the first place is that my coworker Karla and I wanted to help other women in engineering advocate for themselves more in the performance review process. The idea is that some people undersell their accomplishments more than they should, so we wanted to encourage those people to “brag” a little bit and write down what they did that was important.

We did this by running a “brag workshop” just before performance review season. The format of the workshop is like this:

Part 1: write the document: 1-2 hours. Everybody sits down with their laptop, starts looking through their pull requests, tickets they resolved, design docs, etc, and puts together a list of important things they did in the last 6 months.

Part 2: pair up and make the impact of your work clearer: 1 hour. The goal of this part is to pair up, review each other’s documents, and identify places where people haven’t bragged “enough” – maybe they worked on an extremely critical project to the company but didn’t highlight how important it was, maybe they improved test performance but didn’t say that they made the tests 3 times faster and that it improved everyone’s developer experience. It’s easy to accidentally write “I shipped $feature” and miss the follow up (“… which caused $thing to happen”). Another person reading through your document can help you catch the places where you need to clarify the impact.

biweekly brag document writing session

Another approach to helping people remember their accomplishments: my friend Dave gets some friends together every couple of weeks or so for everyone to update their brag documents. It’s a nice way for people to talk about work that they’re happy about & celebrate it a little bit, and updating your brag document as you go can be easier than trying to remember everything you did all at once at the end of the year.

These don’t have to be people in the same company or even in the same city – that group meets over video chat and has people from many different companies doing this together from Portland, Toronto, New York, and Montreal.

In general, especially if you’re someone who really cares about your work, I think it’s really positive to share your goals & accomplishments (and the things that haven’t gone so well too!) with your friends and coworkers. It makes it feel less like you’re working alone and more like everyone is supporting each other in helping them accomplish what they want.

thanks

Thanks to Karla Burnett who I worked with on spreading this idea at work, to Dave Vasilevsky for running brag doc writing sessions, to Will Larson who encouraged me to start one of these in the first place, to my manager Jay Shirley for always being encouraging & showing me that this is a useful way to work with a manager, and to Allie, Dan, Laura, Julian, Kamal, Stanley, and Vaibhav for reading a draft of this.

I’d also recommend the blog post Hype Yourself! You’re Worth It! by Aashni Shah which talks about a similar approach.

Appendix: brag document template

Here’s a template for a brag document! Usually I make one brag document per year. (“Julia’s 2017 brag document”). I think it’s okay to make it quite long / comprehensive – 5-10 pages or more for a year of work doesn’t seem like too much to me, especially if you’re including some graphs/charts / screenshots to show the effects of what you did.

One thing I want to emphasize, for people who don’t like to brag, is – you don’t have to try to make your work sound better than it is. Just make it sound exactly as good as it is! For example “was the primary contributor to X new feature that’s now used by 60% of our customers and has gotten Y positive feedback”.

Goals for this year:

  • List your major goals here! Sharing your goals with your manager & coworkers is really nice because it helps them see how they can support you in accomplishing those goals!

Goals for next year

  • If it’s getting towards the end of the year, maybe start writing down what you think your goals for next year might be.

Projects

For each one, go through:

  • What your contributions were (did you come up with the design? Which components did you build? Was there some useful insight like “wait, we can cut scope and do what we want by doing way less work” that you came up with?)
  • The impact of the project – who was it for? Are there numbers you can attach to it? (saved X dollars? shipped new feature that has helped sell Y big deals? Improved performance by X%? Used by X internal users every day?). Did it support some important non-numeric company goal (required to pass an audit? helped retain an important user?)

Remember: don’t forget to explain what the results of you work actually were! It’s often important to go back a few months later and fill in what actually happened after you launched the project.

Collaboration & mentorship

Examples of things in this category:

  • Helping others in an area you’re an expert in (like “other engineers regularly ask me for one-off help solving weird bugs in their CSS” or “quoting from the C standard at just the right moment”)
  • Mentoring interns / helping new team members get started
  • Writing really clear emails/meeting notes
  • Foundational code that other people built on top of
  • Improving monitoring / dashboards / on call
  • Any code review that you spent a particularly long time on / that you think was especially important
  • Important questions you answered (“helped Risha from OTHER_TEAM with a lot of questions related to Y”)
  • Mentoring someone on a project (“gave Ben advice from time to time on leading his first big project”)
  • Giving an internal talk or workshop

Design & documentation

List design docs & documentation that you worked on

  • Design docs: I usually just say “wrote design for X” or “reviewed design for X”
  • Documentation: maybe briefly explain the goal behind this documentation (for example “we were getting a lot of questions about X, so I documented it and now we can answer the questions more quickly”)

Company building

This is a category we have at work – it basically means “things you did to help the company overall, not just your project / team”. Some things that go in here:

  • Going above & beyond with interviewing or recruiting (doing campus recruiting, etc)
  • Improving important processes, like the interview process or writing better onboarding materials

What you learned

My friend Julian suggested this section and I think it’s a great idea – try listing important things you learned or skills you’ve acquired recently! Some examples of skills you might be learning or improving:

  • how to do performance analysis & make code run faster
  • internals of an important piece of software (like the JVM or Postgres or Linux)
  • how to use a library (like React)
  • how to use an important tool (like the command line or Firefox dev tools)
  • about a specific area of programming (like localization or timezones)
  • an area like product management / UX design
  • how to write a clear design doc
  • a new programming language

It’s really easy to lose track of what skills you’re learning, and usually when I reflect on this I realize I learned a lot more than I thought and also notice things that I’m not learning that I wish I was.

Outside of work

It’s also often useful to track accomplishments outside of work, like:

  • blog posts
  • talks/panels
  • open source work
  • Industry recognition

I think this can be a nice way to highlight how you’re thinking about your career outside of strictly what you’re doing at work.

This can also include other non-career-related things you’re proud of, if that feels good to you! Some people like to keep a combined personal + work brag document.

General prompts

If you’re feeling stuck for things to mention, try:

  • If you were trying to convince a friend to come join your company/team, what would you tell them about your work?
  • Did anybody tell you you did something well recently?
Read the whole story
Share this story
Delete
1 public comment
jepler
105 days ago
reply
(also document your Foss contributions this way)
Earth, Sol system, Western spiral arm

Dooddoener: mensen houden niet van verandering

1 Share

Tegen verandering ? Dan ben je conservatief ! Verandering ligt bij vele mensen moeilijk en dat is maar goed ook. Veranderen om te veranderen heeft weinig zin. Je weet wat je hebt, maar niet wat er komen zal. Iets anders of op een nieuwe manier betekent niet per definitie dat het beter zal zijn, dus … Lees verder Dooddoener: mensen houden niet van verandering

Het bericht Dooddoener: mensen houden niet van verandering verscheen eerst op De Wereld van Kaat.

Read the whole story
Share this story
Delete

Synology-SA-18:62 Netatalk

1 Comment

Abstract

A vulnerability allows remote attackers to execute arbitrary code via a susceptible version of Synology Diskstation Manager (DSM) and Synology Router Manager (SRM).

Affected Products

Product Severity Fixed Release Availability
DSM 6.2[1] Critical Please manually download and install version 6.2.1-23824-3.
DSM 6.1 Critical Ongoing
DSM 5.2 Critical Ongoing
SkyNAS Critical Ongoing
VS960HD Critical Ongoing
SRM 1.2 Important Ongoing

[1] Perform Manual DSM Update

Mitigation

If you need immediate assistance, please contact Synology technical support via https://account.synology.com/support.

Detail

  • CVE-2018-1160
    • Severity: Critical
    • CVSS3 Base Score: 9.8
    • CVSS3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    • Netatalk before 3.1.12 is vulnerable to an out of bounds write in dsi_opensess.c. This is due to lack of bounds checking on attacker controlled data. A remote unauthenticated attacker can leverage this vulnerability to achieve arbitrary code execution.

Reference

CVE-2018-1160

Revision

Revision Date Description
1 2018-12-21 Initial public release.
2 2018-12-21 Update for DSM 6.2 is now available in Affected Products.

Read the whole story
Share this story
Delete
1 public comment
brunovdc
293 days ago
reply
Synology Inc.

Home – Hinata Sushibar

1 Share

Naamsesteenweg 199, 3001 Heverlee 0468 494 231

Read the whole story
Share this story
Delete

Things Break At Their Weakest Point

1 Share
Not even a block in to my 5 block walk to host our weekly Shut Up And Write session, I felt a familiar sensation - my leather dossier, slung over my back, had opened.  Every once in a while, the clasp doesn't quite catch, and the jostling of my quick-pacing walking gradually jars it to the point that it opens up.  It's well designed, so nothing falls out right away.  Usually it's a quick stop to close it up correctly, and then get underway.

Today the problem was a different one.  The leather buckle feeding into the metal clasp broke.  It detached - tore away - from the clasp.  There's no closing that bag at its usual (and only) juncture anymore, at least for the time being.  Everything else on my dossier is in decent condition, so doubtless we will be finding some fix to get in back into commission. It's definitely not the end of the world.  It's not even a major inconvenience - though at earlier points in my life, I would certainly have felt it to be one!

As I walked the rest of the way, holding the bag closed, I thought about how central a piece of equipment that particular dossier is for my work, teaching, and even leisure time.  That spurred a host of other reflections, and I thought they might prove of some interest if I were to set them down.

Things Break At Their Weakest Point

It really should be a truism, when you read it, right?  Despite our efforts, desires, and plans, things inevitably break down.  And where else would they break down?  At their strongest points?  Somewhere in the middle?  No - it will almost invariably be at the weakest point.

If we know - or at least can predict - what the weakest point of something breakable is, then we can take steps to prevent, or at least put off, that breakdown.  We can harden, reinforce, or protect it.  We can deliberately place less stress at that spot, whether through caution, moderation in use, or displacing that stress somewhere else.  When we start to see components fray, we can repair or replace them.  But we often lose sight of this.

It is easy in the course of an active life, to take all sorts of matters for granted.  This is particularly so when it comes to the weakest points of material things, persons, processes, organizations, the places where stress is going to sooner or later take its particular (and predictable) toll.  Without meaning to, we ignore those weak points.  After all, day-in-day-out nothing happens at those spots. With a past of such consistency, why shouldn't things keep going on the same way into an indefinite future?

In the case of my dossier, eight years of hard use have taken a bit of a toll.  Plastic piping shows - and is broken at one point - where the leather wore away along the edges.  Small points of the cloth parts have become a bit threadbare.  That's all minor wear and tear, and doesn't affect main functions of the bag - not the way that buckle and clasp does

Had I given it much thought - as I did the very first time that, overstuffed with class materials and a bulkier laptop, the clasp opened while I hurried across campus seven years ago - I should have expected this particular breakdown would inevitably occur.  After all, that is the weakest point.

All too often, we discover these vulnerabilities to the normal processes of the world, only once things do break down, and we find ourselves at a loss.  No surprise there.  One of the more interesting insights Martin Heidegger develops in Being and Time runs precisely along those lines:  we don't register the equipmentality of our equipment - including their materiality, their capacity for breakdown - while we're using them effectively.  It's when they break down that we actually pay closer attention.  And that's when people engage in a vast range of responses - often a mess of thoughts, feelings, desires, words, and actions.

Gratitude When Things Break Down

I'm not naturally a calm person who takes everything in stride and thoughtfully arrives at the optimal response to setbacks, obstacles, or breakdowns.  In fact, the reason why I originally got into researching - and then eventually writing on, speaking about, and coaching clients with - anger management is because I turned to ancient philosophy for resources to help me with my own too-quick temper.  My general temperament is one that in earlier times would be termed "choleric," "thumotic," or "irascible," and I still struggle with my impulses and inclinations towards anger.

Things breaking down - especially when I'm already short on time, stressed out, or am barely managing my own responsibilities - can prove a trigger for irritability, frustration, and then full-blown anger on my part, when I'm not careful.  I have worked for years to analyze and undo those otherwise automatic responses on my part, using resources drawn from a number of sources.  Sometimes I'm successful in how I deal with matters.  Sometimes not.

Dealing with my broken dossier today definitely goes into the "win" column.  I actually feel a sense of "second-order" or "meta-" gratitude - that is, gratitude about feeling gratitude - about the thoughts and feelings I experienced as I made my way to the coffeehouse for Shut Up And Write. And the reason I feel that second gratitude is because in the past it has not been my normal reaction to things breaking down.  Anger - unreasonable anger - at life, at the item itself, at whoever suggested solutions, that's more often been the case for me.  Totally unproductive, somewhat understandable but frankly unreasonable - that's the case for anger at things breaking down.

Today I felt grateful instead.  Grateful that, although the clasp broke early on in my walk, I only had a few blocks to go, rather than the 10+ block walks to and from the campuses where I teach.  Even more grateful that I wasn't in the midst of travel - what if this clasp had broken while I was quite literally taking planes, trains, and automobiles on my recent trip to present at Stoicon in London?

So much of our reaction depends on maintaining proper perspective - assuming of course, that we had a reasonable perspective in the first place!  The breakdown of the clasp means that the dossier doesn't stay closed, and I need to hold it as I carry it.  That's it.  Those are the only thing that have changed.  It hasn't stopped performing its main function - containing my computer, cords, books, notebooks, student papers, and a few granola bars.  The strap hasn't broken.  It still looks more or less the same. It just doesn't close.  And that's something that can be fixed.

I also thought about the years of service this leather dossier has given me.  I don't go as far as the personification of objects that Marie Kondo advises in The Life-Changing Magic of Tidying Up - you thank the items you're letting go for the service they've rendered you - but I did remind myself that I've owned this particular Coach dossier for eight years.  I'm a big guy, and hard on the equipment I use, and I take it nearly everywhere, so that bag has definitely done its time with me.

When things break down at their weakest points, gratitude is not only a better response than any of those encompassed within anger's spectrum - a more reasonable and productive response - it also feels better, not just in the moment, but through the rest of one's day.

Dealing With Our Dependencies

One approach that people adopt for dealing with the vulnerability to breakdown of those myriad things upon which we come to rely is to attempt to dissociate oneself from them.  Reducing our dependence on things that possess weak points eliminates our own psychological weak points - or so that line of thinking goes - so that when the inevitable does occur, we are not disturbed by it.  That's not unwise council, and you find movements from ancient times down to the present, and across cultures, proffering similar solutions.

One can go too far with that approach, I think. Minimalist excesses of ancient Cynics were already criticized by others for that in ancient times - to where its effectiveness in one area actually makes a person less effective at living in the world in others.  There's also plenty of people who talk the free-from-attachment talk but don't walk that walk (and once they lose their temper over some item breaking down at a bad moment, even their words change too!).  But on the whole, approaching the material objects, processes and platforms, even the technology upon which we are inevitably dependent with realistic sets of expectations is a prudent - a practically wise - course to take.

It would be inadvisable to be mindful or attentive about every single thing that we are dependent upon, and which could break down at weak points.  Given the kind of existence we have at present, that would be an impossible task.  But that doesn't mean that one couldn't devote a bit of time, thought, and attention - perhaps each day - to the things upon which we are particularly dependent, considering or even checking them at their most vulnerable points.

Until today, I'll admit, I hadn't even thought about just how dependent I myself am on that one leather accessory - more dependent than I am on my three pairs of shoes and boots (since, after all, I've got three) - really, about as dependent as I am on much more sophisticated items like my phone or laptop.  I've lugged that dossier practically everywhere - classes, lectures, coffeeshops, overhead bins, my car - filled it full of needful things, and tossed it around, all the while expecting unreasonably that it would simply remain the same faithful piece of equipment over time.

I assumed it would hold up in every way, not even stopping to think about its weakest point.  But of course, that's precisely where things will break down.  It's a matter of when - as well as how one deals with those breakdowns - and that in turn depends.  Depends on what?  How we take stock of at least some of our own dependencies.

Read the whole story
Share this story
Delete
Next Page of Stories