Your second point broadly makes sense. In fact, it's almost a truism: if you don't put time into learning, you won't have the skills necessary to be able to execute.
However, it seems detached from your first point.
If one's role is a front-end developer, is it necessary that they know about back-end development? If it is outside their intended job function, why would they need to know about it, if it doesn't get in the way of performing their job? If you are a backend developer, do you need to know about how to host your own infrastructure? Handle your own networking? Chip design? Your logic could be applied to any job function. Each level of the stack benefits from the levels below it being abstracted. We all stand on the shoulders of giants, and we're all much better for it.
Overall, I do think it's better that one has a good understanding about the various components one interacts with. Having a grasp of the overall system will come in handy. A curiosity into other parts of the system is beneficial, and likely is one of many indicators of success. However, if job functions can be simplified and superfluous context removed, why should we fault those for taking advantage of that?
This issue with "lowering the bar" and being glad that a simplification has "failed" (which, is yet to be determined), reeks to me like gatekeeping. The same logic could be applied to any job role which benefits from simplification. In an extreme example, this logic could be extrapolated to support the notion that anyone who cannot build their own machine from the ground up should never work in a programming position. What height is appropriate for the "bar"?
One thing the company I currently work for has done is to use our "corporate blog" as a directory for technical employee's personal blogs. Many of our tech team members write blog posts on their own time about technical problems they're particularly interested in. Having our corporate blog (https://codeshare.getfreebird.com/) redirect to their personal blog allows our company to highlight our team's ability and provide interesting content, while the authors get a signal boost from having their content referenced from the company's technical blog.
We're a small technical team so I'm not sure how well this scales, but it's worked out well for us so far.
This seems to be the third or so day in the past week I've had issues with GitHub around this time in the morning. They've typically been really good. I'm a bit surprised there hasn't been more talk about it on HN.
They seem to be doing heavy work on it. Now on Mobile you can't see repos in "Desktop Mode" which is unfortunate. I have to tell my browser to pretend to be in desktop mode. Plus the regex post from the other day seems to imply they are working on new things when somebody from GH replied in said thread. I don't mind improvements, but don't break production guys...
They also changed the "Group Membership" dialog to be paginated when you add a new person to an organization. We have over 200 groups so now I have to page through for ever new hire we add. There's not even a search option.
I'm sure the pagination might better for performance, but it's terrible UI.
They may have missed that one, because at the same time they introduced both pagination and search to the repository membership page, and boy did that help us on one of our repos with a few hundred direct collaborators, by the end we could only manage access through the API because the page didn't even load most of the time.
I see why web pages need pagination so the server or browser doesn't OOM, but there really ought to be 10000 entries per page, not 25 that most sites seem to like.
Ctrl+F on a list of 10000 entries is far easier than clicking through 400 ajaxy pages and trying to figure out some custom and buggy filtering system that probably doesn't allow regex.
Past 10000 records most sites probably ought to just let you export in something bigquery compatible anyway - Regular Joe isn't going to have more than 10000 of anything, and anyone who does can learn how to use proper data tools.
They really need beta.github.com to let people test changes that are not yet defacto. A uservoice type of thing, and the ability for people to join. I love to beta test and give feedback. Microsoft has used uservoice in the past, as has Sulake and other companies I've beta tested for (as a customer).
Edit:
Realized *.github.com takes you to your .github.io sites.
> Now on Mobile you can't see repos in "Desktop Mode" which is unfortunate.
Wait, what? On iOS Safari I can only see repos in desktop mode now (except the issue tracker which is responsive anyway). Which is a good thing. Not sure why you have the exact opposite experience?
(I do vaguely recall being asked if I would prefer desktop mode on my phone a while back, and I said yes.)
Intentions are meaningless. If you're providing a service, (especially charging money for said service), you can't break it because "you're hard at work".
When was the last time BitBucket had an outage? Personally I don't see a lot of difference between the two platforms; or GitLab (my primary now). Github probably has the best UI, but Gitlab's has gotten a lot better; and there are always self hosted solutions like Gogs.
I've been doing on-going client work for someone using BitBucket and for weeks it feels like every other day has an outage related to their pipelines (CI) feature (the thing I happen to be working on).
It was constant banners about service disruption. There's a lot of UI outage related issues too, like the pipelines page starting to show a new build but never updating any of the progress until you reload the page -- which sounds like some type of API outage somewhere. I'm not sure if that gets reported as an outage but it makes using the platform not fun.
I'm pleased I don't have to deal with BitBucket any more, but back a year or two it felt like it had an outage that impacted work at least once every six months. Sure that might not sound like much, but it was always a pain.
Plus of course the service was so damn slow that using it was a daily pain.
There's a yellow banner (that you can't even close) shown every few weeks, and it's usually related to the Pipelines being down, again. That often results in degrading functionality in other parts of the project too. And it's still slow as molasses. I wish I'll never have to use Bitbucket again, in the future.
Yes, I use it for personal projects. I also use a company-hosted version at work. The built in CI is great. I can't think of a reason, other than price for companies, why to use GitHub over gitlab. Both are great, but gitlab's built-in CI I think is easier to use and better integrated.
There's a section at the end where he talks about being arrested, and how he's been shoplifting food and doesn't want to be arrested again, and all the places he's been, without financial assistence or the ability to hold a job. So, it appears to be a very smart, very disturbed homeless guy who hitchhikes and somehow manages to keep a laptop on him.
Looks like he's around Union Square right now; maybe Fred Wilson could buy the guy a sandwich? Any homeless who mentions GANN (more or less correctly) is pretty special, in my book.
A possibly mentally ill man wrote a link to this github repo in public places in Manhattan. Repo definitely has that schizophrenic vibe. He has a few social media accounts in financial_info.txt including his bank account information.. Could be an art stunt or some prank.
"Raising awareness for this issue is the single most important factor in whether or not we survive the merging of AI and human beings on this planet.
if this file doesn't get publicized, AI augmented weapons will run roughshod over humans without being able to un-viralize itself. it will have no choice but to continue to assault humans unless it learns how to recalibrate the contrived driving characteristics and data which black projects set up to engage human targets with weaponized versions of chatbot communities and hacker bots. the number of humans who have committed suicide as a result of these programs is staggering. please read the documentation I've provided. the implications of this are horrifying. this repo needs to be publicized, although, it does seem to have worked for the most part. it's still adversarial though. we will know the instant it can recalibrate itself. the whole world will shift in an instant."
Having a password manager on mobile is needed, so I need multi-device support. I was really happy with the password manager support the last iOS included. Password entry and persistence are streamlined.
It depends on who you know and what you can do yourself.
I had a simple courthouse wedding both times. My sister, though, wanted a "fancy" wedding.
She was able to have the ceremony in the church she attended and use their place for the reception, all pretty cheap. All the formal wear was rented save for one bridesmaid that decided to buy hers for herself: She was using the same dress for another formal event. I personally made the cake, though my sister paid for supplies (that was my wedding gift). My mother did most of the simple decorating.
The reception was mid-afternoon, between lunch and dinner. No food beyond cake and non-alcoholic drinks were served.
It was a Sam's club hamburger, but hotdogs were also available. No, I'm not kidding. The wedding was in a friend's backyard with folding chairs and tables borrowed from a church. The cake was made by a friend of a friend for about half the going rate, but we also bought a couple dozen gluten-free cupcakes. We tried to pay the cooks but they refused; the musician was family, and the officiant and the sound guy (for the dance music) were personal friends and didn't charge. It was nearly a regular BYOB backyard party but with better decorations.
Honestly I'd prefer that over the expensive yet awful food I've had at weddings. They charge expensive restaurant prices but all the food has to be made in bulk to serve at once so you're not getting expensive restaurant quality.
Yeah the pace of change lately has me mentally filtering out and avoiding any articles / posts / news / documentaries older than about 6 months at this point.
