1
point
jaz
Joined 80 karma
- 33 points
- The closest I've seen to that is this page: https://cloudharmony.com/status-group-provider
- 5 points
- 1 point
- I work at a medium sized web agency (~60 employees) as a developer and consider myself introverted. For the first year I worked in a client facing role, which exhausted me - long hours, a lot of social interaction. It wore me down almost to the point of burnout. I then made a lateral move to a non client facing team which greatly improved my quality of life here. So there may be hope for you at a larger company that has non client facing roles - but you may need to work yourself up the ladder to get into them.
You can't change your underlying personality, but you can work on being more social. It's definitely not easy (at least not for me) - when in social situations during the workday, my internal monologue is usually saying "I'd rather be coding." It takes time and practice, but it's achievable. I've been working at being more social and have seen some success.
- For one, if you live with others, make sure they know that during the hours of 9-5 (or whatever your hours may be), you are actually working and cannot be disturbed.
My major struggle during my first full time work from home job was family would see I'd be home during the day, and ask me to run errands or do other personal matters during working hours. It was an uphill battle trying to explain to them that I, too, worked during the day - just not in a traditional office building.
Also, if you have the space, try to set up a dedicated "work" office, and them a "home" office in a separate room. Once your work day ends, you can leave your "work" office just as you would a traditional office. I've found this helps with keeping a regular schedule and not working 10+ hours a day. An alternative to having a separate office is utilizing a local coworking space.
- Dress code for non customer-facing employees should be relaxed. I seldom need to be on site at a client's office, but when I am, I dress just as their employees do - anything from a suit to business casual. Otherwise, I wear shorts and flip flops in the office, as do most of my coworkers.
- I work at a ~60 employee company, and while we have apps they do all of the above, they're not that usable (having been designed and written about 10 years ago). The biggest issue is HR apps are not our core competency, so management seldom allocates budget to update these tools.
Our apps do the following: - Time off - Shipment request (i.e. UPS, Fedex, etc) - Purchase order request (part of this process is still paper based) - Employee directory (currently a hodgepodge of excel sheets, paper booklets and a 14 year old intranet site) - HR news/communications (recently purchased a hosted wiki app for this, seldom used anymore)
The biggest selling point for us would be to have the app outside the firewall, and accessible from our mobile devices or home computers.
Beyond that, having the app be a "one stop shop" for HR information (benefits, corporate policies, etc), time off requests, shipment requests and an employee directory listing phone extensions, emails, photos, bio, etc. It definitely doesn't need to be everything to everyone, but if it was a place I could reliably go to for benefits information, time off, it would surely take off at my company.
- I'm working on a large angular project right now, and we're using Usemin[0] for this. Basically you have your dev version of your html page, including all your scripts separately - and when you run a grunt task, it concatenates all these scripts into one and rewrites your <script> tag accordingly.
- For what it's worth, my Sonos bridge and Play:5 barely worked on the Airport Extreme. I switched over to a new Linksys router and it works pretty well now - and the Windows desktop app even works (it didn't before). I have my music library hooked up to the Windows app via a network share.
The biggest issue is still when a component powers down, you still need to search for it again.
- As a candidate, one of the things that annoys me the most about recruiters is how they communicate with me.
I have had recruiters leave me enthusiastic voicemails / emails saying they "can't wait" to speak to me about a position and I am the "perfect candidate", but when I return their phone call or email, there's complete radio silence. Honesty about my qualifications for a given position is key; if I don't meet the job requirements, then tell me so.
It's also annoying when they won't reveal the salary for the position, or when they do, it's only after telling them your current salary. Usually, once I mention my current salary, the recruiter says "this position's salary is close to your current salary". Transparency in this area would go a long way with me personally.
- It is neat, and usually works pretty well... but occasionally I've run into issues where the dashboard 'freezes' for no apparent reason. Looking at the console revealed a backend service threw a 500 error, and because there was no error handling in the front end, the dashboard appeared to freeze. A little bit frustrating to hit this every so often.
- Is Flippa [0] not an option?
- Cached copy here: http://webcache.googleusercontent.com/search?q=cache:http://...
- If you need to just host a .NET website, there's Azure Websites [0], which has a free plan.
[0] http://www.windowsazure.com/en-us/home/scenarios/web-sites/
- I'm at a 60-ish person agency, and we're in the beginning stages of implementing one. The goal is to bring in junior level developers and teach them what they need to know to grow as a developer inside the organization. We brought aboard a junior developer about 4 months ago, with myself and a colleague responsible for training him and helping develop his skillset.
It's been an interesting and successful experience thus far.
* A training schedule, similar to a degree plan in university - just something that outlines where the organization expects them to be at 3, 6, 9 and 12 months during their first year of employ.
* Coding standards defined by the organization. Telling any developer, but particularly a junior, that your standards are "I know it when I see it" doesn't fly.
* Formal code reviews. This is something we could definitely do better. I'm working getting Atlassian Bamboo to make the reviews easier on everyone involved.
* Regularly scheduled meetings with the trainers and the junior. We do every 3 months, with less formal meetings more frequently. It's important to let them know how they are progressing, and to give them tips on how to improve any deficient skill sets.
Overall, I think the most important thing is to maintain open lines of communication.
- Here are a few things that have worked for me.
* No soda - I found soda messed with my body chemistry quite a bit, also affecting my sleep patterns. I sleep and feel better without it.
* No caffeine after 12pm - I have most of my caffeine between 6-8 AM, with the occasional cup of coffee before lunch.
* Very little alcohol on work nights - More than two beers/one cocktail, I've found, contributes to a really poor quality sleep for me.
* Wake up between 5-6 AM, reading in bed by 9 PM (sleeping by 10 usually). Getting into a routine helps me set aside the 7-8 hours of sleep I need each night.
* Exercise - I go to a personal trainer 3x a week after work, and do cardio on the off days. This helps get me to sleep at night, since I'll usually be pretty tired after workouts.
* Eliminate stress at work - I found that for a few months, big projects at work were keeping me up at night. I had to consciously stop thinking about work in my personal time, which helped me sleep.
[0] https://code.gov/agencies
[1] https://github.com/nationalsecurityagency