301–310 of 367 posts
Any thoughts about making this an open platform where people own their own data but apps are built on top of it? And users can design their own UIs too? I'd be an early paying customer of that API.
Definitely beautiful and would love for something simple and clean to eat LinkedIn's lunch. I don't have much to add in addition to everyone else except this: I am really disturbed by the common meme of faces-inside-circles. Why do we need faces? It just distracts from the content. I love the idea of being able to link former colleagues together - that's neat - but I'm very anti-face and there are any number of ways…
I was told it was because they want to avoid bias charges.
Definitely beautiful and would love for something simple and clean to eat LinkedIn's lunch. I don't have much to add in addition to everyone else except this: I am really disturbed by the common meme of faces-inside-circles. Why do we need faces? It just distracts from the content. I love the idea of being able to link former colleagues together - that's neat - but I'm very anti-face and there are any number of ways…
If it was just a CV repository, I would be quite comfortable with this approach. Some regions have a social mandate to include photos on CVs and it bothers me quite a bit. Where I live Marital status / number of children is also common which I really don't understand.
Because this is set up as a web of professional landing pages though, part of the system is discovering people that you may know or finding people that you're looking for (and not just getting a link from someone to their CV).
I'd love an option to turn it off site-wide though, that could be a nice feature if you prefer to more-dissociate your connections from their physical selves.
Definitely beautiful and would love for something simple and clean to eat LinkedIn's lunch. I don't have much to add in addition to everyone else except this: I am really disturbed by the common meme of faces-inside-circles. Why do we need faces? It just distracts from the content. I love the idea of being able to link former colleagues together - that's neat - but I'm very anti-face and there are any number of ways…
I’m not sure how this plays out, but I know of one company that has an HR policy, stating that résumés that come in with photos or images of the applicants are to be immediately rejected. I was told it was because they want to avoid bias charges.
If the latter - do they acknowledge the irony?
Earlier quoted context omitted.
You’ve drawn the incorrect logic statement. !Years == !Experience It’s very hard for a SWE to have immediate impact, especially a junior one. Up to the first six months are a write-off. The next period includes their first launch and review with potentially a months long performance improvement plan. With exceptional exceptions, longevity and impact go hand in hand and a lack of longevity at the very least poses ques…
6 months is a write-off? By the time I was 6 months into my first software gig I had 5 months and 2 weeks of being a contributor. It was made clear to me that I was as entitled to voice wrong opinions as anyone else, and also entitled to own as much responsibility as I wanted. I found a niche that nobody else wanted to own and learned way more than I would have being spoon-fed the way you describe. Then again, I gues…
In my experience, even if all the bureaucracy and ops goes smoothly, any kind of reasonably sized existing project will take weeks to months before one can reach anything approaching full capacity. Learning the structure of the codebase, abstractions used, testing and deployment pipelines, the who's who, protocols for dealing with issues and customers, etc. takes a lot of time, and often can't easily be batched (i.e. you won't learn as much as you need even if you read the codebase end-to-end, you'll also be learning as you do your first tasks).
I had one experience with one-day-to-full-speed onboarding in the past. That was when I was briefly borrowed to a kind of bottom-feeder software house, whose job was to take garbage projects that were outsourced to way too cheap and unskilled labor, and beating them into something mostly working. At that job, once I got necessary accounts provisioned, it was just one unending stream of pushing items on a Kanban board at high velocity. You didn't have to own anything or care about anything, just do the fastest possible change that brings some aspect of a project up to customer's spec. Ain't particularly proud of that one (though I didn't have much of a choice here, their boss was a friend of my boss and needed a favor). Ain't something I'd even consider a proper software job.
And there's probably a typo in your FAQ, "We do not allow sexual of adult content or any kind."
Tech recruiter here. Pros: + Very beautifully designed project + Super readability Big, easy to fix negative: Force people to add months to the years! You only asks the year when someone started in "Work Experience". If I read "2012-2013" I can't tell if someone has been at a place ~12 months or ~1 month. This information is very important. Also, please calculate the durations to allow readers to grasp tenure faster.…
My god.
Even on LinkedIn it is optional.
I was out of work for a year and a half for personal reasons, and I conceal that fact from clueless tech recruiters by having my previous place "2013-2016" and my next as "2017-now". As soon as service "forces people" to fill their form as "tech recruiters" designed, they can just go south.
Earlier quoted context omitted.
You’ve drawn the incorrect logic statement. !Years == !Experience It’s very hard for a SWE to have immediate impact, especially a junior one. Up to the first six months are a write-off. The next period includes their first launch and review with potentially a months long performance improvement plan. With exceptional exceptions, longevity and impact go hand in hand and a lack of longevity at the very least poses ques…
If I was treated the way you describe here as a junior developer in the first year of my career, I would have abandoned software a long time ago. The lack of trust is not something I'd be willing to put up with at the timescale you're describing.