開源 物聯網接入_我們剛剛推出了開源產品。 那么接下來會發生什么呢?

開源 物聯網接入

by Victor F. Santos

由Victor F.Santos

我們剛剛推出了開源產品。 那么接下來會發生什么呢? (We just launched an open source product. So what happens next?)

Last month me and the ninja god Pedro launched GitShowcase, a plug-and-play portfolio for developers. Open source and free.

上個月,我和忍者神佩德羅(Pedro)推出了GitShowcase ,這是一個針對開發人員的即插即用產品組合。 開源和免費。

It’s quite simple what the product does. It fetches GitHub user info and projects to craft an one-page layout, just like this.

產品的作用非常簡單。 它將獲取GitHub用戶信息和項目以制作一頁布局, 就像這樣 。

In this post I’ll talk about how we got over 25,000 projects showcased from 80 different countries in a single month, and how we expect to earn money from it. We hope it to be of some help for the product people and enthusiasts out there. Let’s go open source! :)

在這篇文章中,我將討論如何在一個月內從80個不同的國家展示超過25,000個項目,以及我們希望如何從中賺錢。 我們希望它對產品的產品愛好者和發燒友有所幫助。 讓我們開源吧! :)

為什么我們制作GitShowcase (Why we made GitShowcase)

Developers are amazing crafters. No one would disagree. But when applying to new jobs, most of them struggle to find a good way to present their work. Usually they look for pre-made templates or a custom CMS (Content Management System) tools to develop their personal websites.

開發人員是出色的手Craft.io者。 沒有人會不同意。 但是,當申請新工作時,大多數人都在努力尋找一種介紹工作的好方法。 通常,他們尋找預制模板或自定義CMS(內容管理系統)工具來開發其個人網站。

We made it simple for developers in a rush. No hard sign-ups, no forms to fill, no code. Just a button to sign in with a GitHub account. After a one-click sign-in, all relevant info and projects are displayed in an easy, customizable one-page layout.

我們為匆忙的開發人員簡化了工作。 沒有硬注冊,沒有表格可以填寫,沒有代碼。 只需一個按鈕即可使用GitHub帳戶登錄。 一鍵登錄后,所有相關信息和項目都以簡單,可自定義的一頁布局顯示。

I was responsible for the design and Pedro for the engineering. Ironically GitShowcase was meant to be only a side project to put on our portfolios and that’s it, but community drove us other way…

我負責設計,佩德羅負責工程。 具有諷刺意味的是,GitShowcase只是本應放在我們投資組合中的一個附帶項目,僅此而已,但是社區以其他方式推動了我們……

社區的懷抱 (The community embrace)

We published GitShowcase in a few Brazilian development groups of Facebook to gather feedback. We were overwhelmed by a lot of awesome people engaging with the posts and endorsing it to friends.

我們在Facebook的幾個巴西開發小組中發布了GitShowcase,以收集反饋。 很多很棒的人參與這些帖子并將其推薦給朋友,使我們不知所措。

Within just a few hours, we already had over 4,000 projects showcased on the platform. The most surprising part was that many of them were not from Brazil.

在短短幾個小時內,我們已經在該平臺上展示了??4,000多個項目。 最令人驚訝的是,其中許多不是來自巴西。

我們的增長策略 (Our growth strategy)

We were a little scared by the numbers. How were we going to keep up this rate of growth? We had no budget to make ads, nor to promote the website any other way than organically.

這些數字讓我們有些害怕。 我們將如何保持這種增長率? 我們沒有預算來制作廣告,也沒有其他方法來自然地推廣網站。

We focused our efforts on three pillars to see how it would perform:

我們將工作重點放在三個Struts上,以了解其性能:

  1. Social media ─ The source that made us visible to the world. We kept publishing GitShowcase on other groups via Facebook, LinkedIn, and reaching out to tech influencers on Twitter to have GitShowcase tested. We also put share buttons more visible and actionable on the pages.

    社交媒體 ─使我們對世界可見的資源。 我們一直通過Facebook,LinkedIn在其他小組上發布GitShowcase,并在Twitter上聯系技術影響者以測試GitShowcase。 我們還將頁面上的共享按鈕置于可見和可操作的位置。

  2. Content marketing ─ Pedro likes to write about tech life. So he started writing about GitShowcase, such as our tech stack, process, shipping etc., and publishing them on Hackernoon and other blogs. Check his Medium if you’re interested in shipping apps.

    內容營銷 ─Pedro喜歡撰寫有關技術生活的文章。 因此,他開始撰寫有關GitShowcase的文章,例如我們的技術堆棧,流程,運輸等,然后將其發布在Hackernoon和其他博客上。 如果您對運送應用程序感興趣,請檢查他的媒介 。

  3. SEO ─ This is a more long-tail strategy. We thought about the keywords we want to be well ranked for: “developer portfolio”, “github portfolio”, “developer website”, so users can find us organically through Google search. For the profiles, we prepared dynamic keywords: “gitshowcase + username”, “developer portfolio + username”, to get specific user searches linked to our website too. We also spread the GitShowcase link under comments of famous blog posts to work on our link building (and to get some curious scrolling readers to meet us too).

    SEO─這是一個比較長尾巴的策略。 我們考慮了我們想要很好地排名的關鍵字:“開發人員投資組合”,“ github投資組合”,“開發人員網站”,以便用戶可以通過Google搜索有機地找到我們。 對于配置文件,我們準備了動態關鍵字:“ gitshowcase +用戶名”,“開發人員組合+用戶名”,以使特定的用戶搜索也鏈接到我們的網站。 我們還將GitShowcase鏈接傳播到著名博客文章的評論中,以進行鏈接構建(并吸引一些好奇的滾動閱讀器與我們見面)。

那么,該策略的執行情況如何? (So, how the strategy performed?)

The data above represents:

上面的數據表示:

  • On the left: sessions per source. We will identify which of the initiatives brought more visitors to the website.

    左側: 每個來源的會話 。 我們將確定哪些舉措帶來了更多的網站訪問者。

  • On the right: infographic about traffic per country. We will see how people from different countries visited the website, how many signed up, what’s the top 10 countries with more sign ups and what’s the top 10 countries with the best conversion rates.

    右側: 有關每個國家/地區流量的信息圖 。 我們將看到來自不同國家/地區的人們如何訪問該網站,有多少人注冊,注冊次數最多的前10個國家和轉化率最高的前10個國家/地區。

Before diving in, it’s important to state that both “(direct) / none” and “Github.com / referral” are quite misleading the data. We won’t include them in the analysis because it’s confusing even for us, here’s why:

深入研究之前,務必要聲明“ (直接)/無 ”和“ Github.com /推薦人 ”都誤導了數據。 我們不會將它們包括在分析中,因為這甚至使我們感到困惑,原因如下:

  • (direct) / none ─ This source should stand for people that directly type gitshowcase.com on browser and hit go, but Google Analytics has a bug on it since always and takes credit of the traffic from other sources because of tracking failure. You can read more about it here.

    (直接)/無-這個來源應該代表在瀏覽器上直接鍵入gitshowcase.com并立即點擊執行的人,但是Google Analytics(分析)始終存在錯誤,并且由于跟蹤失敗而將其他來源的流量歸功于此。 您可以在此處了解更多信息。

  • Github.com / referral ─ We use the GitHub API to authenticate the user, so it takes credit as the traffic source when it sends back to GitShowcase.

    Github.com/referral─我們使用GitHub API對用戶進行身份驗證,因此當它發送回GitShowcase時,它將信譽作為流量來源。

We’ll take out the misleading data now so you can look at more precise data points.

現在,我們將刪除誤導性數據,以便您可以查看更精確的數據點。

這看起來更好。 (This looks better.)

Here is how the three pillars contributed to the traffic generation:

以下是三大Struts對流量產生的貢獻:

Social media: 2,429 sessions (50% traffic);

社交媒體: 2,429次會話(50%的訪問量);

Content marketing: 1,084 sessions (22.3% traffic);

內容營銷: 1,084次會話(22.3%的訪問量);

SEO: 235 sessions (4.8% traffic).

SEO: 235個會話(4.8%的流量)。

等一下。 其余22.9%呢? (Oh, wait. What about the other 22.9%?)

They are our email marketing traffic (3.6%) and referrals (19.3%). Referrals are other websites with links to ours. This is something we didn’t map at first when making the strategy, other people linking GitShowcase into their pages and newsletters.

它們是我們的電子郵件營銷流量(3.6%)和 引薦(19.3%) 。 推薦連結是指向我們網站的其他網站。 在制定策略時,其他人將GitShowcase鏈接到其頁面和新聞通訊時,這并不是我們最初映射的內容。

It surprised us positively because we were featured in really cool websites, such as Product Hunt. We were hunted by a nice Israeli guy named Raz. Thanks, man! Check GitShowcase on Product Hunt.

這使我們感到非常驚訝,因為我們在很酷的網站(例如Product Hunt)中被推薦 。 我們被一個名叫拉茲的好以色列人追捕。 謝啦! 在Product Hunt上檢查GitShowcase。

Something on our radar now are referrals, which are becoming our 4th pillar — getting other websites to talk about us and endorse us.

引薦現在已成為我們的關注點,引薦已成為我們的第四大Struts-讓其他網站談論我們并認可我們。

Social media nailed it as the best source to drive traffic, as we expected. It’s where users share their profiles and discuss the the tool, tweet it, endorse it, and others can meet us.

正如我們預期的那樣,社交媒體將其定為吸引流量的最佳來源。 在這里,用戶可以共享其個人資料并討論該工具,對其進行鳴叫,認可,其他人也可以與我們見面。

Content marketing was quite expressive too. People pay attention to good quality content and reward it with their time.

內容營銷也很富有表現力。 人們關注高質量的內容,并隨著時間的流逝對其進行獎勵。

SEO is still a baby, because we are building our brand awareness and reputation with search engines. We think it will become more effective over the next 3 months or so.

SEO還是一個嬰兒,因為我們正在通過搜索引擎建立我們的品牌知名度和聲譽。 我們認為它將在未來3個月左右變得更加有效。

好的,我們收到了來自世界各地的杰出人士的報名,并且一些網站在談論我們。 現在,如何從中賺錢呢? (Ok, we got some sign-ups from awesome people worldwide and some websites are talking about us. Now, how to make money out of it?)

That’s where we are in this moment. As the base grows, users start making a lot of suggestions and asking for more features. We iterate the product on a daily basis when we’re home after our full-time jobs. It’s kinda driving us sleepless. So we thought: “Would it be, let’s say, maybe… the right call to monetize GitShowcase?”

那就是我們現在的位置。 隨著基礎的增長,用戶開始提出很多建議并要求更多功能。 我們每天在家工作后,每天都會對產品進行迭代。 這有點使我們無法入睡。 因此我們想到:“是不是,也許……正確的電話交易可以通過GitShowcase貨幣化?”

We have a couple ideas about how to make GitShowcase a freemium product. In other words, people could use the basic plan for free, and get some exclusive features through paid plans. Our basic plan would be the same as it is today — a full and automated portfolio. Paid plans would have the same, along with some extras:

關于如何使GitShowcase成為免費增值產品,我們有一些想法。 換句話說,人們可以免費使用基本計劃,并通過付費計劃獲得一些專有功能。 我們的基本計劃將與今天相同-完整且自動化的產品組合。 付費計劃將具有相同的功能,以及一些額外功能:

  • A custom domain ─ www.username.com instead of https://www.gitshowcase.com/username

    自定義域 ─www.username.com,而不是https://www.gitshowcase.com/username

  • Access to premium templates ─ Handcrafted templates for different focus. Today we have only one template, which is focused primarily on projects.

    訪問高級模板 ─手工制作的模板可用于不同的重點。 今天,我們只有一個模板,主要用于項目。

  • Recruitment area benefits ─ Developers need portfolios mostly for job applications, or to be headhunted, so building a recruitment area seems like a no-brainer. Recruiters would be able to search our database to find developers with specific knowledge, and those on paid plans would appear higher up in results than those who are on the basic plan.

    招聘區域的好處 ─開發人員主要是為了求職或被獵頭而需要投資組合,因此建立招聘區域似乎是理所當然的事情。 招聘人員將能夠搜索我們的數據庫,以找到具有特定知識的開發人員,而那些付費計劃的人的收入要比那些基本計劃的人高。

調查時間 (Time to survey)

Before spending any time developing the features, we made a survey with our users to understand if these ideas would resonate to their interests. We used Mailchimp to send the email and Typeform to activate it.

在花任何時間開發功能之前,我們與用戶進行了調查,以了解這些想法是否會引起他們的興趣。 我們使用Mailchimp發送電子郵件,并使用Typeform激活它。

“今天缺少什么?” (“What’s missing today?”)

Wow, analytics and generic inner content? We just put these options there to fill space, but apparently they’re what most people want.

哇,分析和通用內部內容? 我們只是將這些選項放在此處以填充空間,但是顯然它們是大多數人想要的。

This is why listening to users is important. We are very biased by what we think is a priority.

這就是為什么聽用戶很重要的原因。 我們認為優先是我們的偏見。

“你愿意付那些錢嗎?” (“Would you pay for those?”)

I must confess we were expecting more enthusiasm here, even when we know it’s hard to ask for people to abstract and imagine them paying for something they can’t yet see or interact with.

我必須承認,我們期望在這里有更多的熱情,即使我們知道很難要求人們抽象和想象他們為看不見的事物或與之互動所付出的代價也是如此。

Well, maybe is not that bad… Right? *holding tears*

好吧,也許還不錯...對嗎? *流淚*

I have heard once that companies should listen more to the extreme users of both ends — the haters and the lovers. This is where you can see serious mistakes, and you can see how you are adding real value to people’s lives. Neutrals won’t bother telling you much, because they don’t hate nor love you, so it mostly gets you in the same place. Makes sense, I guess…

我曾經聽過,公司應該更多地聽取雙方的極端用戶-仇恨者和愛好者。 在這里,您可以看到嚴重的錯誤,也可以看到如何為人們的生活增加真正的價值。 中立人不會費心告訴您很多事情,因為他們既不討厭也不愛您,所以它通常會使您處于同一個位置。 我猜是有道理的...

“值得付出的服務是什么?” (“What could be a service worth paying for?”)

This was the last question of the survey. It was open, more abstract than the others and not required, so many people just passed it blank. 29% spoke their mind. I will try to condense the answers on three personas:

這是調查的最后一個問題。 它是開放的,比其他的更抽象,并且不是必需的,因此許多人將其空白。 29%的人說了主意 。 我將嘗試將答案濃縮為三個角色:

Hater: I might have signed up, but don’t even try to charge something, I can develop my own portfolio if I want to, you obnoxious capitalists!!!!

Hater:我可能已經簽約了,但是甚至不想收費,如果你愿意,我可以發展自己的投資組合,令人討厭的資本家們!!!!

Neutral: It’s ok to charge something, but how about a symbolic $1 per year just to have access to GitShowcase? It’s fair to help you pay the bills.

中立:收費是可以的,但是每年僅象征性地支付1美元就可以訪問GitShowcase嗎? 幫助您支付賬單很公平。

Lover side: I like the custom domain thing and would pay for it. The portfolio is really cool. But guys, have you thought about getting us closer to recruiters? Man, that’s something that would make me to tattoo the GitShowcase logo on my leg.

情人方面:我喜歡自定義域名,并且會為此付費。 投資組合真的很棒。 但是伙計們,您是否考慮過讓我們更接近招聘人員? 天哪,那會讓我在腿上刺青GitShowcase徽標。

This was way more revealing than the other closed questions. We won’t make much progress on tiny specific things that developers can code themselves. Custom domains are still a thing because some people would like their GitShowcase profile to be their official website.

比其他未解決的問題更能說明問題。 在開發人員可以自己編寫的微小特定事項上,我們不會取得太大進展。 自定義域仍然是一件事情,因為有些人希望他們的GitShowcase個人資料成為其官方網站。

What got us really wondering is that we had plans for a recruitment area to happen in the future, but we didn’t put that in the survey because we thought it to be a really distant step. But some users are already expecting it to happen. TODAY. And they are on fire.

我們真正想知道的是,我們計劃在將來進行招聘,但我們沒有將其納入調查范圍,因為我們認為這是一個遙不可及的步驟。 但是一些用戶已經期望它會發生。 今天。 他們著火了。

招聘人員對GitShowcase感興趣嗎? (Do recruiters have interest on GitShowcase?)

I’m looking into this. I spammed some high level tech recruiters in my network with a couple questions to see which tools they use currently, how they research candidates before approaching them, and whether they’re interested in a place to hunt developers by specific knowledge, location, and projects.

我正在調查這個。 我向網絡中的一些高級技術招聘人員發送了一些問題,以詢問他們當前使用哪些工具,在與候選人聯系之前如何研究候選人以及他們是否對通過特定知識,位置和項目來尋找開發人員的場所感興趣。

Three answered back. All of them had positive feedback about the prospects of using our platform.

三人回答了。 他們都對使用我們平臺的前景有積極的反饋。

Do you know a tech recruiter? Tag him/her in the comments please. We are very open to count on them to help us shape GitShowcase.

你認識科技招聘人員嗎? 請在評論中標記他/她。 我們非常愿意依靠它們來幫助我們塑造GitShowcase。

接下來我們要做什么? (What are we going to do next?)

Well, it seems now we have a plan. And tons of homework. We decided to prioritize the tasks by balancing relevance and ease of implementation. So, this is what we will grind out over the next three months:

好吧,現在看來我們有了一個計劃。 和大量的作業。 我們決定通過平衡相關性和易于實施的方式來優先考慮這些任務。 因此,這是我們在接下來的三個月中要研究的內容:

  • Custom domain functionality

    自定義域功能
  • Modular templates to enrich profile content

    模塊化模板以豐富配置文件內容
  • A talent recruitment area

    人才招聘區

為什么我只告訴你我所有的計劃? (Why did I just tell you all my plans?)

We embrace the open source culture. Even when the common sense might say otherwise, we believe transparency builds trust, while secrecy repels it. People shouldn’t be afraid of sharing knowledge and speaking openly about their plans.

我們擁護開源文化。 即使常識可能另有說明,我們也認為透明度可以建立信任,而保密可以消除信任。 人們不應該害怕分享知識并公開談論自己的計劃。

到目前為止,我們已經吸取了教訓: (The lessons we’ve learned so far:)

  1. Open source is love. Open source is life.

    開源就是愛。 開源就是生命。
  2. People won’t steal the code because it’s open. In fact, people help building the product. Fork our project on GitHub and help us too.

    人們不會竊取該代碼,因為它是開放的。 實際上,人們可以幫助構建產品。 在GitHub上分叉我們的項目,也可以幫助我們 。

  3. Content marketing performs well if the content is relevant and published in the right places.

    如果內容相關并在正確的位置發布,則內容營銷將表現良好。
  4. If you aren’t sure of something, just ask. Don’t try and fake anything that your users depend on.

    如果您不確定某件事,請詢問。 不要嘗試偽造用戶依賴的任何內容。
  5. If your product doesn’t solve a real problem, there’s no strategy that can save it. Build a good product, and do some marketing to take your product places.

    如果您的產品不能解決真正的問題,則沒有可以挽救它的策略。 建立一個好的產品,并進行一些營銷以取代您的產品。

喜歡這個職位嗎? 通過在評論中標記開發人員或技術招聘人員來幫助我們:) (Liked the post? Help us by tagging a developer or a tech recruiter in the comments :))

We are a two-man band with zero budget trying to make things happen, so all the support is more than welcome. You can either:

我們是一個兩人樂隊,預算為零,力求使事情成真,因此,所有的支持都將受到歡迎。 您可以:

  1. Tag a developer in the comments to meet GitShowcase

    在評論中標記開發人員以符合GitShowcase

  2. Tag a tech recruiter to take a look at what we’re doing here. We’ll be opening the talent recruitment dashboard on beta soon.

    給技術招聘人員標簽 ,看看我們在這里做什么。 我們即將在Beta版中打開人才招聘信息中心。

  3. Like, comment and share this post to help it reach out more interesting people just like you.

    喜歡,評論和分享此帖子,以幫助它吸引更多與您一樣有趣的人。

If you are still reading this, you’re the best. Thanks for your time.

如果您仍在閱讀本文,那將是最好的。 謝謝你的時間。

Follow GitShowcase on Facebook, Twitter and GitHub.

在Facebook , Twitter和GitHub上關注GitShowcase。

翻譯自: https://www.freecodecamp.org/news/we-launched-an-open-source-product-what-happens-now-e586b6d8b99c/

開源 物聯網接入

本文來自互聯網用戶投稿,該文觀點僅代表作者本人,不代表本站立場。本站僅提供信息存儲空間服務,不擁有所有權,不承擔相關法律責任。
如若轉載,請注明出處:http://www.pswp.cn/news/395775.shtml
繁體地址,請注明出處:http://hk.pswp.cn/news/395775.shtml
英文地址,請注明出處:http://en.pswp.cn/news/395775.shtml

如若內容造成侵權/違法違規/事實不符,請聯系多彩編程網進行投訴反饋email:809451989@qq.com,一經查實,立即刪除!

相關文章

Class? getClass()

getClass()方法屬于Object的一部分,它將產生對象的類,并且在打印該類時,可以看到該類類型的編碼字符串,前導"["表示這是一個后滿緊隨的類型的數組,而緊隨的"I"表示基本類型int, //: initialization/OptionalTrailingArgrments.java package object;import …

log4j使用說明

1.log4j代碼中修改輸出級別:如: protected final Logger logger LoggerFactory.getLogger(Test.class); 將其轉成實現類,修改輸出級別即可System.out.println(logger.isDebugEnabled()?"debug is true":"debug is false&quo…

java list集合增刪改_Java中集合類list的增刪改查

今天給大家帶來的是Java中list類的使用,java.util 包提供了list類來對線性數據操作List接口是Collection接口的子接口,List有一個重要的實現類--ArrayList類,List中的元素是有序排列的而且可重復,所以被稱為是序列List可以精確的控…

IIS6、IIS7和IIS8各版本的差別

一、寫在前面 目前市面上所用的IIS版本估計都是>6.0的.所以我們主要以下面三個版本進行講解 服務器版本IIS默認版本server20036.0server20087.0server20128.0二、IIS6的請求過程 由圖可知,所有的請求會被服務器中的http.sys組件監聽到,它會根據IIS中的 Metabase 查看基于該 …

Android Studio 插件的使用

1、GsonFormat https://github.com/zzz40500/GsonFormat 2、Android SelectorChapek http://blog.csdn.net/weifei554287925/article/details/41727541

函數式編程基礎_在收件箱中免費學習函數式編程的基礎

函數式編程基礎by Preethi Kasireddy通過Preethi Kasireddy 在收件箱中免費學習函數式編程的基礎 (Learn the fundamentals of functional programming — for free, in your inbox) If you’re a software developer, you’ve probably noticed a growing trend: software ap…

安卓Java虛擬機大小_虛擬機為安卓流暢度背鍋,是因為關系數十萬程序員飯碗?...

導讀:虛擬機相當于應用程序在不同運行環境中的翻譯。說起谷歌安卓系統的“虛擬機”,很多人愛拿它和蘋果iOS做比較,結果,安卓的很多短腿兒都讓虛擬機背了鍋,比如安卓手機運存容量是iPhone的兩到三倍,流暢度卻…

Redis PHP連接操作

安裝 要在PHP程序中使用Redis,首先需要確保 Redis 的PHP驅動程序和 PHP 安裝設置在機器上。可以查看 PHP教程 教你如何在機器上安裝PHP。現在,讓我們來看看一下如何設置 Redis 的PHP驅動程序。 需要從 github 上資料庫: https://github.com/n…

AppCompatActivity實現全屏的問題

前言:我的 Activity 是繼承 BaseActivity , 而 BaseActivity 繼承 AppCompatActivity 。 BaseActivity 的繼承 /*** 應用程序的基類**/ public class BaseActivity extends AppCompatActivity {}HomeActivity 的繼承 public class HomeActivity extends BaseActivit…

aws cognito_使用AWS Cognito的用戶管理—(1/3)初始設置

aws cognitoby Kangze Huang黃康澤 使用AWS Cognito的用戶管理—(1/3)初始設置 (User Management with AWS Cognito — (1/3) Initial Setup) 完整的AWS Web樣板-教程1A (The Complete AWS Web Boilerplate — Tutorial 1A) Main Table of Contents Click Here主要目錄請點擊這…

java建一個conversion_Scala中的JavaConverters和JavaConversions之間有什么區別?

JavaConversions 提供了一系列隱式方法,可以在Java集合和最接近的相應Scala集合之間進行轉換,反之亦然 . 這是通過創建實現Scala接口的包裝器并將調用轉發到底層Java集合或Java接口,將調用轉發到底層Scala集合來完成的 .JavaConverters 使用p…

flexbox:1.0.0_了解Flexbox:您需要了解的一切

flexbox:1.0.0This article will cover all the fundamental concepts you need to get good with the CSS Flexbox model. It’s a long one, so I hope you’re ready for it.本文將介紹您熟悉CSS Flexbox模型所需的所有基本概念。 這是一個很長的時間,所以希望您…

10.Object類

在JAVA中,所有的類都直接或間接繼承了Java.lang.Object類Object是一個特殊的類,他是所有類的父類,是Java類層中的最高層類。當創建一個類時,他總是在繼承,除非某個類已經指定要從其他類繼承,否則他就是從ja…

RecyclerView的下拉刷新和加載更多 動畫

下拉刷新和加載更多 1、https://github.com/jianghejie/XRecyclerView 2、http://blog.csdn.net/jabony/article/details/44780187 動畫 1、https://github.com/wasabeef/recyclerview-animators

java中顯示動態信息的方法_java里的動態表單技術

最近的一個項目,由于客戶的需求等信息不確定,為了降低以后修改的成本及產品的推廣考慮到動態表單技術,之前也一直在考慮到動態表單技術,畢竟在delphi里已經實現過了,由于我們采用的hibernate的執久層的原故&#xff0c…

Cinder 組件詳解 - 每天5分鐘玩轉 OpenStack(47)

本節我們將詳細講解 Cinder 的各個子服務。 cinder-api cinder-api 是整個 Cinder 組件的門戶,所有 cinder 的請求都首先由 nova-api 處理。cinder-api 向外界暴露若干 HTTP REST API 接口。在 keystone 中我們可以查詢 cinder-api 的 endponits。 客戶端可以將請…

中國移動 全球通、 動感地帶、神州行 的區別

1、全球通 1、主要面向商務人士可以享受機場VIP俱樂部的尊貴、1860專席的高質量服務、個性化賬單、客戶積分獎勵以及大客戶經理貼心服務,更有尊貴資費套餐優惠,但它價格也是最貴的。 2、全球通面對事業成功的人士,進取。 3、全球通&#xff…

java 并發測試main方法_java并發編程test之synchronized測試

synchronized關鍵字可以用于聲明方法,也可以用于聲明代碼塊;package com.test.java;public class SyncTest {public static void main(String[] args) {SynchronizedDemo1 synct1 new SynchronizedDemo1();SynchronizedDemo2 synct new SynchronizedDemo2();SynchronizedDemo…

業余愛好者linux_如何從業余愛好者變成專業開發人員

業余愛好者linuxby Ken Rogers肯羅杰斯(Ken Rogers) 如何從業余愛好者變成專業開發人員 (How to Go From Hobbyist to Professional Developer) A few years ago, I was bouncing back and forth between landscaping jobs and restaurant jobs. I had just left college, and…

RedHat Enterprise Linux 6 配置Xmanager ,實現圖形界面連接

我們經常見到的幾種最為常用的windows下遠程管理Linux服務器的方法,基本上都是利用SecureCRT,或者是PUTTY等客戶端工具通過ssh服務來實現Windows下管理Linux服務器的,這些客戶端工具幾乎不需要什么配置,使用簡單,但是它們都無法啟…