blog

10 reasons everyone at your startup should blog

Corporate blogging is on the rise, and most startups use their blogs as one of their best PR tools. But in most corporate blogs, you can see only a few contributors, most of them cofounders, marketing people or even content creators. That means that a great part of the team is not writing, even eventually, to the corporate blog. I think the best approaches to corporate blogging should involve everyone in your startup.

More content

This is one of the most obvious reasons for making everyone writing to the corporate blog, and also the less important one from my perspective, but it’s a good reason after all. If you want to position your startup, you need to generate content, and publishing more content is a way to improve your actual positioning.

More quality and diversity

More content doesn’t need to mean more content regarding the same interests. If your development team startups contributing to your startup blog, they can write about what they care about, so they’ll probably write about different stuff than marketing people. More diversity means more interestingness for your actual readers and you’ll be also expanding the actual reach of your blog.

Educate everyone to understand your clients

Blogging means also documenting and learning about new stuff. It’s an opportunity for everyone at your startup to start trying to understand what concerns to your market. Even if you have awesome developers, that doesn’t mean that your developers and other members of your start team understand the actual need and concerns of your clients. Make them to research and write about topics that could be interesting to your potential customers, educate your team to understand those problems, so when they’re developing new features, they would better understand how to do it well in order to fulfill your customers interests.

Give visibility to everyone working at your startup

Most of the time we forget companies are built around people, but people is the most important asset in your startup. So if your startup team is your primary asset, why are you hiding part of your team from the world? Make them appear in your blog, make them visible to your customers, and create a more human-friendly company.

Generate trust

Eventually, anyone at your company would be talking to a client or potential customer, because there’s a problem when your customer is using your product (that represents mainly your support team), or even because they found each other at any event and they’re talking about what your product could do for his/her company. If you make your team public and visible, it’s more probable that any customer knows the name of some of your team members, so it’s possible that the customer previously knows about the people from your team he is talking with right now. Knowing a person, even if you only know him due to several posts published in a corporate blog, generates trust, because we trust more the people we know. So making everyone at your startup contributing to your blog, would eventually generate trust to your clients base.

Share Knowledge

You’re a startup, so you hire great people and professionals, who accumulates knowledge about what they do everyday. Sharing knowledge is what has made us evolve as society, so sharing your team’s knowledge would help other to solve specific problems they face. Sharing knowledge also generates trust, because if you share interesting problems and solutions, your startup would become a reference on those topics, making your clients feel that they are on good hands.

Test new ideas

Frequently, in a startup, someone from the company has a new idea that would become in a new feature, or even in a side project that would become a new product. When that happens, certain people on your company talks about that idea in order to decide whether that idea can generate something interesting for the company. But it’s not so frequent that you share that idea among your clients, who are the right people to be asked about the potential interest. Sharing those new ideas on your blog, would help you to test the ideas and receive clients feedback that would help you to model a new feature or product.

Get answers to your actual problems

If you share knowledge and make people lifes easier, why wouldn’t you use your blog to receive help about your actual problems? If your developers usually writes about code hacks, or interesting technologies related to your company, you’ll be creating a community of potential helpers to your technical problems. Don’t be afraid to share your problems with others, I’m pretty sure you would find that sharing them is a very good way to find the perfect solution.

Make everyone be nearer sales

This is a real interesting and problematic point for most startups, so I feel I’d write deeper about making everyone at a startup being more near of the sales team of the sales process. Attract people to your website is one of the first steps in order to make sales, so if you make everyone write in your corporate blog, you’d be starting to walk into the right direction.

Fun

At the end, blogging is fun, so make it possible for your startup team to start making fun contributing to your corporate blog.

Compartiendo código en tu blog con SyntaxHighlighter Evolved

Los que somos algo técnicos, solemos querer compartir algo de código de vez en cuando en nuestros blogs, y a veces resulta complicado compartirlo porque al meterlo dentro de nuestro blog, con los estilos existentes, acaba formándose una amalgama de contenido que no resulta claro a la hora de comprender lo que hace ese fragmento de código. Buscando una opción viable para compartir código de forma más efectiva, he dado con un plugin de WordPress: SyntaxHighlighter Evolved, que quizás algunos ya conocíais pero es nuevo para mi.

Ofrece muchas formas de visualización del código, ajustando el aspecto visual a cómo vemos el código en editores comunes, como Eclipse o Emacs, así como colorea la sintaxis del código en función del lenguaje. Os dejo algunos ejemplos de código para que veáis los resultados:

Código PHP, extraído de los ejemplos de uso de arrays en PHP:

<br />
&lt;?php<br />
function object_to_array($mixed) {<br />
    if(is_object($mixed)) $mixed = (array) $mixed;<br />
    if(is_array($mixed)) {<br />
        $new = array();<br />
        foreach($mixed as $key =&gt; $val) {<br />
            $key = preg_replace(&quot;/^\&#92;&#48;(.*)\&#92;&#48;/&quot;,&quot;&quot;,$key);<br />
            $new[$key] = object_to_array($val);<br />
        }<br />
    }<br />
    else $new = $mixed;<br />
    return $new;<br />
}<br />
?&gt;<br />

Código java, ejemplificado con una función de números fibonacci extraído de Java Examples in a Nutshell:

<br />
public class Fibonacci {<br />
  public static void main(String[] args) {<br />
    int current, prev = 1, prevprev = 0;// Initialize some variables<br />
    for(int i = 0; i &lt; 20; i++) {       // Loop exactly 20 times<br />
      current = prev + prevprev;        // Next number is sum of previous two<br />
      System.out.print(current + &quot; &quot;);  // Print it out<br />
      prevprev = prev;                  // First previous becomes 2nd previous<br />
      prev = current;                   // And current number becomes previous<br />
    }<br />
    System.out.println();               // Terminate the line, and flush output<br />
  }<br />
}<br />

Ejemplo de programación de threads en Python, extraído de Python Threads:

<br />
import os<br />
import re<br />
import time<br />
import sys</p>
<p>lifeline = re.compile(r&quot;(\d) received&quot;)<br />
report = (&quot;No response&quot;,&quot;Partial Response&quot;,&quot;Alive&quot;)</p>
<p>print time.ctime()</p>
<p>for host in range(60,70):<br />
   ip = &quot;192.168.200.&quot;+str(host)<br />
   pingaling = os.popen(&quot;ping -q -c2 &quot;+ip,&quot;r&quot;)<br />
   print &quot;Testing &quot;,ip,<br />
   sys.stdout.flush()<br />
   while 1:<br />
      line = pingaling.readline()<br />
      if not line: break<br />
      igot = re.findall(lifeline,line)<br />
      if igot:<br />
           print report[int(igot[0])]</p>
<p>print time.ctime()<br />

P.D: Imagen de davestfu, licenciada bajo Creative Commons-NC-SA

Estrenando mi blog en mi propio dominio

Mucho antes de tener mi blog personal, tenía ya mi propio dominio: http://www.josek.net, pero en parte por pereza, y en parte porque los CMS de la época para la gestión de blogs no eran más que una imagen borrosa de lo que son hoy en día herramientas como WordPress, lo empecé a escribir en Blogger. Hacía ya tiempo que me apetecía migrar el blog a mi propio dominio, y tras encontrar un tema que me gustaba y podía encajar con mi visión del blog (Inuit Types), y algo de paciencia, hoy re-estreno mi blog bajo mi propio dominio.

De paso, quiero que josek.net aglutine información sobre las investigaciones que realizo, mis fotografías, y también conecte de una forma simple con mi blog de investigación, que sigue residiendo en blogger. Así que poco a poco iré integrando estas cosas con el blog gracias a las páginas que ofrece WordPress. Gracias por leer mi blog, y si tenéis cualquier comentario sobre el diseño o el blog en si, estaré encantado de escucharos.

P.D: Gracias a utilizar feedburner, no tenéis que preocuparos de actualizar el feed los que me sigáis con algún lector de feeds.

Presentación de los Premios Bitácoras 2009

Hoy fue la presentación de los Premios Bitácoras 2009, en la Casa Encendida. Como bien me comentabamos con @prueno y @skiter, resulta sorprendente la excelente organización y afluencia de público para la simple presentación de los premios (ni nominaciones ni premios en si), lo que demuestra la importancia de estos premios. Por otro lado, hay que reconocer las excelentes dotes organizativas de los chicos de Bitacoras, que se han marcado un pedazo de evento a recordar, sobre todo la parte final en la terracita de la Casa Encendida. Os dejo con un vídeo del comienzo de la presentación.

Usando LinkWithin para enlazar posts relacionados

Hace poco descubrí LinkWithin, un servicio que, gracias a una serie de plug-ins para WordPress, bogger, y otras plataformas, se encarga de añadir posts relacionados a cada posts que escribas en tu blog. Después de probarlo un poco, hay tres cosas que me convencen bastante y que me hacen verlo como un servicio de valor añadido para un blog:

1.- Es un fácil de instalar y de usar, ya que símplemente añades el plug-in o el código javascript en dónde quieras que se visualicen los relacionados y al cabo de unas horas ya lo tienes funcionando.

2.- Las entradas relacionadas que muestra parecen tener sentido, coincidiendo palabras clave del título o de las etiquetas, lo cuál ya es bastante más que algunos otras extensiones para mostrar posts relacionados.

3.- La visualización es en formato imagen, LinkWithin se encarga de buscar fotografías dentro de cada post relacionado y hacer un recorte de la misma para mostrar ese fragmento de imagen dentro de las relacionadas.

LinkWithin ya está funcionando el mi blog, por lo que si queréis verlo funcionando podeís hacerlo desde el mismo, aunque os dejo una captura del comienzo de un post, y a continuación otra de las entradas relacionadas proporcionadas por LinkWithin para que los que accedáis desde un agregador de feeds podáis verlo sin pasar por la página:

Entrada


Relacionadas

 Scroll to top